Most Internet Service Providers (ISP) don’t have the ability yet to get native IPv6 on your home router/modem. Most modems the ISP provides don’t have the ability to router IPv6 packets, but only IPv4. If you ask you ISP to configure their provided modem in a bridged mode, you then can connect you own device to it and that device will provide your router function in your home network.
If you use a Time Capsule as your home router you can fairly easy set up a IPv6 tunnel if your provider does not support a native IPv6 connection. This tunnel allows you to connect to the IPv6 Internet. Your connection with your ISP will still be only using IPv4. If you connect to a website which is only available via IPv4 nothing will change. If you connect to a website which is available on IPv6. Your home router will encapsulate the IPv6 packet into an IPv4 packet and send it to the other end of the tunnel. The packet which normally only has a IPv6 header, now has a IPv4 header in front of it. Therefore your ISP will handle this traffic exactly the same as the other IPv4 packets.
So how does your router know to where it must send the encapsulated IPv6 packet? You tell the router by configuring the tunnel parameters manually. For such a configuration you need a so called Tunnel Broker. This Tunnel Broker is the other end of the Tunnel where the IPv4 header is removed again and only the IPv6 packet will be left and routed to the final destination.
So before you can start your manual IPv6 tunnel configuration, the only thing you need is so called Tunnel Broker. I use the Hurricane Electric Free IPv6 Tunnel Broker.
On the website you must provide the Tunnel Broker with your IPv4 address. If you don’t know your IPv4 address, you can check this on www.whatismyip.com. Your details will look like:
The black blocks are specific for your connection, and at the green block you have to fill your home IPv4 address.
Go to the settings of your TC with the Airport Utility and select the tab Internet:
on the field IPv6 DNS Servers fill in the Anycasted IPv6 Caching Nameserver address.
Form there go to to button Internet Options… which is located at the bottom. Now you can start configuring your IPv6 tunnel.
From the drop down menu’s select Manually for Configure IPv6 and choose Tunnel for IPv6 mode.
Now you only need to fill in some addresses which are on the tunnelbroker.net webpage. The fields you need for you Time Capsule configuration are:
IPv6 WAN Address: Client IPv6 Address
IPv6 Default Route: Server IPv6 Address
Remote IPv4 Address: Server IPv4 Address
IPv6 Delegate Prefix: Routed /64
IPV6 LAN Address: choose a address form the Routed /64 you filled in the line above. e.g. the prefix ending with ::1
Now your tunnel is set up correctly. Go to test-ipv6.com to test your IPv6.
The latest version for the Time Capsule is at the moment is 7.6.3.
I installed this update and after the installation I experienced issues with my IPv6 connectivity. I googled around and found many discussions and blogs where people are explaining they have issues with IPv6 tunnels (6in4) after the update.
When I started my AirPort Utility I noticed that my native IPv6 configuration options are still the same. But the weird thing is that Apple somehow changed the IPv6 WAN address to address from the 6to4 prefix (described in RFC 3056). This prefix starts with 2002: then followed by the IP Address converted to hexadecimal numbers, which together makes the /48 6to4 prefix.
So if my IPv4 address was 220.127.116.11 my 6to4 address would be: 2002:7BEA:7BEA::/48. You need to do the calculation from decimal to hexadecimal (123 = 0x7B and 234 = 0xEA).
The weird thing is that in the configuration you can see my address was still manually configured to a IPv6 unicast prefix, but somehow Apple changed the active IPv6 on the WAN interface to the 6to4 prefix. You can see this in the picture below:
The only solution to get IPv6 to work again is to downgrade the Time Capsule. You need to click on your Time Capsule. When you hover over you version number and use the ‘option’ button when you click you get the option to select your previous version number. See the screenshot below:
After the downgrade to 7.6.1 I see that the configured IPv6 WAN address is the same as the active IPv6 address. A visit to test-ipv6.com shows that IPv6 is working again :).
Since my previous Asus WL-500gP was broken due to a power outage, it was time for a new one. Some requirements for a new router where; IPv6, 802.11a/n and gigabit Ethernet switch ports. The Asus only had the IPv6 requirement since I installed OpenWrt on it.
The Cisco EA4500 was one that supports all this. Since I quickly needed a new router I bought this one at a local reseller.
I installed this router at home and found out that this router supports native IPv6, but only via auto-configuration and DHCPv6. Manual IPv6 addresses cannot be configured and static IPv6 routing is also not an option.
Since my previous setup was static routing with IPv6, I needed some changes on the Internet Service Provider side. Luckily I do the configuration and administration for this ISP as a day job. So I introduced DHCPv6 as a configuration option for customers.
This is very easy to setup. The router on the ISP site is an Cisco ASR 1002, with an ATM interface to a DSL provider.
First the configuration for static IPv6 routing was as follow (only IPv6 relevant commands):
The EA4500 on the client side does a DHCPv6 request. The ASR on the ISP side replies and sends a prefix for the local LAN side and the DNS servers. The EA4500 advertises the /64 prefix and its own IPv6 address for DNS resolving on the local LAN via router advertisements (RA).