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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607992 Title: ipv6 autoconfiguration does not provide a site-local address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/607992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
