Ubuntu
network-manager package

NM fails to add IPv6 routes with netlink errors

Bug #832045 reported by Mathieu Trudel-Lapierre
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

NM appears to work properly and does give me an IP address, but there are error messages indicative of something wrong in adding routes:

Aug 23 09:08:11 artemis NetworkManager[1050]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Aug 23 09:08:11 artemis NetworkManager[1050]: <warn> Failed to add route Object not found
Aug 23 09:08:11 artemis NetworkManager[1050]: <error> [1314104891.882457] [nm-device.c:1782] dhcp6_start(): (wlan0): failed to add IPv6 multicast route: Object not found
Aug 23 09:08:15 artemis NetworkManager[1050]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed
Aug 23 09:08:16 artemis NetworkManager[1050]: <warn> Failed to add route Missing attribute
Aug 23 09:08:16 artemis NetworkManager[1050]: <error> [1314104896.421195] [nm-system.c:1036] nm_system_replace_default_ip6_route(): (wlan0): failed to set IPv6 default route: -1
Aug 23 09:08:16 artemis NetworkManager[1050]: <info> Policy set 'cyphermox.net' (wlan0) as default for IPv6 routing and DNS.
Aug 23 09:08:16 artemis NetworkManager[1050]: <info> nameserver 'xxxxxxxxx'
Aug 23 09:08:16 artemis NetworkManager[1050]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed
Aug 23 09:08:17 artemis NetworkManager[1050]: <warn> Failed to add route Missing attribute
Aug 23 09:08:17 artemis NetworkManager[1050]: <error> [1314104897.429011] [nm-system.c:1036] nm_system_replace_default_ip6_route(): (wlan0): failed to set IPv6 default route: -1

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I think this is likely due to small bits missing in the patch to use libnl3.

Revision history for this message
Robie Basak (racb) wrote :

I also see this. My symptom is an IPv6 failure caused by a missing default route. In /var/log/syslog I see:

Sep 19 09:24:30 mal NetworkManager[1565]: <warn> Failed to add route Missing attribute
Sep 19 09:24:30 mal NetworkManager[1565]: <error> [1316420670.859276] [nm-system.c:1036] nm_system_replace_default_ip6_route(): (wlan0): failed to set IPv6 default route: -1
Sep 19 09:24:30 mal NetworkManager[1565]: <info> Policy set 'XXXXXXX' (wlan0) as default for IPv6 routing and DNS.
Sep 19 09:24:30 mal NetworkManager[1565]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 19 09:24:30 mal NetworkManager[1565]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.

If I add an IPv6 default route manually using this, then it works:
    sudo ip -6 route add ::/0 via XXX metric 0

IPv4 works fine.

My configuration: I have static addresses against this wireless network for both IPv4 and IPv6. I'm using network-manager 0.9.0-0ubuntu3.

This worked fine for me in Maverick. I haven't tested Natty.

Unless IPv6 works for someone else in a more automatic mode, it seems to me that this is a regression making IPv6 unusable.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Well, I had opened this bug due to a different issue.

I'll close this as Fix Released now because AFAICT, everything is fine on the system here. It definitely is here, IPv6 is absolutely usable in DHCPv6 (and really should be in SLAAC too).

Robie, please open a separate bug using 'ubuntu-bug network-manager' and include the output of 'ip -6 route list' before making any changes to the connection so we can confirm exactly what's going on. Maybe it's specific to some settings I'm not using here. (although we really should have caught this in the testing that was done prior to uploading the patches).

Note that the error message "missing attribute" is kind of normal and should be covered by a second pass of trying to replace the default route.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Robie Basak (racb) wrote :

I have created bug 856209.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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