CONFIG_IPV6_SIT_6RD is disabled in kernel config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft |
Bug Description
Binary package hint: linux-image-
The 2.6.35-1 packages in maverick do not have the CONFIG_IPV6_SIT_6RD option enabled. This option controls the availability of the "IPv6 Rapid Deployment (6rd)" implementation in the IPv6 SIT module.
6rd is an automatic tunneling mechanism that allows ISPs to provide IPv6 access to their customers using an existing IPv4 infrastructure. Free.fr has been using 6rd since 2007, and Comcast is rolling out 6rd-based IPv6 trials this month. Several other ISPs are planning to deploy 6rd as well.
With the CONFIG_IPV6_SIT_6RD kernel config option enabled, the behavior of the kernel will not change unless the user specifically configures a 6rd interface using "ip tunnel". (On the userland side, 6rd is supported in iproute-20100519-2 which is already in maverick.)
Please enable the CONFIG_IPV6_SIT_6RD option in the maverick kernel config so that Ubuntu users can receive IPv6 connectivity with 6rd.
tags: | removed: needs-kernel-logs needs-upstream-testing |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
tags: | added: kernel-core kernel-needs-review |
tags: |
added: kernel-candidate kernel-reviewed removed: kernel-needs-review |
tags: | removed: kernel-candidate |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in linux (Ubuntu): | |
milestone: | none → maverick-alpha-3 |
Hi Nathan,
Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http:// cdimage. ubuntu. com/daily- live/current/ . If the issue remains, please 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 591869
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/KernelMainl ineBuilds . 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.]