Resolved, sort of: [PLUG] Network is unreachable

Mon Dec 27 01:53:49 UTC 2004

On Sunday 26 December 2004 2:23 pm, Evan Heidtmann wrote:

> AFAIK, DHCP normally provides the default gateway. So up until now, DHCP
> was doing its job.

Naturally, when something like this comes up, I'm usually short on time. Now 
that I have some spare time, I've looked up how the DHCP client works and see 
that it should have been able to get what it needed by broadcasting 
DHCPDISCOVER, which I am assuming it normally does. I'm also assuming that my 
router, which runs a DHCP server should have responded to that request, so 
I'm not sure why I needed to manually configure the default gateway. Maybe I 
didn't. Maybe something was temporarily misconfigured, and my fiddling with 
YaST reconfigured things.

> Just out of curiosity, what does 'route -n' output?

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

I understand the 192.168 and the 127 IP addresses, above, but I don't 
recognize 169.245.0.0. Is that likely to be Comcast, my ISP?

-- 
Regards,

Dick Steffens
http://home.comcast.net/~rsteff/