Warning: Do not upgrade to Linux 2.6.20+
Carmen Sandiego on Wednesday, 09 May 2007 01:39:48
2.6.20 seems to have introduced a strange bug that most of the time prevents IPv6 routing through the tunnel to sixxs, see http://bugzilla.kernel.org/show_bug.cgi?id=8382
It worked for me one time and I thought at first that disabling some IPv6 options in kernel configuration did the trick, but after I had to reboot today, I couldn't get it back to work.
I now downgraded to 2.6.19 and everything is perfectly fine again.
(Don't forget http://noc.sixxs.net/faq/connectivity/?faq=filters for linux < 2.6.20.9)
Regards,
Felix
Warning: Do not upgrade to Linux 2.6.20+
Shadow Hawkins on Monday, 14 May 2007 21:17:35
Confirm this bug.
Unfortunately the bug opened on bugzilla doesnt seem to receive so much attention. :(
Warning: Do not upgrade to Linux 2.6.20+
Shadow Hawkins on Monday, 14 May 2007 21:46:30
[update]
ip route add 2000::/3 dev ifname
fix the problem as reported on the other topic
Warning: Do not upgrade to Linux 2.6.20+
Shadow Hawkins on Thursday, 17 May 2007 22:13:20
Well, this workaround is far from being perfect.
Every 20 hours more or less I have to delete the added route and then readd it.
Weird!....
Warning: Do not upgrade to Linux 2.6.20+
Carmen Sandiego on Sunday, 20 May 2007 01:09:26
Hi Stefano,
I decided to avoid the hassle with a downgrade, but i really appreciate your efforts, because sooner or later, i'll want to do a linux upgrade again and I hope the bug will be fixed by then :)
Nevertheless, i don't understand that route, it looks kind of strange to me. What is it supposed to do? I don't have such a route on my 2.6.19 system...
Regards, Felix
Warning: Do not upgrade to Linux 2.6.20+
Shadow Hawkins on Monday, 21 May 2007 12:59:02
I have the following work around:
add the route 2000::/1 via <gateway> dev sixxs
After this the routing work.
Posting is only allowed when you are logged in. |