Until my VMware server machine crashed, I had a pair of IPv6 tunnels running for many months out of a pair of virtual machines. One was Ubuntu Hardy with a tunnel to Sixxs.net, the other an OpenBSD machine with a tunnel to Hurricane Electric‘s Tunnelbroker service.
Wanting to get back into the IPv6 address space, I installed the aiccu client on another server and configured it for my Sixxs tunnel. This worked out of the box, but within about 36 hours it stopped working. Most frustrating was the lack of any errors in any logs and restarting the service had no effect. The tunnel interface was created with the correct IP, route showed all the correct routes, and I could ping the IPv4 address of my assigned PoP (uschi02). Then, strangely, about two hours later things started working again. Until this morning…
I awoke to find that the tunnel had again dropped overnight, and as before, nothing I do seems to be able to get the tunnel working again. The Sixxs website indicates that the PoP is up and talking to other PoPs.
So, since I also have a tunnel from Hurricane, I gave another machine a static IP and added the necessary information to /etc/network/interfaces:
# Hurrican Electric IPv6 Tunnel auto he-ipv6 iface he-ipv6 inet6 v4tunnel endpoint <your_assigned_IPv4_server_endpoint> address <local_IPv6_tunnel_endpoint> netmask 64 mtu 1480 up ip -6 route add 2000::/3 dev he-ipv6
From this point, I restarted the network service:
sudo /etc/init.d/networking restart
et voila! The tunnel was up and pingable. So I guess I will stick with the HE service for now, though if anyone has any ideas as to what the issue with Sixxs might be (when using Ubuntu Intrepid and aiccu / AYIYA), please let me know.
2 comments
Seeder says:
December 7, 2008 at 7:14 pm (UTC -4 )
Usual cause it the time being out of sync, it’s a good practice to have a ntp running on that server as a daemon.
Ben Thompson says:
December 26, 2008 at 3:55 pm (UTC -4 )
Great article. I found some more information here