Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-26 Thread Meelis Roos
(To YOSHIFUJI Hideaki: this is about the http://comments.gmane.org/gmane.linux.network/35262 thread) : I guess rt6_select() is returning ip6_null_entry and the caller is finding next best route; e.g. default route. Does this solve your problem? Sorry, typo... The unreachable route works

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-26 Thread YOSHIFUJI Hideaki / 吉藤英明
In article [EMAIL PROTECTED] (at Fri, 26 May 2006 11:35:53 +0300 (EEST)), Meelis Roos [EMAIL PROTECTED] says: The unreachable route works now but LAN routing still does not work. Locally generated ICMPv6 packets that should go to LAN interface still go to tun6to4. Please try this.

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-26 Thread Meelis Roos
The unreachable route works now but LAN routing still does not work. Locally generated ICMPv6 packets that should go to LAN interface still go to tun6to4. Please try this. This works for both unreachable and LAN routes, thanks! -- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-25 Thread Meelis Roos
On my home 6to4 gw, ipv6 routing seems to be broken and everything is sent to 6to4 tunnel (the default route). It worked with fine for a long time and with 2.6.17-rc2-g4d5c34ec and it's broken with vmlinuz-2.6.17-rc3-g3cd73eed and 2.6.17-rc4-g9be2f7c3 (yesterdays kernel). So far I have

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-25 Thread Meelis Roos
(To YOSHIFUJI Hideaki: this is about the http://comments.gmane.org/gmane.linux.network/35262 thread) Tracked it down to IPV6 merge at 2006-03-21: commit cd85f6e2f58282186ad720fc18482be228f0b972 is good (right before the bunch of patches) commit b00055aacdb172c05067612278ba27265fcd05ce is bad

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-25 Thread YOSHIFUJI Hideaki / 吉藤英明
In article [EMAIL PROTECTED] (at Fri, 26 May 2006 02:24:19 +0300 (EEST)), Meelis Roos [EMAIL PROTECTED] says: (To YOSHIFUJI Hideaki: this is about the http://comments.gmane.org/gmane.linux.network/35262 thread) Tracked it down to IPV6 merge at 2006-03-21: commit

ipv6 routing broken in 2.6.17-rc3,4

2006-05-15 Thread Meelis Roos
On my home 6to4 gw, ipv6 routing seems to be broken and everything is sent to 6to4 tunnel (the default route). It worked with fine for a long time and with 2.6.17-rc2-g4d5c34ec and it's broken with vmlinuz-2.6.17-rc3-g3cd73eed and 2.6.17-rc4-g9be2f7c3 (yesterdays kernel). Example (I add an

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-15 Thread Pekka Savola
On Mon, 15 May 2006, Meelis Roos wrote: On my home 6to4 gw, ipv6 routing seems to be broken and everything is sent to 6to4 tunnel (the default route). It worked with fine for a long time and with 2.6.17-rc2-g4d5c34ec and it's broken with vmlinuz-2.6.17-rc3-g3cd73eed and 2.6.17-rc4-g9be2f7c3

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-15 Thread Meelis Roos
vaarikas:~# ip -6 route 2002:5283:297e::/48 dev tun6to4 metric 256 expires 21332659sec mtu 1480 advmss 1420 hoplimit 4294967295 You're using the wrong prefix length. The right one is /16. Does that work? Will try soon today. But the other routes had mor specific masks anyway - /64 and

Re: ipv6 routing broken in 2.6.17-rc3,4

2006-05-15 Thread Meelis Roos
vaarikas:~# ip -6 route 2002:5283:297e::/48 dev tun6to4 metric 256 expires 21332659sec mtu 1480 advmss 1420 hoplimit 4294967295 You're using the wrong prefix length. The right one is /16. Does that work? Changed tun6to4 to 2002::/16, still the same (packets for eth0 and the unreachable