FYI, The Fedora project has decided to consider IPv6-only network attachment failing out-of-the-box a release blocker for Fedora 17. And the required patches to fix that is hitting the NetworkManager upstream code as we speak. One significant commit is here:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=4abb300c967705b536cb11303f1c8296a6ca32f0 Dan Williams also just informed me that the patch in https://bugzilla.redhat.com/attachment.cgi?id=569078 will also be applied after having been adapted not to apply to WiMAX, mobile broadband, and Bluetooth DUN (because those connection types currently don't support IPv6 anyway). I'll post the commit ID as soon as I see it. That's is all the pieces missing for Ubuntu, as far as I can tell. I see from the 0.9.3.995+git201203081848.bba834f-0ubuntu1 upload that the network-manager package in Precise is far from frozen, so I'm still hoping that the upstream support for IPv6-only networks, as well as the Fedora project's decision, will persuade you to include the two patches (or simply update to a more recent git snapshot) before Precise goes out the door. Tore -- 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/761558 Title: Default to enabling IPv6 addresses, but set to optional to bring up devices Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager Ubuntu 11.04 Beta 2 does not support IPv6 networks out of the box. It really should. (Microsoft Windows have had this support since Vista.) The remaining IPv4 addresses are depleting fast - as of yesterday, there are no more IPv4 addresses to be had in the Asia-Pacific region, a situation which soon will happen in Europe and North America too - likely before the end of the year. It is therefore urgent that IPv6 networks are supported out of the box - average end users cannot be expected to jump through hoops in order to get a working network connection. Fortunately, all the necessary support is found in the NetworkManager source code - it is just a matter of changing the defaults so that both IPv4 and IPv6 networks are supported equally well, as well as hybrid IPv4+IPv6 dual-stack networks. These are the defaults that need to change in the standard connection profile: Require IPv4 addressing for this connection to complete: OFF IPv6 Method: Automatic Require IPv6 addressing for this connection to complete: OFF I've attached a log from when I first activated a connection to a IPv6 wireless network (which failed), and then another attempt after having modified these settings (which succeeded). Tore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/761558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp