On Wed, May 21, 2003 at 08:30:33PM +0200, Rudi Sluijtman wrote: > On Tue, May 20, 2003 at 12:08:51PM +0200, Lionel Elie Mamane wrote: >> ip -6 route del default via ::139.18.38.73 >> ip -6 route add default via 2002:c058:6301:: > This one doesn't work, at least I cannot ping6 www.kame.net. Hmm... >> Please let me know if it works, I'm very curious. If it doesn't work, >> try >> ip -6 route del default via 2002:c058:6301:: >> ip -6 route add default via ::192.88.99.1 > Yes, this does work! > I guess using the ipv6 address as route directly is not possible > because there is no ipv6 route to it. Well, the kernel *should* recognize the 2002::/16 prefix and route it over IPv4 directly, to the IPv4 address in the next 32 bits. I'm going to try this with an USAGI kernel some day. I guess that is what "CONFIG_IPV6_6TO4_NEXTHOP" is about in USAGI kernels. Let's take the example of a machine having both an IPv4 and IPv6 access. A packet is to be sent to an address in 2002:DEAD:BEEF::/48 - Stock 2.4 linux seems (I think) to send the packet to the default IPv6 router, bringing a catch-22 when the default router is in 2002:DEAD:BEEF::/48 - USAGI kernel with CONFIG_IPV6_6TO4_NEXTHOP=Y would send it "directly" over IPv4 to 222.173.190.239 . >> And by the way, the "List of public 6to4 routers" that was unavailable >> during the meeting is back online: http://www.kfu.com/~nsayer/6to4/ > It mentions 6to4.ipng.nl for the Netherlands, but this name cannot > be resolved :( Yeah, I know. > ::192.88.99.1 is fine with me, as it is the nearest router anyway. Yes, and the really cool thing is that when Chello will setup their own 6to4 router, you'll start using it immediately and automagically :-)
<<inline: application/pgp-signature>>