IPv6: Miredo link to HE Tunnel endpoint

Julien — Sat, 17 Jan 2009 07:51:14 +0000

As announced a few weeks ago, my website should now be accessible through IPv6. The connectivity is made thanks to Hurricane Electric IPv6 tunnel service as recommended on Linode wiki.

At home, I use Miredo, an open-source Teredo IPv6 tunneling software for GNU/Linux and BSD. This works great with many websites. I can ping6 servers I know, like ipv6.google.com or www.debian-administration.org.
However, I cannot ping6 my Linode server until I have established a link from the linode to home. But after a while (a quarter or so), the link is dead, and I have to ping my home address again from the linode to make it alive.

Here are some results which might help:

From home to linode when not working:

$ traceroute6 2001:470:1f06:ccf::2
traceroute to 2001:470:1f06:ccf::2 (2001:470:1f06:ccf::2), 30 hops max, 80 byte packets
 1  2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2)  0.066 ms !H  0.060 ms !H  0.059 ms !H

From Linode to home:

$ traceroute6 2001:0:53aa:64c:2c29:6807:a37d:37e2
traceroute to 2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2), 30 hops max, 40 byte packets
 1  JulienV-1.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:ccf::1)  17.205 ms  19.652 ms  22.253 ms
 2  gige-g3-8.core1.nyc4.he.net (2001:470:0:5d::1)  23.290 ms  23.270 ms  23.272 ms
 3  10gigabitethernet1-2.core1.lon1.he.net (2001:470:0:3e::2)  91.743 ms  91.868 ms  91.846 ms
 4  10gigabitethernet1-1.core1.ams1.he.net (2001:470:0:3f::2)  99.611 ms  99.681 ms  99.659 ms
 5  amsix-501.xe-0-0-0.jun1.kelvin.network.bit.nl (2001:7f8:1::a501:2859:2)  100.223 ms  100.351 ms  100.330 ms
 6  teredo.bit.nl (2001:7b8:3:27:87:251:43:68)  100.347 ms  80.329 ms  95.304 ms
 7  2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2)  375.204 ms  379.675 ms  382.140 ms

And then from home to Linode when working (ie just after the previous traceroute6):

$ traceroute6 2001:470:1f06:ccf::2
traceroute to 2001:470:1f06:ccf::2 (2001:470:1f06:ccf::2), 30 hops max, 80 byte packets
 1  teredo.bit.nl (2001:7b8:3:27:87:251:43:68)  298.818 ms  298.804 ms  298.789 ms
 2  teredo-gw.jun1.kelvin.network.bit.nl (2001:7b8:3:27::2)  349.530 ms  349.522 ms  349.510 ms
 3  linx.he.net (2001:7f8:4::1b1b:1)  371.854 ms  371.847 ms  371.835 ms
 4  10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1)  491.051 ms  491.041 ms  491.029 ms
 5  1g-bge0.tserv4.nyc4.ipv6.he.net (2001:470:0:5d::2)  349.111 ms  346.930 ms  344.158 ms
 6  nix.kirya.net (2001:470:1f06:ccf::2)  351.527 ms  140.178 ms  142.217 ms

Is there anything else I could try to understand which is the faulty side (before I contact both Linode’s and tunnelbroker’s supports or report a bug against Miredo)?

IPv6 available on this site

Julien — Wed, 24 Dec 2008 15:34:02 +0000

Thanks to a recent article published on debian-administration.org, I have managed to get an IPv6 connectivity at home, and have hence decided to make this website available through IPv6.

I have used Hurricane Electric IPv6 tunnel service as recommended on Linode wiki, and everything seems to be working.

This was a really simple process (both at home and on my Linode!).

The AAAA DNS records have been set up.
While the propagation is being processed, you can still test using the IP 2001:470:1f06:ccf::2 (I now really understand why DNS have been created!). You can use ping6 or telnet -6 or even use your browser.

While browsing www.kirya.net using IPv6, you should get a message in the header (just below the links to RSS feeds) confirming your request have been served using IPv6.

Note that I haven’t yet set up all Apache virtual hosts to answer on IPv6, which might lead to some web pages being redirected to the defaut vhost. More over, the HTTP server will only answer to IPv6 request on port 80 (no SSL at the moment).

Kirya [.net] » IPv6

IPv6: Miredo link to HE Tunnel endpoint

IPv6 available on this site