Re: [SLUG] Another annoyance

From: Chuck Hast (wchast@gmail.com)
Date: Sun Aug 29 2004 - 18:13:01 EDT


On Sun, 29 Aug 2004 16:08:41 -0400, Chuck Hast <wchast@gmail.com> wrote:
> On Sun, 29 Aug 2004 14:42:52 -0400, Felix Boecker
> <3.14159265359@mad.scientist.com> wrote:
> > if you're using wireless networking, that'd be a problem. I've had the
> > same problem and after digging through various fora on the web, it
> > turned out that one the updates kill the wireless connectivity. I even
> > tried reinstalling stock kernel packages without success. Just a thought.
> >
> >
> Indeed I am using wireless, I use the wired connection at the office and both
> of them were working just fine. I did the updates last night and zazzz, no
> more routing. I can ping anyting on MY network numericaly, but I can not
> ping anything beyond the router by name (no DNS being pased) or by address.
> It looks to me like the machine is not picking up the gateway from DHCP.
> I was looking at the routing and I see the first entry has the folloing (from
> memory
> route gw etc etc...
> 192.168.1.0 *
> I figure that the gateway should be 192.168.1.1 which is the address of the
> router.

More info and wierdness...
1. I am doing this as root because after about 18 hours it just started working.
2. The dhcp stuff is in in resolve.conf.
3. I do NOT like things that fix themselves particularly when I do NOT know
    why.
4. I see that the road runner DNS servers have been automaticaly recorded
    in resolv.conf

Here is what my routing table looks like
rf-tools:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 0 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
rf-tools:~ #

This is what it looked like prior to the link coming up
rf-tools:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 0 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
rf-tools:~ #

I wonder why it took so long to finally figure out that it needed to go out and
get the gateway info in there?

Some timer that my not be kicking off correctly?

-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS).  Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:43:12 EDT