On Mon, Nov 04, 2002 at 07:26:42PM -0800, Steven Bedrick wrote:
'pidof dhclient' didn't return anything, nor did 'pidof rcdhclient'. Even when name resolution is working fine, neither command returns anything.
Okay, let's use a different method: 'ps aufx | grep dhc'
Yeah, that turns up dhcpcd.
Ah! So while the DHCP client is running, the network doesn't work though.
There's nothing in /var/log/messages about dhclient, except for the messages generated by restarting it.
If it dies it should log an error.
Nope. No errors being logged.
Strange. Can you set DHCLIENT_DEBUG to "yes" in /etc/rc.config.d/dhcpcd.rc.config and restart the network? And, as I'm still not clear about what your situation is when the network is "down", can you check 'ifconfig -a' in such a case? Ping your own address? And in addition look for messages like "transmit timeout" or similar messages in /var/log/messages that might come from the driver? Do you have access to the DHCP server logfiles? They could also be helpful. 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.
What about dhcpcd? (Is there a certain reason why you use dhclient?)
Well, apparently, I'm actually using dhcpcd, according to ps. The dhclient bit came into play when I was trying to figure out how to work around this problem. I've got a more-or-less stock SuSE installation going on, nothing fancy, especially in the networking area. I don't know much about the particulars of what's going on with all of that, so I've left it alone.
The names are utterly confusing, which is neither your fault, nor mine :) Peter -- Thought is limitation. Free your mind.