On Tue, Nov 05, 2002 at 09:01:37PM -0800, Steven Bedrick wrote:
So, it looks like it's getting an IP addresss for the remote host, it just can't get there. What the heck is going on here?
Regarding the next question, "ifconfig -a" looks normal (I've still got an IP address, and other stuff seems to be set properly). That is, it looks the same when my network is working and when it isn't.
So the interface is up, but it doesn't work.
To ultimately determine whether it is a DHCP or driver problem, try a static configuration instead of DHCP: rcdhclient stop ifconfig eth0 192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0 up route add default gw 192.168.0.5 (or whatever the address is that you last got from the DHCP server) ...and see the problem turns up as well.
I'm a bit unclear- is "route add default gw 192.168.0.5" a second command after ifconfig? Also, which address should be used rather than "192.168.0.5"? My own computer's most recently assigned IP address? My broadcast address?
"route ..." is a second command. The IP address would be the default route of your subnet (if there is any), check 'route -n', the line that starts with 0.0.0.0. (Another way of setting the interface up would be to rcdhclient restart and 'killall -9 dhcpcd', that leaves the interface up) But anyway, this doesn't look like a problem with the DHCP client. The DHCP client just sits there and waits. It looks more like a driver problem. It would be most promising to try a different kernel, as it was suggested earlier in this thread. Peter -- Thought is limitation. Free your mind.