IPv6 with 6to4 and 6in4/SixXS

Wed 09 February 2011
By mute

I took interest in IPv6 again, possibly like many other people, after hearing about IPv4's last big blocks being assigned and a World IPv6 day scheduled in June. I had signed up for both SixXS and HE.net's tunnel broker services in Janurary 2009 but didn't really use them.

First, I setup a 6in4 tunnel from my WRT54G using SixXS's acciu client. This setup is nice. You only get a single IP though, and must run the tunnel for a week before getting your /64 subnet.

My WRT54G is currently a "dial-up router" which has a public address but is firewalled from any incoming traffic. Thus, HE.NET would not setup a tunnel, and SixXS's AICCU client keeps dynamic tunnels working well. So now I am able to connect to my dynamic IPv4 dial-up router from anywhere on the IPv6 network using a static IPv6 address.

The setup was fairly trivial and I will not discuss that here, but the differences between this and 6to4 which I found.

So on my netbook, using Linux as well, I setup 6to4 while not behind the dial-up router. http://6to4.version6.net/?lang=en_GB shows the complete simple setup. Now it has basically the same IPv6 connectivity as the dial-up router, with the exception that it's IPv6 address is dynamic due to its dynamic IPv4 address. Also, I've read that the 6to4 prefix 2002::/16 is not always routable to native IPv6 clients.. Possibly something to do with the other ends closest relay server that advertise the 2002::/16 prefix may not be functioning while the relay closest to me is.. Hmm!

But with 6to4, there is no signup process, and you immediately get a routable subnet, albeit a dynamic one if your IPv4 address is dynamic. This is OK for traveling system. My home network would be better served by 6in4 tho. SixXS will eventually assign me my own address space which is hopefully mine, and mine forever. :) Right now tho, I only have a single IP which is assigned to the tunnel endpoint.

When I get home, I'd like to further experiment by connecting some machines only by IPv6, and using NAT64 on the router.

I am unsure if the problem is my DNS server, my libc library or what, but traffic still prefers IPv4 right now if a hostname returns both. That's OK for now... Whatever.

Comments