Comment 7 for bug 704812

Sorry for the delay, here is the promised debug log. I can still easily reproduce this problem.

1) Set IPv6 to auto instead of ignore
2) connect to a (wireless?) network where IPv6 RA works fine (the client gets an autoconfed address and route), but DHCPv4 fails to answer in time (shutdown the server)
3) after DHCPv4 timeout nm disconnects
4) reconnect to the same network using nm-applet
5) this time make sure DHCPv4 works (start the server again)
6) on successful connect you have two IPv6 default routes, one pointing to the LL next-hop from RA (correct) and one pointing to the interface without nexthop (wrong)

It does not happen when
a) the first connection attempt already succeeded
b) IPv6 is set to ignore in the connection profile

Since nm is still not flushing the IPv6 address when the interface goes down I assume it is recording the list of routes present before step 4 (which includes the correct nexthop to the router) and attempts to readd them after step 5, but fails to set the next hop correctly.

Interesting side effect, I have to delete the wrong route three times before it is finally gone. It looks like nm is readding it immediately, but I don't see anything in the debug log. I could not find the debug category where it shows adding routes at all.