Hello, On 10 July 2014 15:27, Harald Dunkel <[email protected]> wrote: >>> Come on, does this really matter? >> It does indeed.
> Sorry to say, but it doesn't. The current configuration of > other hosts or services in a network is sometimes unpredictable. > Esp. for IPv6 in a foreign LAN there is a high probability that > some feature is not configured correctly, that there is SLAAC > instead of statefull DHCP, etc. That's not true. If you have unpredictable environment, you shouldn't have a fixed configuration at boot time. You should either have a number of different configuration profiles and fire them up manually with ifup eth0=home, or configure guessnet to do that for you. >>> Point is that the Debian host got stuck at boot time >>> without any way out. This is fatal. >> Probably, that's a bug in dhclient. It should time out and background >> itself. > If you think that ifupdown should block the boot process > until dhclient returns, then please reassign this ticket. There used to be a slightly different dhclient configuration for a while before wheezy, and I've got a lot of complaints, so I had to revert that back. Ifupdown should definitely wait for the DHCP process to finish successfully. Actually, what we have currently, when dhclient goes to the background after a while, is not quite right, as ifupdown thinks that it's actually done, but it's not. If you have any real ideas which could help to improve the situation, I'd be happy to hear them. -- Cheers, Andrew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
