Ubuntu
network-manager package

NM fails to set IPv6 default route when IPv6 details entered manually

Bug #856209 reported by Robie Basak on 2011-09-22

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	libnl3 (Ubuntu)	Fix Released	High	Mathieu Trudel-Lapierre
	network-manager (Ubuntu)	Fix Released	High	Mathieu Trudel-Lapierre

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:

Tags:

Related branches

lp:~cyphermox/ubuntu/oneiric/libnl3/lp856209

Merged into lp:ubuntu/oneiric/libnl3

Adam Conrad (community): Approve on 2011-10-06

Ubuntu Sponsors: Pending requested 2011-10-06

lp:ubuntu/oneiric/libnl3

lp:ubuntu/oneiric/network-manager

Revision history for this message

Robie Basak (racb) wrote on 2011-09-22:

Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
IfupdownConfig.txt Edit (309 bytes, text/plain; charset="utf-8")
IpAddr.txt Edit (1.1 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (594 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (380 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (177 bytes, text/plain; charset="utf-8")
NetDevice.vboxnet0.txt Edit (195 bytes, text/plain; charset="utf-8")
NetDevice.virbr0.txt Edit (207 bytes, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (415 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (1.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (182 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (128.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-09-22:

Confirmed/High; I was able to verify this failure before.

Changed in network-manager (Ubuntu):
status:	New → Confirmed
importance:	Undecided → High

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-09-22:

The same default route should work if you point to the same device on the local link, with link-local addresses. Could you try this out?

Revision history for this message

Robie Basak (racb) wrote on 2011-09-22:

I've repeated my steps but this time I put the link-local address of the router in the gateway column. I get the same result - no IPv6 default route. I can ping6 -Iwlan0 <router_link_local_address> and that works OK.

Mathieu Trudel-Lapierre (cyphermox) on 2011-09-22

Changed in network-manager (Ubuntu):
assignee:	nobody → Mathieu Trudel-Lapierre (mathieu-tl)

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-10-03:

Some issue with libnl3, although it's still unclear why exactly that fails. I'm working on it.

Changed in network-manager (Ubuntu):
status:	Confirmed → In Progress

Mathieu Trudel-Lapierre (cyphermox) on 2011-10-05

Changed in libnl3 (Ubuntu):
status:	New → Triaged
importance:	Undecided → High

Mathieu Trudel-Lapierre (cyphermox) on 2011-10-06

Changed in libnl3 (Ubuntu):
status:	Triaged → In Progress
assignee:	nobody → Mathieu Trudel-Lapierre (mathieu-tl)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-10-06:

This bug was fixed in the package network-manager - 0.9.1.90-0ubuntu3

---------------
network-manager (0.9.1.90-0ubuntu3) oneiric; urgency=low

  * debian/patches/nl3-default-ip6-route.patch: set destination for default
    gateway as an all-zero in6_addr rather than NULL (since libnl3 requires
    setting a destination). (LP: #856209)
  * debian/patches/manual-ip6-manager.patch: provide an unused but set ipv6
    manager object so manual routes are torn down when a device is deactivated.
  * debian/patches/dhcpv6-duid-support.patch: update to avoid spewing out debug
    messages as warnings/info.
-- Mathieu Trudel-Lapierre <email address hidden> Thu, 06 Oct 2011 15:03:22 -0400

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-10-06:

This bug was fixed in the package libnl3 - 3.0-1.1ubuntu1

---------------
libnl3 (3.0-1.1ubuntu1) oneiric; urgency=low

  * debian/patches/lp854719_single_path_fixes.patch: if dealing with a single
    nexthop object for a route, apply the destination and interface directly to
    the underlying route object. (LP: #856209)
-- Mathieu Trudel-Lapierre <email address hidden> Wed, 05 Oct 2011 13:35:04 -0400

Changed in libnl3 (Ubuntu):
status:	In Progress → Fix Released
Changed in network-manager (Ubuntu):
status:	In Progress → Fix Released

Revision history for this message

Robie Basak (racb) wrote on 2011-10-07:

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!

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #854719

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntunetwork-manager package

NM fails to set IPv6 default route when IPv6 details entered manually

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
network-manager package