6to4 borkeness (Was: Google and IPv6)

David Malone dwmalone at maths.tcd.ie
Wed Mar 19 16:46:52 CET 2008


On Wed, Mar 19, 2008 at 08:31:07AM -0700, Tim wrote:
> > Please give up on the debugging, 6to4 is not worth it.

> I expected as much.

FWIW, my experience with 6to4 is more positive than Jeroen's. It
works almost all the time for me, except when someone breaks the
2.0.0.2.ip6.arpa zone, but that hasn't happened for months. Mind
you, many of the ISPs that I regurally use have their own relays
or a relay close by.

For me, debugging 6to4 hasn't proved that much harder than anything
else. You can find the relay at your end by tracerouting to
192.88.99.1.  It's true that the reverse path is hard to debug, but
that's the same no matter what you're using. It was a little easier
in IPv6 when we had RH0 (though I know Jeroen prefers looking glasses
for this sort of thing).

> PS - Another poster's suggestion to have Google set up a 6to4 interface
>      might be a good one.  Until most of the Internet has transitioned
>      to non-tunneled access (in what, 50 years?), this would certainly
>      improve connectivity for users like me.

A 6to4 relay inside Google might help either (maybe they have one
already?) - that could smooth out the reverse path.

	David.



More information about the ipv6-ops mailing list