Hello, On 29 September 2014 03:35, Christoph Anton Mitterer <cales...@scientia.net> wrote: > Well you have explained that here, but this is nothing that a admin > necessarily reads before upgrading... he would only read it once his > stuff already starts to fail. > So as along as the default is still to have allow-hotplug on eth > interfaces (which is still the case, AFAIK) and as long as there is no > NEWS.Debian entry or other measure to warn people that update their > ifupdown, that it will likely fail with IPv6 and their current setup - > the issue still fully exists and is therefore still as severe (namely > critical) as it was on the first day.
No, no and no. The default is allow-hotplug and auto, which means no DAD waiting. If you chose to change the setting to static, it's your job to ensure it actually works. Allow-hotplug means ‘I don't know and don't want to know and care when this interface comes up, and if it comes up at all, I have nothing that depends on it during the boot-up sequence, maybe I don't have it at all, but when it appears, I want it to be brought up’. If you want your interface to be brought during boot no matter what, don't use allow-hotplug, use auto. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
