Hi all, at boot up and when no caple is plugged in into my laptop (Fujitsu Siemens Amilo M 7400), the ifplugd daemon still detects a beat link and therefore causes dhclient to run. This means that the boot up process is paused until dhclient gives up: ifplugd(eth0)[4073]: ifplugd 0.26 initializing. ifplugd(eth0)[4073]: Using interface eth0/00:0A:E4:23:E1:5E with driver <b44> (version: 0.94) ifplugd(eth0)[4073]: Using detection mode: SIOCETHTOOL ifplugd(eth0)[4073]: Initialization complete, link beat detected. ^^^^^^^^^^^^^^^^^^^^^ But no cable is plugged in ^^^^^^ ifplugd(eth0)[4073]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. dhclient: Internet Systems Consortium DHCP Client V3.0.1 ifplugd(eth0)[4073]: client: Internet Systems Consortium DHCP Client V3.0.1 dhclient: Copyright 2004 Internet Systems Consortium. ifplugd(eth0)[4073]: client: Copyright 2004 Internet Systems Consortium.
... and so on until dhclient gives up, because the beat link was detected falsely, because there is no cable plugged in ... kern.log says (don't know if it's important): kernel: b44: eth0: Link is down. kernel: NET: Registered protocol family 17 This only happens at bootup and it happens reproducable. I use the standard 2.6.8 debian kernel (Sarge), though if I remember right it also happened with other kernel versions under Sid (I did a complete reinstall with formatting my whole harddrive). Any ideas what causes this? Suggestions or workarounds? BTW: Is there a way one can background the dhclient at boot-up to speed-up dhcp setups? TIA, Jens
pgpjiJo4jS0CH.pgp
Description: PGP signature
