On Thu, 2005-04-28 at 12:53 +0200, Martin Steigerwald wrote: > Package: ifplugd > Version: 0.26-2 > Severity: important > > I use ifplugd and guessnet together to have automatic network > configuration for laptops. Usually on boot up when /etc/init.d/ifplugd > is started it will probe for a link beat and when it detects one run > guessnet which then probes for a DSL modem and when that timeouts try > with a DHCP. Usually booting stops until that process is finished > completely so that the network interface is properly setup before > network services are started. This is also the behaviour I observe when > I manually do a "ifdown eth0 ; ifup eth0". It gives me the next shell > prompt, when it finished all those steps and not before. > > But sometimes - I do not yet get when and why - it doesn't wait. In this > case it starts guessnet, but then goes on immediately without waiting > for guessnet to complete the detection of the network environment. This > looks like this:
Well, this is not a bug. ifplugd's purpose is to run as a daemon, and bring up an interface whenever you plug in a cable. This means your setup should also work when you boot your laptop without a cable plugged in, and plug it in some time later - at that time it should do your guessnet work, which in turn does pppoe or dhcp. It won't work, right? So if you solve that problem, you will also solve your original problem ;-). ifplugd calls (by default) ifup <iface>. ifup will use the scripts in /etc/network/if-up.d/ and *that* is where you have to start all services that depend on that interface. This will also work at boot time. I hope that helps. Greetings, Oliver
signature.asc
Description: This is a digitally signed message part
