This might be a workaround: Set NM IPv6 to "Ignore". After IPv4 is up (so in an if-up.d script, if you like), issue ip -6 link set DEV down ip -6 link set DEV up where DEV is eth0 or wlan0 or whatever. This will not take down the IPv4 network, but will put the IPv6 stack for that device back into a basic "wait and see" mode, where it should catch the next radvd broadcast.
It seems to work on my LAN, but this is only 3 machines... -- IPv6=automatic breaks IPv4 https://bugs.launchpad.net/bugs/284874 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