Hide Forgot
Description of problem: NetworkManager does not appear to set a default route when dhcp is selected to configure an ipv6 connection. I have setup a pure ipv6 environment over wireless using dhcp6, disabled stateless autoconfig and enabled dhcp6 on the client. With stateless autoconfig, a default route is set properly, however I am unable to get a name server unless I run dhcpv6 or run a dual stack and perform dns lookups over ipv4. No default router is provided via dhcp6 because it was decided in RFC3315 that a default router field would be unnecessary due to the neighbor discovery and router advertisement features of the ipv6. Version-Release number of selected component (if applicable): 0.8.1-10.git20100831.fc14.i686 How reproducible: Seems to happen every time. Steps to Reproduce: 1. Configure a lan or wlan connection with networkmanager that has ipv4 totally disabled and uses dhcp for ipv6 configuration. 2. Obtain an ipv6 address via DHCP and NOT via stateless autoconfig 3. type ip -6 route and note that there is no default gateway set, only a default route through the interface with no gateway address. Expected results: I would expect NetworkManager to perform router discovery and accept a default route for a pure ipv6 dhcp managed configuration. Additional info: Manually configuring the wlan0 interface Running dhclient -6 wlan0 by hand obtains an address as expected and a default route is set. Also, if I enable accept_ra (accept_ra_defrtr is already enabled) I will eventually get a default route when the router sends the next RA.
DHCPv6 does not have the capability of sending a gateway; it's simply not in the standard. There are draft standards for it, but they are not implemented. DHCPv6 alone cannot provide complete, routable IPv6 infrastructure. Instead, you need to enable router advertisement and set the "managed" or "otherconf" bit in the RA. That will provide the default router via RA as well as additional DHCP configuration values. Either way, to get routable addresses, you need RA. That's the only way you can get a default router with IPv6.
Dan, you misunderstand what I am saying. I am saying I get my ip6 address via dhcp, however router advertisements are being sent by my router. Here is the config from my router: rtr0-edge-home#show run int vlan1 Building configuration... Current configuration : 376 bytes ! interface Vlan1 ip address 172.31.1.254 255.255.255.0 no ip redirects no ip proxy-arp ip flow ingress ip pim sparse-mode ip nat inside ip virtual-reassembly in ipv6 address FE80:470:E33B::1 link-local ipv6 address 2001:470:E33B::1/64 ipv6 enable ipv6 nd prefix 2001:470:E33B::/64 ipv6 nd other-config-flag ipv6 nd router-preference High no ipv6 redirects end It is clearly sending RAs. Networkmanager is telling my kernel to ignore them. I get my ip6 address via dhcpd6, however the RAs from my router are being ignored.
Yes, but do you have IPv6 set to "Automatic (DHCP only)" or "Automatic"? If the former, NetworkManager is doing exactly what you told it to do (ignore RA and use DHCPv6 instead). If the latter, than that's a bug (one I've never seen).
Matt, which IPv6 addressing mode are you using there, and can you grab /var/log/messages output for me?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping