On Saturday 27 January 2007 23:29, James G. Sack (jim) wrote: <SNIP> > > > 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
interesting. Wandering thru /var/log/messages gives me this relevant error earlier when I was still having issues- I missed it: dhclient:can't create /var/lib/dhcp/dhclient-eth1.leases: No such file or directory. So this could likely be the reason I could not retrieve a GW when using dhcp under network device control - perhaps the knetworkmanager doesn't touch that file. Regardless, dhcp seems to work properly now using knetworkmanager. see the log -> Jan 27 18:58:47 hekate dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Jan 27 18:58:47 hekate dhclient: DHCPACK from 192.168.1.1 Jan 27 18:58:47 hekate NetworkManager: <information> Retrieved the following IP4 configuration from the DHCP daemon: Jan 27 18:58:47 hekate NetworkManager: <information> address 192.168.1.66 Jan 27 18:58:47 hekate NetworkManager: <information> netmask 255.255.255.0 Jan 27 18:58:47 hekate NetworkManager: <information> broadcast 192.168.1.255 Jan 27 18:58:47 hekate NetworkManager: <information> gateway 192.168.1.1 Jan 27 18:58:47 hekate NetworkManager: <information> nameserver 192.168.1.1 Jan 27 18:58:47 hekate dhclient: bound to 192.168.1.66 -- renewal in 40194 seconds. Jan 27 18:58:47 hekate NetworkManager: <information> nameserver 68.238.64.12 Jan 27 18:58:47 hekate NetworkManager: <information> hostname 'hekate' Jan 27 18:58:47 hekate NetworkManager: <information> domain name 'verizon' Jan 27 18:58:47 hekate NetworkManager: <information> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 27 18:58:47 hekate NetworkManager: <information> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Jan 27 18:58:47 hekate NetworkManager: <information> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Jan 27 18:58:47 hekate avahi-daemon[2407]: New relevant interface eth1.IPv4 for mDNS. Jan 27 18:58:47 hekate avahi-daemon[2407]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.66. ---------------- Lan- tomorrow I will outline the steps for you I went thru to get it working using DJA's info. Tired. eyes a little blurry.. thanks again to all who responded! C. -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
