* Mathieu Trudel-Lapierre > That's an option that can be changed by the user, so irrelevant to > supporting IPv6 networks out of the box.
«Plug and Play» is important for most users. > I don't think there are enough IPv6-only networks to warrant shipping > IPv4 as optional by default just yet, to me that's likely to cause > far more pain for the time being. If there's no IPv6 on the network, as is the case for 99%+ of networks today, IPv4 *won't* be made optional by such a change. Either IPv4 or IPv6 must succeed even if neither is marked as "required", and if there's no IPv6 on the network, the succeeding protocol pretty much has to be IPv4. Also, for what it's worth, Microsoft Windows (since Vista, 2006) and Apple Mac OS X (since Lion, 2011) supports IPv6-only networks in their default configuration. With that in mind, it is hard for me to understand what that «far more pain» concern you have is all about. Could you be more specific? Best regards, -- Tore Anderson -- 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
