dmesg full of "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

Bug #1065974 reported by Christoph Settgast
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I am using Ubuntu Server 12.04.1 LTS and since IPv6 RAs are enabled on wired connection, the message "ICMPv6 RA: ndisc_router_discovery() failed to add default route" fills dmesg.

The default route is being set nontheless:

2001:638:a000:4104::/64 dev eth0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
default via fe80::1 dev eth0 metric 1024

/etc/network/interfaces looks like this:

# The primary network interface
auto eth0
iface eth0 inet static
        address 131.188.31.189
        netmask 255.255.255.0
        gateway 131.188.31.1
        dns-nameservers 131.188.0.11 131.188.0.10
        dns-domain informatik.uni-erlangen.de
        dns-search informatik.uni-erlangen.de
iface eth0 inet6 static
        address 2001:638:a000:4104::189
        netmask 64
        gateway fe80::1
        dns-nameservers 2001:638:a000:1053:53::1 2001:638:a000:1053:53::2

NetworkManager is not installed, so I don't think its a dublicate of #988183

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-virtual 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-virtual 3.2.28
Uname: Linux 3.2.0-31-virtual x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Okt 4 23:10 seq
 crw-rw---T 1 root audio 116, 33 Okt 4 23:10 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Oct 12 15:12:44 2012
HibernationDevice: RESUME=UUID=f3f34eb5-dc4d-47b9-b67e-6938afa8a07a
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
MachineType: Bochs Bochs
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-virtual root=UUID=07c76f05-3330-4c30-b1f5-488a08024a0d ro
ProcModules:
 floppy 70365 0 - Live 0x0000000000000000
 lp 17799 0 - Live 0x0000000000000000
 parport 46562 1 lp, Live 0x0000000000000000
 psmouse 97362 0 - Live 0x0000000000000000
 serio_raw 13211 0 - Live 0x0000000000000000
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-virtual N/A
 linux-backports-modules-3.2.0-31-virtual N/A
 linux-firmware 1.79.1
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

Revision history for this message
Christoph Settgast (csett86) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Christoph Settgast (csett86) wrote :

The bug exists with 3.6.0-030600-generic #201209302035 as well. I have changed the tag accordingly.

I have noticed on another machine: If I remove the gateway line for IPv6 configuration, the message disappears. Maybe this helps.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Christoph Settgast (csett86) wrote :

I did further testing: The message went away with both current Ubuntu kernel (3.2.0-31-virtual) and mainline kernel (3.6.0-030600-generic #201209302035) on my machine as well, once I removed the IPv6 gateway configuration in /etc/network/interfaces.

/etc/network/interfaces:
iface eth0 inet6 static
        address 2001:638:a000:4104::228
        netmask 64

Hope this helps.

Revision history for this message
LaMont Jones (lamont) wrote :

I believe that this happens because the config (/proc/sys/net/ipv6/conf/all/accept_ra_defrtr) says to accept a default route, and you have one specified in /etc/network/interfaces, and therefore the advertised default route fails to get added to the routing table.

It would be a good thing if the logged error (1) said what it was trying to add as the default route, and (2) was rate limited, and (3) pointed at accept_ra_defrtr

Having ifup turn off accept_ra_defrtr when it adds a default route might be a good thing, too.

Just my thoughts.

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

Other bug subscribers

Remote bug watches

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