Comment 5 for bug 988183

In Progress/High. It's kind of annoying, if only just for the log entries. All of the connection/disconnection states depend a lot on the RA interval used, but that's still also quite annoying, and the fix is clearly safe (as it's a new route with a different metric, so we don't risk breaking stuff too much).

I'm sponsoring this to -proposed shortly, just need to apply the debdiff, quickly test that it's properly adding the routes, and we should be ok. It will need to be carefully tested to make sure the added metric doesn't clash with wireless/wired coexistence: basically, we need to make sure that on a system connected to both wired and wireless that has ipv6 on both interfaces, the wireless default v6 route added by NM needs to have a lower priority (higher metric) than the default ipv6 route added by NM for the wired interface. This will make sure ethernet remains "preferred" in the event that these networks are in fact different, and I'm a little worried that the upstream patch breaks this.