© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I just booted the 23 Sep 2010 daily Maverick build and thoroughly tested the network manager. By default, the settings don't match the dialog, but after changing the settings, all works well. What I mean by this is that by default, the IPv6 setting is to ignore. But it doesn't ignore (I got an address). After setting the IPv6 settings to automatic and leaving the 'Require IPv6' checkbox checked, I was still able to get a connection even without IPv6 available. I unchecked the box and all worked. Then I checked the box and my connection failed without IPv6 enabled.
Setting | IPv6 required | IPv6 not required
-------
IPv6 available | IPv4 OK | IPv4 OK
IPv6 not avail | no connection | IPv4 OK
My conclusion is that while the initial settings still allow IPv6 despite what the dialog says, this bug is no longer an issue. Someone can open a bug for the initial settings if it is that bad. If this bug is targeted for Maverick, then it can be closed.
For those who care, I have attached a screenshot of the Maverick network manager settings dialogs.