desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #30352
[Bug 856209] Re: NM fails to set IPv6 default route when IPv6 details entered manually
Mathieu,
This seems to work - thanks!
In testing I noticed a couple of things that I think are worth
mentioning:
1) I'm using the same static IP (IPv4 and IPv6) on both wired and
wireless - this way I can switch from wired to wireless and back without
losing existing connections. I've noticed that with IPv6 I sometimes end
up with the interface stuck in a "dadfailed" state if I switch over by
briefly having both interfaces on the same IP. To clear this I have to
reconnect in NM. It would be nice if this were cleared automatically,
but I realise that I'm probably the only one doing this!
2) When I am on wireless and add wired, I end up with two default
gateways (but everything still works fine). But when I'm on wired and
add wireless, the wireless default gateway does not get added until I
disconnect wired. Neither wired nor wireless are on automatic. This
isn't causing a routing problem; it just seems odd to me that the
behaviour isn't symmetrical.
I don't think that either of these is a bug. With the update we no
longer have a regression over Natty functionality IMO.
Your help is much appreciated!
--
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/856209
Title:
NM fails to set IPv6 default route when IPv6 details entered manually
Status in “libnl3” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
I have also reproduced this bug booting from the beta1 live DVD. Steps
to reproduce:
1. Connect to a wireless network. Mine just presents a standard connection using IPv4 DHCP only. No DHCPv6 or SLAAC is available.
2. Disconnect from the wireless network (by choosing Disconnect from the network indicator)
3. Edit Connections (from the network indicator)
4. Set the connection that has just been connected to not connect automatically.
5. Add IPv6 manual settings. Mine are 2001:8b0:XXX::3, prefix 64, gateway 2001:8b0:XXX::1, nameservers 2001:8b0::2020,2001:8b0::2021.
6. Save and reconnect to the network
Expected behaviour: default route of 2001:8b0:XXX::1 should be added and I should have both IPv4 and IPv6 connectivity.
Actual behaviour: IPv6 default route missing but otherwise IPv6 configured. IPv4 connectivity OK.
Output of ip -6 route show:
2001:8b0:XXX::/64 dev wlan1 proto kernel metric 256
fe80::/64 dev wlan1 proto kernel metric 256
Workaround: add the IPv6 default route by hand.
This happens on both my main machine (up-to-date on this morning's
oneiric) and a spare machine I tested with the beta1 ISO. Details
above are from the spare machine. I ran ubuntu-bug on my main machine
so the attachments reflect that.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Sep 22 09:37:15 2011
IpRoute:
default via 217.169.15.241 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
217.169.15.240/29 dev wlan0 proto kernel scope link src 217.169.15.243
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to oneiric on 2011-09-03 (18 days ago)
WpaSupplicantLog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/856209/+subscriptions
References