> 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 doesn't necessarily have an associated file on the > filesystem) means "Ignore", which is obviously false at this point.
I think patch is what you need (maybe the last chunk only): http://mail.gnome.org/archives/networkmanager- list/2011-August/msg00063.html > I also noted that there is such a check in nm-applet which would write > "Ignore" and then include the assigned IPv6 addresses if the above is > fixed, so now we have two separate tasks for network-manager and > network-manager-applet. I'm working on both, and they should be fixed > shortly. Ok, thanks! I haven't looked into the GUI stuff at all. > As for your crash, please try to reproduce it with apport enabled. You > should see a file in /var/crash about this crash; we'd need this opened > as a separate bug in order to be able to debug what is causing it. This > is just so we can track each issue separately and know what is fixed and > what isn't. I'll do my best, but I can't promise you I find the time before next week, I'm going away from Friday, and I've got a really busy schedule today and tomorrow. 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: Triaged Status in “network-manager-applet” package in Ubuntu: Triaged 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
