On 2015-11-18 11:46, Guus Sliepen wrote: [..] >> Indeed, Ubuntu sets use_tempaddr=2 in their sysctl (hence the empty file >> mentioned above) and then when sysctl this custom file the setting is >> reverted and you lose your default... >> >> hmmm, that might actually be affecting this too now I think of it. >> >> But the sysctl stuff should run BEFORE ifupdown comes into play (hence >> setting default+all so that existing and new interfaces get that setting). > > Yes. Maybe it could also have something to do with DAD.
>From my POV DAD does not come into play there, and also the kernel would log it. > I'll try it out with the settings you have and poke around until I find the culprit, > then see how I can have ifupdown work around it. I did not check the code thus maybe it does it already but checking the setting if accept_ra is going to be toggled might be a good thing. Of course if is accept_ra toggle related (losing the default route) then that is clearly a kernel thing, not much ifupdown could do about. Greets, Jeroen
