On Wed, Nov 18, 2015 at 11:28:49AM +0100, Jeroen Massar wrote: > > It's not dropping your SQL tables or blowing up your house, so: > > > > important > > a bug which has a major effect on the usability of a package, > > without rendering it completely unusable to everyone. > > Well actually.... there are folks with IPv6 only connectivity (or IPv4 > behind NAT or worse CGN) and no KVM access (which is silly but still) > thus they would lose access to the host if it would restart.
I agree, and if anyone is using IPv6-only connectivity I would expect it to be you :) > There are then also people who manage their home heater system with it > and thus won't be able to access that remotely.... thus it could blow up > your house ;) Yes, but even if ifupdown works you cannot assume that your network works. Severity critical is for when one package starts overwriting files from another package, or something else that breaks the OS. But if the package just doesn't work it's not "critical" for Debian, even though it might be for a user who depends on it. > >> See Ubuntu bug report here: > >> https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098 > > > > Did you try this on a Debian system or on Ubuntu? > > Debian stable 0.7.53.1, I avoid Ubuntu like a plague :) Ok. > > Then I can try it out in a VM and try to find the cause. > > Awesome, please do. I would btw not be surprised if this is related to > having accept_ra set to 0 in sysctl as it should be for server systems. [...] Aha, that might indeed affect things. Thanks for providing the details, that will help find the problem much quicker :) > 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. 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. -- Met vriendelijke groet / with kind regards, Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
