Julien Valroff's weblog and personal homepage
IPv6: Miredo link to HE Tunnel endpoint
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)?
| Print article | This entry was posted by Julien on January 17, 2009 at 08:51, and is filed under Weblog. Follow any responses to this post through RSS 2.0. Both comments and pings are currently closed. |
Comments are closed.
about 1 year ago
Use an IPv6 keepalive like NTP on the linode server
about 1 year ago
Thanks, that should indeed help, but is there a reason of this issue you can think of?
Cheers,
Julien
about 1 year ago
Unfortunately, this hasn’t worked.
After rebooting my home machine (and hence after the IP address changed):
Any ideas?
about 1 year ago
Following to this issue, I have configured my linode to use 6to4.
Until now, I haven’t noticed any similar issue.
I have written to HE support and will report their answer if relevant.
Cheers,
Julien
about 1 year ago
OK, after a few hours, the same issue happens with 6to4. The problem is hence on my side (Miredo).
I will investigate further.
I am switching my Linode back to HE tunnel service.
about 1 year ago
Actually, and after Alex explained to me that my Linode has to use an ipv6 NTP server as a keepalive, things are now working correctly.