\_ SMTP quoth Eric Bishop on 8/18/2003 23:06 as having spake thusly:
\_
\_ David,
\_ 
\_ You stated that nmap says 80 is open, did you scan your IP (internet
\_ access provider assigned) or did you scan 192.168.1.1? 

I scanned it from the dhcp address it gave me.



\_ SMTP quoth Bill Lindley on 8/18/2003 23:18 as having spake thusly:
\_
\_ what does 'ifconfig eth0' say that you currently have your IP and 
\_ netmask set to?

Well, this morning the wireless is being difficult, but the wired
ifconfig is saying 

192.168.1.107 mask 255.255.255.0

which are both correct/reasonable afaik.



\_ SMTP quoth Eric Bishop on 8/18/2003 23:50 as having spake thusly:
\_
\_ Try connecting via TFTP,
\_ 
\_ at a terminal type: tftp 192.168.1.1
\_
\_ If this works you are able to talk with the Linksys, 

results are inconclusive imho.  I didn't get any errors 'connecting'
to 192.168.1.1 but neither did I get anything that looked definitively
good.  Same same with 192.168.23.3.  Got a tftp prompt on each.  I
don't speak tftp and 'ls' didn't work.  Non destructive pointers for
testing if a tftp connection is really good or not?

\_ then the next
\_ question would be when using Linux to connect to the WAP/Router are you
\_ using Mozilla or a browser that utilizes the Mozilla engine? 

I had been using Mozilla and telnet.  No results in either.

\_ and also interfered with Netscape; it is absent in 1.44 and a good
\_ reason to upgrade.

The windows view into it says 1.45.1, so I'm hoping it's still good.  :-)

\_ The symptom you're likely to see is a broken-image icon at the upper
\_ left hand corner of each page. The broken image is a series of
\_ file-folder tabs for an image map. That image map is how you get to the
\_ other web pages.

Sure.  I've not even got the grace of a broken image map.  Nothing.

\_ You will almost always have to do this on the first page, but it often
\_ won't trigger on later page loads.

Possibly pulling from cache.

\_ Hope this helps, I have references of this information if interested,
\_ just ask!

I found some of this already, but was hoping firmware 1.45.1 hadn't
backslid. 

\_ Most other browsers are immune to this problem. Konqueror doesn't
\_ trigger it. Neither does Internet Explorer.

Based on the description telnet should be immune too.  :-)

fwiw, konquerer reports 'An error occured while loading
http://192.168.1.1/: could not connect to 192.168.1.1.'

David