From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
Description of problem:
First of all, netplugd is not added to chkconfig--is this a security
feature or a bug?
The machine I am using is an Intel Pentium III 600MHz with an Intel
EEPRO100 NIC. I am disconnecting the cable at the switch, not at the
Once I start netplug, I see that it attempts to get an address (even
though the network is already up). I unplug the cable, and netplug
brings eth0 down. I plug in the cable, and netplug brings up eth0. I
unplug the cable, and netplug brings eth0 down. I plug in the cable,
and I get no response from netplug. eth0 remains down, and the kernel
(kernel-2.6.1-1.65) doesn't even recognize that the cable has been
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start netplugd
2. Unplug cable, verify network is down
3. Plug in cable, verify network is up
4. Unplug cable, verify network is down
5. Plug in cable, verify that network is still down
Actual Results: The network remained down even though the cable was
Expected Results: It should have brought up the network.
Created attachment 98081 [details]
Log of netplug actions
This is the /var/log/messages entries during plug/unplug. Notice that the last
time I plug in the cable, no kernel messages were received stating that the
cable was plugged in.
With netplug stopped, the kernel acknowledges all unplug/plug actions.
Well, this looks more like a kernel resp. driver problem to me as the
kernel has to send that message to userland, otherwise how should
netplug be able to detect the reestablished link?
So i'm reasssigning this bug to kernel.
Read ya, Phil
PS: The missing chkconfig is a bug, will be fixed on next version.
Has anyone looked at this from a kernel perspective?
is this still a problem with the 2.6.9 based update?
Created attachment 108045 [details]
/var/log/messages from my RHEL4 box running 2.6.9-1.751_ELsmp (should be pretty
close to latest FC2 kernel update).
Box in question has an e100 card as eth1 -- /var/log/messages shows output from
multiple plug/unplug cycles while running netplugd. No problem is apparent.