Bugzilla Bug 48482

Hi guys,

using ifplugd - unfortunately it does not down the interface at startup  -even thought it does detect that it is actually down.

see http://forums.gentoo.org/viewtopic.php?t=162916&highlight=ifplugd for details.

I've looked high and low for a config option to make it do this - but there is none.

it works fine, if I plug in the cable, and then unplug it.

ifplugd does not take care of setting routes correctly - but it is fair to say, that the corresponding stop/start network-scripts should handle that - which I made them to, via the wireless-config ebuild (not in portage - written by UberLord) :)

Reproducible: Always
Steps to Reproduce:
1. up your eth0 without cable being plugged in
2. start ifplugd
3. watch the logs and see it detects the if being unplugged.. but does not down it.



Expected Results:  
It should down the interface.

is this still an issue wiht ifplugd-0.25 ?

I just upgraded 0.25 - and it still does not take care of downing the interface
at boot :(

Perhaps thats how its supposed to work - which would IMHO be a failure by
design.

I have similar problems. To show my problems: 
/etc/init.d/ifplugd stop
/etc/init.d/ifplugd start

My link-cable is plugged in, and starting net.eth0 by hand works flawlessly, however, net.eth0 wouldn't start.

I tried out plugging-out the cable, and it would shut down the interface. However, plugging it back in wouldn't start it.
I'm not sure, whether we're talking about the same/similar bug, but at least, it has been working with the oder version, being 0.13x afaik.

I just noted a very funny thing: When I do then manually /etc/init.d/net.eth0 start, ifplugd would detect the link beat. Could it be that net.eth0 shuts down the interface, which doesn't, in turn, allow ifplugd detect the link-beat? 

Dec 25 14:22:45 [ifplugd(eth0)] Link beat lost.
Dec 25 14:22:47 [ifplugd(eth0)] Executing '/usr/sbin/ifplugd.action eth0 down'.
Dec 25 14:22:47 [ifplugd(eth0)] Program executed successfully.
Dec 25 14:25:07 [kernel] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Half Duplex
##-- Now I started the net.eth0 interface --##
Dec 25 14:25:07 [rc-scripts] Configuration not set for eth0 - assuming dhcp
Dec 25 14:25:09 [kernel] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Half Duplex
Dec 25 14:25:10 [ifplugd(eth0)] Link beat detected.
Dec 25 14:25:11 [ifplugd(eth0)] Executing '/usr/sbin/ifplugd.action eth0 up'.
Dec 25 14:25:11 [ifplugd(eth0)] Program executed successfully.
Dec 25 14:25:12 [dhcpcd] infinite IP address lease time. Exiting_

I can confirm: 

I boot my computer - sometimes, eth0 starts, this time it didn't. I did ifconfig eth0 up, and ifplugd would start the device.

Should be fixed with a combination of ifplugd-0.28-r1 and
baselayout-1.12.0_pre7-r1