[Touch-packages] [Bug 1773041] [NEW] IPv6 Default Route is "static" Instead of "ra", IPv6 Eventually Stops Working
Public bug reported: I have NM (1.2.6-0ubuntu0.16.04.2) on my eth0 interface. The IPv6 setup is "Automatic" (via the NM GUI). When first starting up (or if I manually run "nmcli connection up Ethernet") I have IPv6 connectivity, as NM will hear my router's RA and assign a default route via the router's advertised link-local address: default via fe80::4cf4:93ff:fec3:321 dev eth0 proto static metric 100 pref medium The problem comes some time later when my router (Google WiFi) for some reason will change its link-local address, and by extension, the IPv6 default route. I don't know why this happens, but I do know the router will send that new LL default address in response to Router Solicitations (which this box generates, BTW), and which I've verified via "traceroute"- yet NM will ignore the new IPv6 default route and continue to use whatever value it got when booting (or from "nmcli connection up"). At this point I have no external IPv6 connectivity. Even if I delete that default route and manually re-assign it (and even using the "ra" vs. "static" designation) when the router sends another RA NM replaces the default route, and with the OLD bad address. Please fix NM so that it pays attention to the RAs that routers send. Apparently I can't manually assign a default route (which can also be "::") and also have "Automatic" or "Automatic, Addresses Only" for the address selection (I need DHCPv6 to run, I don't want to manually assign an IPv6 address). Trying to add "gateway=" to the [ipv6] config section of /etc/NetworkManager/system- connections/Ethernet is ignored. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1773041 Title: IPv6 Default Route is "static" Instead of "ra", IPv6 Eventually Stops Working Status in network-manager package in Ubuntu: New Bug description: I have NM (1.2.6-0ubuntu0.16.04.2) on my eth0 interface. The IPv6 setup is "Automatic" (via the NM GUI). When first starting up (or if I manually run "nmcli connection up Ethernet") I have IPv6 connectivity, as NM will hear my router's RA and assign a default route via the router's advertised link-local address: default via fe80::4cf4:93ff:fec3:321 dev eth0 proto static metric 100 pref medium The problem comes some time later when my router (Google WiFi) for some reason will change its link-local address, and by extension, the IPv6 default route. I don't know why this happens, but I do know the router will send that new LL default address in response to Router Solicitations (which this box generates, BTW), and which I've verified via "traceroute"- yet NM will ignore the new IPv6 default route and continue to use whatever value it got when booting (or from "nmcli connection up"). At this point I have no external IPv6 connectivity. Even if I delete that default route and manually re-assign it (and even using the "ra" vs. "static" designation) when the router sends another RA NM replaces the default route, and with the OLD bad address. Please fix NM so that it pays attention to the RAs that routers send. Apparently I can't manually assign a default route (which can also be "::") and also have "Automatic" or "Automatic, Addresses Only" for the address selection (I need DHCPv6 to run, I don't want to manually assign an IPv6 address). Trying to add "gateway=" to the [ipv6] config section of /etc/NetworkManager/system- connections/Ethernet is ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1773041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager
I believe I am affected by this issue as well. I have a Google WiFi device as a router, and everything works well for the first few days, with the link-local address used on the Google WiFi's RA used as the IPv6 default route. After a couple of days however, the Google WiFi device changes its link- local address (for some reason) on the LAN subnet, and although an RA goes out with this new link-local address, NetworkManager still hangs onto the old default route (which is marked "static" as well) and as such I lose IPv6 connectivity to the outside world. I have to run "nmcli conn up Ethernet" to force NM to delete the old default route and use a the new one. Also, if I manually "ip -6 replace default ..." leaving the line otherwise intact as it comes from NM, changing only "proto static" to "proto ra", as soon as the Google WiFi sends another RA, NM re-writes the default as "proto static"- yet does NOT update the actual "via" link-local address to the one the RA came in on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
