RIPE, the European internet registry has started heavily rationing IPv4 addresses, meaning that the day of IPv6 only connections is fast approaching. BT don't yet support IPv6 on their connections, but I need to be able to use IPv6 to help ensure that servers are correctly set up to handle IPv6 only traffic.
So, I need to create an IPv6 over IPv4 tunnel.
This documentation details the steps to do this using Helium Electric's (free) tunnelbroker service
Firstly we need to sign up for a free account at http://tunnelbroker.net. Once your username and password have been emailed to you, login and start the process of creating a tunnel. If you're on a BT connection behind a BTHomeHub you're going to hit issues almost straight away!
The BTHomeHub doesn't respond to WAN Side ICMP echo requests (Pings) and there's no way to configure it to do so. You'll need to put one of your machines into the DMZ so that tunnel broker can check your IP. To do so
- Browse to BTHomehub.home
- Click Settings
- Enter your Administrator password
- Click Advanced Settings
- Click Advanced Settings again (why do BT make us click twice?)
- Click Port Forwarding
- Click DMZ
- Set the radio to Yes and select the machine you're currently on
- Click Apply
Now Tunnelbroker should be able to ping your machine, so continue with the set up process. Once the tunnel's created, make a note of the settings you are given and then run the following set of commands from a console
Change the addresses to those that you were given
# replace 126.96.36.199 with the Server IPv4 address you were given
# Replace 188.8.131.52 with the Client IPv4 address you were given
ip tunnel add he-ipv6 mode sit remote 184.108.40.206 local 220.127.116.11 ttl 255
ip link set he-ipv6 up
# Replace 2001:470:1f08:4cc::2/64 with Client the IPv6 address you were given
ip addr add 2001:470:1f08:4cc::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr
In theory you should now be able to ping using an IPv6 connection
Did it work? No it didn't for me either at first! (Network is unreachable).
I found two things - first that my machine has to be in the DMZ as the HomeHub won't route protocol 41 (I'd taken it back out of the DMZ once the tunnel was created on tunnelbroker), but also that the routes created above didn't seem to work.
So what I did was to remove all the routes
# I ran each of these twice
ip -6 route del 2001:470:1f08:4cc::/64
ip -6 route del default
Now I was able to use ifconfig to set things up (the commands above helpfully created the sit devices for us!). I did originally try re-adding the routes using ip but received errors
ifconfig sit0 up
ifconfig sit0 inet6 tunnel ::18.104.22.168
ifconfig sit1 up
ifconfig sit1 inet6 add 2001:470:1f08:4cc::2/64
route -A inet6 add ::/0 dev sit1
Following this I was able to run
and get a response!
Browsing to http://www.whatsmyipv6.org/ also showed that I was connecting via IPv6.
Now I can go and add some AAAA records for websites, as I'm able to check that the sites/servers are actually working with IPv6 rather than having to click and pray.
Update: Once the tunnel is established you can move the machine out of the DMZ. It seems the HomeHub will route the packets if the state is ESTABLISHED. You'll need to move back into the DMZ if you want to re-connect (say after a reboot) but it's better than leaving a client in the unprotected area the whole time (though you are running a software firewall, aren't you!)