Hey. Anything new here?
First of all, I'm pretty unhappy with hiding away that bug behind severity "normal"? I mean that issue means, that with the default way of IPv6 used to be set up (i.e. eth0 being allow-hotplug) many services fail to work. So the proper severity by definition is critical as I've set it in the beginning. The only reason for not re-setting it is that I'm tired of these severity-wars. Second,... all this used to work until version 0.7.45, so there is a clear thing which has changed (0.7.45 waits for DAD to complete for 'inet6 static' interfaces) and it should be possible to decide what to do (or revert that change). Now you we've seen that it works with allow-auto, but not with allow-hotplug. To be honest, I've never fully understood what hotplug really does here, and I couldn't find any place where it's documented (at least not in interfaces(5) - probably something that should be done). If that would be documented and if that says "don't use hotplug with static addresses" than one could easily say "okay people have to change their setups". But OTOH it sounds kinda strange that allow-* would have an effect on whether dhcp or static. So what exactly is the difference that it can work with auto but not hotplug, when having DAD enabled in both cases? Is this just a timing issue? Or why does IPv6 not work with -hotplug, while it does with -auto? > More thinking required. Would event-driven init-systems (i.e. systemd) help us here? Anyway, if no solution is found, then either this should be properly documented (with the ideal solution what people should do disable-DAD vs. -auto) or ifupdown should implicitly either disable DAD (probably a bad idea?) or implicitly convert the allow-hotplug to allow-auto. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
