Comment 4 for bug 761558
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
What I mean by this is that for most users, switching to IPv6 is a no-op: ISPs will switch, most likely provide v6 addresses from their systems to the CPE, but most local networks for customers will remain IPv4. AFAIK, there are still very few home routers sold with IPv6 support (with the notable exception of the DLink DIR615 at least that I know of).
I hardly think that if you don't know what you're doing, that you'd really be using IPv6 at this time, or need to use it on a local network.
Other equipment was really referring to CPE -- the router your ISP gives you, in other words.
I'm not saying this won't be fixed, just that there's already a way to use IPv6 for a connection even if it's not on by default. I do believe it's discoverable enough, being a separate tab from IPv4, which is always visible when you edit the connection's settings in nm-applet. Another thing to keep in mind is that systems supporting IPv6 (aka, those that didn't get it disabled by manual configuration modifications) should still build IPv6 addresses from router advertisements, since this is not disabled by NM and taken care of by the kernel.
We'll set IPv6 to Automatic by default early in the Oneiric cycle, along with making sure it doesn't block interfaces from coming up. I think this is sufficient to cater for most use cases; whereas changing defaults at this point in the cycle seems to me like risking to introduce issues related to having IPv6, to systems trying to resolve AAAA addresses when they can't (for instance, because their routers don't support it). I tested this relatively early in the cycle, and IIRC it worked just fine.
I understand the importance of exceptional IPv6 support, but I do expect it to be reasonable in its current state for the reasons stated above; which reduces the importance of changing NM's connection defaults at this time (especially considering freeze status and how close we are to release).
Anything I'm missing from the above analysis that would warrant changing this now? I'm open to having my mind changed if there's a compelling reason ;)