When configured to use DHCPv6, NetworkManager will accept the address and DNS server supplied by the router, but will not set the default route. Reproducible: Always Steps to Reproduce: 1. Connect to a DHCPv6-enabled router. 2. Right-click applet and go to "Connection Information" Actual Results: "Default route" shows "::" and IPv6 access doesn't work. Expected Results: "Default route" should show something that's RFC-compliant for a routing address. Using dhclient.
Created attachment 299187 [details] emerge --info
Have you tried to disable the ifnet plug-in? Edit /etc/NetworkManager/nm-system-settings.conf and change the following: plugins=ifnet,keyfile to plugins=keyfile If it's working properly then, the problem is caused by ifnet. And I'll see what's going on. Thanks.
I can't get the interface to raise at all like that. It won't even attempt to connect.
I believe this bug has been fixed in NetworkManager 0.9.6: https://bugzilla.gnome.org/show_bug.cgi?id=676317 commit 8a059b1496448ffaa1178b35887883e1cf87800b Author: Pavel Šimerda <psimerda@redhat.com> Date: Wed May 23 19:07:39 2012 +0200 ip6: add default gateway to NMIP6Config (bgo #676317) Bug #676317 describes the following error: NetworkManager[30151]: <error> [1337348764.559121] [nm-system.c:1121] nm_system_replace_default_ip6_route(): (eth1): failed to set IPv6 default route: -7 The above error is caused by NetworkManager assuming default gateways belong to addresses but failing to setup default gateways for addresses learned through DHCPv6. This commit doesn't fix the fundamental issue but can be viewed as an ugly workaround that gets IPv6 connection up and running. It doesn't fix the fundamental flaw of binding gateways to IP addresses. They are configured separately in IPv6 and NM should use lifetimes and allow default gateway reconfiguration.
Marking as fixed then. William, please reopen if the problem still occurs with networkmanager-0.9.6.4
