Can't Navigate My LAN Or Ping
glgxg at sbcglobal.net
Sun Dec 7 01:48:34 UTC 2008
On 12/06/2008 04:10 PM, Leonard Chatagnier wrote:
> --- On Sat, 12/6/08, NoOp wrote:
> And it doesn't tell me much either except that I'm on line and have
> been all day except for a couple of lost connections. I then went to
> gnome and things have been running a little smoother. Thought you
> might like to hear that-:))
OK, so I'm a little confused (not unusual):
1. The IWM (Intrepid Wireless Machine - I am too lazy to keep typing the
full identifier - hence using 'IWM' previously) is actually your Gutsy
Wireless Machine (GWM) and it's working with a fixed IP of 192.168.1.2
when connected to the 2wire. Both ifconfig and iwconfig show that IP
address on your GWM.
2. You've verified that you are actually connected to, and talking to
_your_ 2Wire & not some other open network within your range.
3. You can connect to the internet & post here (I thought perhaps you'd
been doing so via Windows instead of Ubuntu).
4. You currently have no other machine connected to the network other
than GWM to ping or test to/from. But the existing issue is that you
can't get to the 2wire manager using a browser at 192.168.1.254 or by
http://gateway.2wire.net is that correct? Also try:
http://192.168.1.254/setup you'll need to enter the number on the bottom
of the router/modem, but that should get you into the setup.
If it is, then your 2wire might actually not be set to 192.168.1.x. Try
this; reset the GWM temporarily to DHCP (set it to roaming in Network
Manager) & power the 2wire off/on as instructed previously so that it
clears it's DHCP tables. Reconnect using the GWM and check the IP
address that the device issues. Post back with the address.
If the DHCP address is in the 192.168.1.1 - 192.168.1.63 (reserved
static IP) range then your 2Wire has been set back to it's default and
is again issuing DHCP for the full 192.168.1.1 - 192.168.1.253 range.
More information about the ubuntu-users