Advertenties

Setup IPv6 at home

Most dutch providers are not ready for IPv6 yet so two years ago i decided to look for other ways to enable IPv6 on my home connection. I finally did this using the Tunnelbroker of He.net. The setup is fairly easy and can be done on a lot of routers.

First, sign up for the Tunnelbroker website to get the needed account. Then login there. On the left side you will find the option ‘Create regular tunnel’, just below the account information. At IPv4 Endpoint type in your public IPv4 address (you can find it by going to www.whatismyip.nl) and choose a location that is close to you (i have Amsterdam, NL). Then click ‘Create Tunnel’.

After creating the tunnel go to the overview page and click on the newly created tunnel in the bottom. You will see all the configuration. Thats what you will need to configure IPv6 at home.

Configuration of Apple Airport

If you have an Airport Express or Airport Extreme the configuration is simple. Open the configuration tool of OSX and logon to your router, then go to the tab Advanced and click IPv6.

– Set the IPv6 mode to ‘tunnel’
– Set configure IPv6 to Manually
– Set ‘Remote IPv4 address’ to the Server IPv4 address found on the configuration page of tunnelbroker.net
– Set ‘Wan IPv6 address’ to the Client IPv6 address found on the configuration page of tunnelbroker.net
– Set ‘IPv6 gateway’ to the Client IPv6 gateway address found on the configuration page of tunnelbroker.net
– Set LAN IPv6 Address to the ‘Routed /64’ without the :/64 ending found on the configuration page of tunnelbroker.net

Now hit the apply button and let the airport restart. As found on the website of He.net:

After setting up the tunnel, you may get a warning from the Airport that there’s a problem with the tunnel configuration. Ensure you have a IPv6 DNS server set in the TCP/IP settings to correct the problem. Alternatively, if you can reach IPv6 websites with the error notice, you should be able to safely tell the Airport to ignore the error.

At home i’m using a Vyatta router for firewalling/NAT purpouses. Here is the configuration that i’m using:

configure
edit interfaces tunnel tun0
set encapsulation sit
set local-ip 77.xxx.xx.7
set remote-ip 216.xx.84.xx
set address 2001:470:xxxx:xxx::2/64
set description "IPv6 Tunnel"
exit
set protocols static interface-route6 ::/0 next-hop-interface tun0
commit

Not using a router?
These are the commands for a Windows PC (open a CMD box):

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 77.xxx.xx.7 216.xx.84.xx
netsh interface ipv6 add address IP6Tunnel 2001:470:xxxx:xxx::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:xxxx:xxx::1

You can verify the configuration by rebooting the Router and your PC, then try pinging commandline (DOS prompt?) with the command

ping6 www.facebook.com
Advertenties
  1. […] All of my servers are running on both ipv4 and ipv6 for a few years now, however i had never checked to see if people were actually connecting over IPv6 to our network yet. I know i do, since i am using the Tunnelbroker from HE.net. More information on that can be found here. […]

    Beantwoorden

Geef een reactie

%d bloggers liken dit: