I don't think that's going to completely solve the problems with IPv6 and NM, unfortunately. It seems that when NM doesn't get a router advertisement for IPv6 in a relatively short timeframe, it fails the entire connection, even if it got an IPv4 address. Where that ties into this bug is that if (by some miracle) NM got the router advertisement in enough time, it wasn't flushing the configuration when the interface went down and the *next time* the interface came up, problems would ensue - and the problem would seem to change faces depending on whether a router advertisement hit the listening window again. Sometimes you would seem to have a valid IPv6 config that worked and sometimes you would seem to have a valid IPv6 config that didn't.
The problem is, this bug doesn't define the problem well enough anymore. Right now, I have IPv6 set to "Ignore" for my home network even though my router still sends out IPv6 advertisements. I still get an IPv6 address for the interface, though, and it's a crapshoot whether the configuration will actually work. If I set NM to "Automatic" for the IPv6 on this connection, it most often fails because a router advertisement does not get through in the brief window that NM is actually listening for one. The real problem is that IPv6 is unreliable in NM, *period*, and it's not always possible to know what your network setup currently is with it. -- IPv6 configuration is not flushed when interface goes down https://bugs.launchpad.net/bugs/215497 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
