GNOME Bugzilla – Bug 757587
IPv6 default route lingers after device has disconnected
Last modified: 2015-11-20 14:30:28 UTC
Created attachment 314816 [details] NM debug log Attached is a debug log where I perform the steps shown. The version is NetworkManager-1.0.6-7.fc22.x86_64. The bug is that a default route lingers after the device has been disconnected (step #7). It should have been removed. I have several times experienced that this causes problems - IPv6 traffic is sent to some disconnected interface even though it should have been sent to some other interface that has been connected in the meantime. Furthermore, it is clear that NM hasn't lost fully track of the route since it does get removed when NM shuts down (step #9). 0) Initial state: No cable connected, NM not running, no output from "ip -6 r" 1) $ systemctl start NetworkManager 2) $ nmcli general logging level debug 3) connect wired ethernet cable 4) $ ip -6 r 2a02:c0:100:2::/64 dev enp0s25 proto ra metric 100 fe80::/64 dev enp0s25 proto kernel metric 256 default via fe80::3ed9:2bff:fefb:8004 dev enp0s25 proto static metric 100 5) disconnect ethernet cable 6) wait until NM notices and tears down connection 7) $ ip -6 r default via fe80::3ed9:2bff:fefb:8004 dev enp0s25 proto static metric 100 8) $ systemctl stop NetworkManager 9) $ ip -6 r # no output
should be fixed by: master: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c2831875e3a2cf046f8a3b42a971172319c50e99 nm-1-0: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0178baea2c396b9a7a57fe11dc79c93882dffaf7