Can't Navigate My LAN Or Ping

Leonard Chatagnier lenc5570 at sbcglobal.net
Sun Dec 7 01:10:43 UTC 2008



--- On Sat, 12/6/08, Mark Kirkwood <markir at paradise.net.nz> wrote:

> From: Mark Kirkwood <markir at paradise.net.nz>
> Subject: Re: Can't Navigate My LAN Or Ping
> To: "Ubuntu user technical support, not for general discussions" <ubuntu-users at lists.ubuntu.com>
> Date: Saturday, December 6, 2008, 5:40 PM
> Leonard Chatagnier wrote:
> >
> > Think I've done that before but here it is again.
> > But you may have to interpret it as it looks like
> > it says 192.168.1.254 that it always has been.
> > lchata at ubuntu:~$ netstat -Frn
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags 
>  MSS Window  irtt Iface
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     
>    0 0          0 eth0
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     
>    0 0          0 wlan0
> > 169.254.0.0     0.0.0.0         255.255.0.0     U     
>    0 0          0 wlan0
> > 0.0.0.0         192.168.1.254   0.0.0.0         UG    
>    0 0          0 wlan0
> > 0.0.0.0         192.168.1.254   0.0.0.0         UG    
>    0 0          0 eth0
> > lchata at ubuntu:~$
> >
> >   
> 
> Maybe I missed it - anyway, yeah - your workstation thinks
> its gateway 
> is 192.168.1.254 - looks like you have a wireless network
> (as I type 
> this I see your next message which mentions this, LOL).

No problem and if you've been reading/answering email all day
as I have, it's now wonder.  I'm just about to go blind ansering
2 separate post on the same topic thanks to Karl.-:))  Thanks for
 verifying my desktop thinks it's router/gateway is what it always
has been.

> >> If you changed it manually, it's possible a
> loss of
> >> power
> >> (blackout,etc) caused it to reset to factory
> defaults. Any
> >> manual
> >> changes you did would be erased.
> >>
> >>     
> > The router was unplugged yesterday while talking to
> ATT but the
> > problem existed well before I unplugged it.  I'm
> going to do a manual
> > reset of the router using the button on the back side
> but not before I
> > hear from NoOp and Nils who first responded to this
> thread.  Don't want
> > to do something to break the chain until I hear from
> them.  Thanks for 
> > your input and please tell me your thoughts on the
> output of netstat -Frn.
> > Does it not verify that my gateway/router IP is
> 192.168.1.254? I ask because
> > I'm not very network literate.
> >   
> 
> Good plan, waiting for No0p et al.  And, re the router, yes
> - see above.
> 
> What I would recommend next is to install nmap, scan your
> router ip (i.e 
> nmap 192.168.1.254) and post the results here (unless No0p
> et al provide 
> an alternative solution that is...).
> 
>
Here it is but it looks like it can't connect either.  Using the -NP option
has a way to go yet.  Interesting to seen what the -NP option shows 
but it's going to be another 24 minutes before it completes. If something
profound shows up, I post it. Thanks for you help.
lchata at ubuntu:~$ nmap 192.168.1.254

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-06 18:55 CST
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 2.406 seconds
lchata at ubuntu:~$ nmap -PN 192.168.1.254

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-06 18:55 CST
Stats: 0:01:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 3.66% done; ETC: 19:24 (0:28:12 remaining)
Stats: 0:11:26 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 32.20% done; ETC: 19:31 (0:24:03 remaining)
  

Leonard Chatagnier
lenc5570 at sbcglobal.net





More information about the ubuntu-users mailing list