Lan Barnes wrote: > On Fri, January 26, 2007 10:40 pm, Gus Wirth wrote: >> Chris Mauricio wrote: >>> Google is not my friend... >>> >>> Recently did a fresh install from FC4 to FC6. I had noticed this issue >>> sporadically in FC4, where dhcp would fail to pick up the gateway every >>> odd >>> router or so. This issue has become full blown in FC6. >>>
<snip> ..next part was from gus.. >> Unfortunately, the problem is probably not in Linux but in the DHCP >> server. I discovered that many DHCP servers (Microsoft, cheap wireless >> access points) are brain dead and take the RFC's as suggestions and not >> as requirements and do not present the gateway in the correct manner. >> >> One way to help troubleshoot would be to see if you can sniff the >> connection, either by running the DHCP client in debug mode or maybe >> with Wireshark (the new name for Ethereal). I had to do that at the >> Installfest at National City Adult School. >> .. > > I suspected as much in Portland. Is there a workaround? I would have added > a GW by hand but didn't know how to detect or guess it. Here are some guess-worthies: On a rh/fedora type system, look at the contents of /var/lib/dhclient/dhclient-eth0.leases (or whatever matches your device) on ubuntu (& debian?) look for /var/lib/dhcp3/dhclient.eth0.leases The default route is normally determined by a line in there like option routers 192.168.1.1 (or some such) If there no such line, I would try as a guess other IPs from that file, such as: dhcp server address domain name server (if actually in the local network) If none of those works, I might try the lowest and highest IPs in the local network (taking account of the netmask to determine the network) ..for an issued IP=192.168.1.123 netmask 255.255.255.0, try 192.168.1.X for X=1 and 254 ..for an IP=10.17.18.19 netmask 255.0.0.0 try 10.0.0.X for X=1 and 254 Rather than setting and removing default routes, I would first try ping and not bother if there is no ping response. In case you forget, the route commands are route add default gw 192.1.68.1.1 route del default Remember that "There Can Be Only One" (tm) default route, so you may need to do the delete if route -n shows any existing destination 0.0.0.0 entry(-ies) Regards, ..jim If there is no -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
