Well, you'd have to configure DNS separately to make things work; and perhaps NM wasn't quite doing the right thing with the address and default route in that case, back then...
Since, there's been a lot of work on NM IPv6 support. I'm not sure how you configure your settings for site-local (well, actually ULA now I guess, since site-local has since been deprecated). Please add more information so that we can help you out. AFAIK, the most practical way to deal with this is to hand out the ULA addresses with DHCP or some other configuration. You'd need at least the subnet ID to set somehow -- see http://4sysops.com/archives/ipv6 -tutorial-part-7-zone-id-and-unique-local-ipv6-unicast-addresses/. How would you set these up otherwise? I don't think configuring ULA with NM and always using 0's for the subnet would be a great idea. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/607992 Title: ipv6 autoconfiguration does not provide a site-local address Status in “network-manager” package in Ubuntu: Incomplete Bug description: Binary package hint: network-manager Description: Ubuntu 10.04.1 LTS Network-manager 0.8-0ubuntu3 Everything in ip6tables set to ACCEPT #ip6tables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Tried it on two different computers with up-to-date Ubuntu 10.04 connected to the same "Freebox" router, one using wifi, the other using ethernet. I decided to activate ipv6 in network-manager for my running interface; I chose automatic mode and the connection to sites like ipv6.google.com worked fine and ifconfig showed two addresses: a link- local one and an Internet one: inet6 addr: abcd:ef12:134:534:8488:1abe:335:2ef/64 Scope:Global inet6 addr: fe80::8488:1abe:335:2ef/64 Scope:Link but no address in fec0:: with scope site. This is rather annoying since it means that to communicate on the local network, I must use the global address. The behavior I expected was for network-manager to also configure a site local address if fec0:: I managed to configure the network manually by modifying /etc/network/interfaces and now nm-applet doesn't show up but I suppose this is normal. I don't know if I shouldn't file a separate bug but here goes: I also tried manual configuration for ipv6 and added these fields in the manager: abcd:ef12:134:534::aaaa / 64 fe80::aaaa / 64 fec0::aaaa / 64 but with that, the site-local (fec0::aaaa) address works but not the global one. When I do "ping6 ipv6.google.com", I get "connect: Network is unreachable" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/607992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
