routes ignored advertised in ipv6 router advertisement packets

[AZ]

I'm using ipv6 on a tun device. My router (a debian system) sends out router advertisements using radvd which are received by my ubuntu machine and used for address generation.
Although the ra's include route information, this is ignored.
The interface uses the fec1::/64 prefix and routing is advertised for fec0::/64.
I cannot add this route to /etc/network/interfaces, as it comes up after vpn is started.

radvdump:

interface tap0
{
 AdvSendAdvert on;

 prefix fec1::/64
 {
 }; # End of prefix definition

 route fec0::/64
 {
  AdvRouteLifetime 30;
 }; # End of route definition

 RDNSS fec1::254
 {
  AdvRDNSSLifetime 10;
 }; # End of RDNSS definition

}; # End of interface definition

rdisc6 ::

 rdisc6 tap0
Soliciting ff02::2 (ff02::2) on tap0...

Hop limit : 64 ( 0x40)
Stateful address conf. : No
Stateful other conf. : No
Router preference : medium
Router lifetime : 30 (0x0000001e) seconds
Reachable time : unspecified (0x00000000)
Retransmit time : unspecified (0x00000000)
 Prefix : fec1::/64
  Valid time : 2592000 (0x00278d00) seconds
  Pref. time : 604800 (0x00093a80) seconds
 Route : fec0::/64
  Route preference : medium
  Route lifetime : 30 (0x0000001e) seconds
 Recursive DNS server : fec1::254
  DNS server lifetime : 10 (0x0000000a) seconds
 Source link-layer address: EE:18:EC:79:D5:2E
 from fe80::ec18:ecff:fe79:d52e

[AZ (m-dev)]

Sry, its tap , not a tun device ;)

[AZ (m-dev)]

%> ip -f inet6 route | grep tap0
fe80::/64 dev tap0 metric 256 expires 21334198sec mtu 1500 advmss 1440 hoplimit 4294967295
fec1::/64 dev tap0 proto kernel metric 256 expires 2592161sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev tap0 metric 256 expires 21334198sec mtu 1500 advmss 1440 hoplimit 4294967295
default via fe80::ec18:ecff:fe79:d52e dev tap0 proto kernel metric 1024 expires 29sec mtu 1500 advmss 1440 hoplimit 64

[Dereck Wonnacott (dereck)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[AZ (m-dev)]

uname -a : Linux charlie 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

[AZ (m-dev)]

It looks like support for this has already been added to the kernel and can be enabled using IPV6_ROUTE_INFO. I'm going to test it.

[AZ (m-dev)]

I set
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
in kernel config add configured sysctl
net.ipv6.conf.<device>.accept_ra_rt_info_max_plen = 128

whichs works fine for me.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[kernel-janitor (kernel-janitor)]

Hi alfonsname,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 235258

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[AZ (m-dev)]

As nobody has enabled
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
nothing has changed regarding this report concerning jaunty.

[AZ (m-dev)]

Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=
MachineType: MEDIONPC MS-7091
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.28-11-generic root=/dev/mapper/system ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare users vboxusers video

[Bernhard Schmidt (berni)]

Any news here? CONFIG_IPV6_ROUTER_PREF is still not set in natty (2.6.38-7.38). Since Debian Squeeze ships with it it should be safe to use.

[Andrew Byrne (andrew-andy)]

Please enable the following options:

CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y

Routers configured according to RFC 6204 must advertise routes using the "Route Information Option" defined in RFC 4191. If desktops/servers running Ubuntu don't support this option, they may fail to route local IPv6 networks in the absence of a default route.

[penalvch (penalvch)]

AZ, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]