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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761558
Title:
Default to enabling IPv6 addresses, but set to optional to bring up
devices
To manage
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
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
** Attachment added: Syslog, Oneiric alpha-3, singlestac IPv4, wired
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/+attachment/2258180/+files/test2.oneiric-a3.wired.singlestack.syslog
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: Syslog, Oneiric alpha-3, dualstack, wireless
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/+attachment/2258181/+files/test3.oneiric-a3.wireless.dualstack.syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Okay, now I've tested a bit with the Oneiric Alpha 3 live image.
Highlights:
- The default Wired connection profile now has set the IPv6 mode to
Automatic by default.
- ...however, it behaves as if it is still set to «Disable» and does no
attempt of configuring IPv6.
- DHCPv6 appears broken, any
** Attachment added: Syslog, Oneiric alpha-3, singlestack IPv6, wireless
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/+attachment/2258182/+files/test4.oneiric-a3.wireless.singlestack.syslog
--
You received this bug notification because you are a member of
I also found a crash (probably unrelated to IPv6).
In this syslog, I booted the Live CD on a computer connected to a dual-
stacked network using wired ethernet. As in test #1 above, it connected
only using IPv4, apparently ignoring that the default IPv6 mode was
«automatic». I entered the
* Mathieu Trudel-Lapierre
I've just confirmed it is indeed the case: there is something
wrong in the LiveCD, and we'll definitely fix that.
Great! :-)
After re-reading this, I also got to the same conclusion (and also
with Stephane's careful analysis and testing); IPv4 could
theoretically
On Tue, Jul 26, 2011 at 11:00 AM, Tore Anderson t...@fud.no wrote:
Is that the only concern you have about making IPv4 optional?
It is, although I'm just stating potential issues so we can make an
informed decision. The next step will be to bring this up to the
NetworkManager mailing list; I'd
I agree completely that it is the best if this change is made upstream
so that it will benefit other Linux distributions too!
I actually submitted a bug on NetworkManager in Fedora back in 2009
regarding IPv6 support by default (which was falsely claimed to be
implemented in the release notes of
On Fri, Jul 22, 2011 at 2:46 AM, Tore Anderson t...@fud.no wrote:
If you look closely at the log, you will see that NM does not do anything
at all about IPv6 until I manually change the settings at 15:37:19. Before
that point, the only thing related to IPv6 that is logged at all is from
On Thu, 21 Jul 2011 19:30:34 -, Mathieu Trudel-Lapierre
mathieu...@gmail.com wrote:
Dual-stack and single-stack connections are being tested extensively,
but at this point the default is already (for an automatically created
connection, that is) to have IPv6 at Automatic and optional. This
Dual-stack and single-stack connections are being tested extensively,
but at this point the default is already (for an automatically created
connection, that is) to have IPv6 at Automatic and optional. This
doesn't apply to connections created by clicking the Add button in nm-
connection-editor
I just tested Oneiric alpha-2, and there has been no improvement. After
booting the Live DVD, it ultimately fails to connect to the network
(after repeated attempts), due to the lack of DHCPv4 responses from the
network. This happens to be because the default «Wired connection 1»
profile has 1)
Assigning to Matt Trudel who's working on changing the default.
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager-applet (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761558
Title:
Default to enabling IPv6 addresses, but set to
I'm reopening this bug, as Oneiric Alpha 1 does not appear to be able to
connect to IPv6 networks in its default out-of-the-box configuration.
See attached (unedited) syslog for a log of the process.
The network in question is managed by an AVM FRITZ!Box 7390 DSL router,
which uses SLAAC for IPv6
Closing as Fix Released, the default for NM 0.9 (which is now in
Oneiric) is to enable IPv6 automatically, although it's optional to
bring up interfaces.
** Changed in: network-manager-applet (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a
Mathieu,
I did not mean to insist on this becoming part of Natty. While that
would have been a good thing, I can understand that the release cycle
has progressed too far now.
However, I wanted to object to your argument which I interpreted as
essentially: «it does not matter if IPv6 is supported
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
32 matches
Mail list logo
