|
IPv6 broken on upgrade to 2.4.21 kernel (linux)
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Friday, 20 June 2003 09:55:16
Hi,
I've been a happy tunnel user for quite some time. Last week I upgraded to the 2.4.21 kernel (to get rid of some nasty sploits). My ipv6 tunnel has been working all this time (even on the new kernel), however there are some routing issues with ipv6 on 2.4.21. I can't ping the sixxs tunnel endpoint (at least, I get replies from my own system, and not from the other endpoint).
I've spent some hours trying to figure it out, manually adding and removing addresses, routes etc, but can't get it to work correctly under 2.4.21...
For the time being i've downgraded back to 2.4.20, so I don't lose all my credits.
Any suggestions are welcome.
IPv6 broken on upgrade to 2.4.21 kernel (linux)
![[si]](/s/countries/si.gif) Carmen Sandiego on Tuesday, 29 June 2004 18:42:17
Hmmh you probably forgotten to enable kernel support })
IPv6 broken on upgrade to 2.4.21 kernel (linux)
![[de]](/s/countries/de.gif) Shadow Hawkins on Friday, 20 June 2003 11:35:41
A quick check of the routing table revealed that it installed a "strange" route automtacalyy. As I did not follow the linux net maillinglist, perhaps someone who did has an idea about the why and howto switch off.
Anyway, the workaround (in works-for-me-state ;-) is
route -A inet6 del <remote ipv6 tunnel endpoint> dev lo metric 0
HTH,
Joerg
IPv6 broken on upgrade to 2.4.21 kernel (linux)
usagi-users 02433 discusses the problem.
8<-------
This is NOT the bug but by the spec.
prefix:: is an anycast address, not a unicast;
you cannot use it like an unicast address.
------->8
IMHO they are correct, but they should have provided a toggle for turning this behaviour off certainly because many people use /127's and other prefixes in production.
IPv6 broken on upgrade to 2.4.21 kernel (linux)
![[ie]](/s/countries/ie.gif) Shadow Hawkins on Wednesday, 14 April 2004 14:26:34
seems that there is a follow up (here: http://www.linux-ipv6.org/ml/usagi-users/msg02435.html ) that anwsers that :
8<-----------
Is there a toggle for turning this behaviour off ?
Switch forwarding off.
Routers are REQUIRED to be enabled.
----------->8
IPv6 broken on upgrade to 2.4.21 kernel (linux)
Shadow Hawkins on Friday, 20 June 2003 19:22:45
Hm, is there a plan to change the /127 tunnel managed by sixxs.net to /126 or something bigger?
IPv6 broken on upgrade to 2.4.21 kernel (linux)
No.. why should we all of a sudden need to move a lot of users because of Linux people changing stuff. Also it's quite easy to avoid by adding some routes and deleting the route to lo. It's a endsite setup problem, not ours ;)
Also the IPng POP is the only POP using /127's the others use /64 tunnels which only have ::1 (POP side) and ::2 (user side).
|
![[ch]](/s/countries/ch.gif)
on Friday, 20 June 2003 16:57:35
Posting is only allowed when you are