Posted by Julien in Weblog
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.
More >
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:a37
Posted by Julien in Weblog
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).
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
