The second part is now committed, here:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b9511f6e98429c01b741754bc58795bf59f693e
Tore
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
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:
Hi Mathieu,
On dual-stack networks, which remains the norm rather than ipv6-only so
far,
The norm so far is without question IPv4-only, which outnumbers anything
including IPv6 by an enormous amount. According to Google, IPv4-only is the
case for about 99.5% of users world-wide (see
On dual-stack networks, which remains the norm rather than ipv6-only so
far, and usually still require IPv4 to gain access to a large part of
the internet, having IPv4 optional will mean the connection may still be
brought up with just IPv6. Then people will wonder what is going on and
file bugs
* 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
That's an option that can be changed by the user, so irrelevant to
supporting IPv6 networks out of the box. 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.
Definitely
Great!
However, is IPv4 success still required in order to bring up interfaces?
If so, that still needs to change before you can say that Ubuntu truly
supports IPv6 networks out of the box.
Tore
--
You received this bug notification because you are a member of Desktop
Packages, which is
This should have been closed again some time ago -- the default since
Oneiric is to try IPv6 in Automatic mode; although its success is not
required to bring up interfaces.
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
I reopened the bug because the change made in network-manager
0.9.0-0ubuntu2 breaks connections using mobile broadband devices (the
connections fail silently). Notified the NM mailing list about the issue
on the patch from Tore.
* debian/patches/lp761558_default_ip6_setting_auto.patch: default to
This bug was fixed in the package network-manager - 0.9.0-0ubuntu2
---
network-manager (0.9.0-0ubuntu2) oneiric; urgency=low
* debian/patches/lp761558_default_ip6_setting_auto.patch: default to AUTO for
IPv6 method if the setting is missing (e.g. default new connection for new
** Branch linked: lp:ubuntu/network-manager
--
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
This bug was fixed in the package network-manager-applet -
0.9.0-0ubuntu2
---
network-manager-applet (0.9.0-0ubuntu2) oneiric; urgency=low
* debian/patches/default-ipv6-auto.patch: don't expect a missing DHCPv6 method
value to mean Ignore, when it now means use DHCP. (LP:
I finally could verify/reproduce the issues you were seeing with
connections initially never start DHCPv6 even if they are showing Auto
for the method -- there is another part of network-manager which uses
the assumption that a missing method (e.g. for a new device connection,
which typically
13 matches
Mail list logo
