Comment 2 for bug 591869

I removed the needs-kernel-logs and needs-upstream-testing tags because I don't think there's anything that needs to debugged or checked upstream. I'm not reporting a software failure; I'm just asking for a config option to be turned on. (If there's a more appropriate place to make this kind of request, please let me know.)

Just to confirm, I tested to make sure that the latest Maverick kernel (2.6.35-2.2 now) does not have 6rd support:

root@maverick:~# uname -a
Linux maverick 2.6.35-2-generic #2-Ubuntu SMP Tue Jun 8 19:15:10 UTC 2010 i686 GNU/Linux
root@maverick:~# grep 6RD /boot/config-$(uname -r)
# CONFIG_IPV6_SIT_6RD is not set
root@maverick:~# ip tunnel add sit1 mode sit local 10.100.100.1 ttl 64
root@maverick:~# ip tunnel 6rd dev sit1 6rd-prefix 2001:0db8::/32 6rd-relay_prefix 10.0.0.0/8
ioctl: Invalid argument
root@maverick:~#

If I grab the 2.6.35-2 source package, I can add CONFIG_IPV6_SIT_6RD=y to debian.master/config/config.common.ubuntu and rebuild new kernel packages with 6rd support.

Using my custom-built kernel package with CONFIG_IPV6_SIT_6RD, I get the following result from the above test:

root@maverick:~# uname -a
Linux maverick 2.6.35-2-generic #2 SMP Wed Jun 9 23:52:10 EDT 2010 i686 GNU/Linux
root@maverick:~# grep 6RD /boot/config-$(uname -r)
CONFIG_IPV6_SIT_6RD=y
root@maverick:~# ip tunnel add sit1 mode sit local 10.100.100.1 ttl 64
root@maverick:~# ip tunnel 6rd dev sit1 6rd-prefix 2001:0db8::/32 6rd-relay_prefix 10.0.0.0/8
root@maverick:~# ip tunnel show sit1
sit1: ipv6/ip remote any local 10.100.100.1 ttl 64 6rd-prefix 2001:db8::/32 6rd-relay_prefix 10.0.0.0/8
root@maverick:~#

Let me know if you need further justification for this request, or if I should raise the discussion in a different venue. Thanks.