FAQ : Connectivity (Tunnels and Subnets) : How do I configure my machine to setup the IPv6 in IPv4 tunnel to the SixXS PoP?

Other FAQ sections

Can I move my tunnel/subnet to another PoP? Can I request multiple subnets over my tunnel? Can I use SixXS tunnels to hide my IPv4 IP? Can a heartbeat tunnel be converted to a static or AYIYA tunnel or vice versa? Do you provide 6to4 connectivity? Do you provide BGP peering? Heartbeat or AYIYA tunnel doesn't work How do I configure my machine to setup the IPv6 in IPv4 tunnel to the SixXS PoP? How do I give connectivity to other hosts on my subnet? How is my endpoint connectivity tested? I have a firewall, what ports/protocols are used? IPv6 Transition Mechanism / Tunneling Comparison Is my connectivity filtered? / Mandatory IPv6 Filtering on IPv6 Is there a command line/non web tool for SixXS? Is there a traffic/data limit? Is there support for dynamic IPv4 endpoints? Multicast Support My IPv6 is random and changes often. Why? My static endpoint is broken and I don't want to lose credits My tunnel doesn't work My tunnel goes down after some idletime. My tunnelendpoint also is a NAT/Connection Tracker My tunnel/subnet doesn't work at once My tunnel/subnet stays in deleted state PoPs that are marked down The tunnel is slow Transit / I have some other tunnels and now it doesn't work Tunnel endpoint didn't ping What is the MTU of a tunnel? Where can I get native IPv6 / Which ISPs provide IPv6? Where can I get native IPv6 transit? Which PoP should I choose? Why are some PoPs not available for tunnels

How do I configure my machine to setup the IPv6 in IPv4 tunnel to the SixXS PoP?

The easiest way is by using AICCU, though if one wants to configure it manually or because AICCU doesn't support your platform, then you can pick your Operating system from the following list. AICCU can configure static, heartbeat and AYIYA tunnels.

The manual methods described below only apply to static proto-41 tunnels. AYIYA and heartbeat tunnels require AICCU.

Select your Operating System
6Wind (SixOS) ASUS WL-500g Apple Mac OS X (Darwin) Cisco (IOS) FreeBSD IBM AIX Juniper (JunOS) Linux - Debian, Ubuntu and derivatives Linux - Gentoo Linux - New - using iproute2 Linux - Old Linux - RPM/initscripts (Fedora/Redhat/etc) Linux - SUSE/OpenSUSE MirOS NetBSD OpenBSD Solaris Tru64 Windows 98 / NT4 / 2000 / XP / .Net / Vista

Windows 98 / NT4 / 2000 / XP / .Net / Vista

AICCU can be used to setup a tunnel without any need for manual command typing.

For Windows the IPv6 stacks that are recommended are at least:

• Windows Server 2003 and up
• Windows Vista / Seven / Eight onward

Other stacks, eg for Windows 98 and Windows XP SP2+ (End of Life on 2014.04.08) should not be used as they tend to have security issues that are not resolved and/or do not support a proper full IPv6 feature set.

See also IPv6 Support in Microsoft Products and Services for an overview what Microsoft offers.

The following sections detail the various available stacks in a little bit more detail.

Windows 98 and older

For Windows 98 there exists "Hitachi Toolnet6" and "Trumpet Winsock", we won't cover these two any further. One should not be using these Operating Systems anymore.

Windows NT4 with MS Tech Preview IPv6

This version is very unsupported by Microsoft and lacks a lot of features and is generally considered unstable. It is still available from the Microsoft Research IPv6 stack (MSRIPv6) pages and even comes with source.

Windows 2000 with MS Tech Preview IPv6 stack

First step is to check if you've got the IPv6 stack installed. The Microsoft stack can be easily detected by typing 'ipv6 if' in a command prompt. If you get a listing of the IPv6 interfaces you know it is installed. For Windows 2000 you'll need to download:

• tpipv6-001205-SP2-IE6.zip which contains the SP2 fixes
• tpipv6-001205-SP3-IE6.zip for an SP3 version
• tpipv6-001205-SP4-IE6.zip for an SP4 version

Note that the Windows 2000 IPv6 stack isn't supported by Microsoft and Windows 2000 itself is EOL.

Next step is configuring the tunnel:
C:\> ipv6.exe rtu ::/0 2/::[PoP IPv4 Endpoint] pub
C:\> ipv6.exe adu 2/[Your IPv6 endpoint]

Windows XP / .Net / Vista / Seven / Eight

On XP it can be installed quite easily by typing "netsh interface ipv6 install" in the command prompt.
For Windows XP/2003/.Net and up, according to Updating IPv6.exe Commands to Netsh Commands this should be:
C:\> netsh interface ipv6 install
C:\> netsh interface ipv6 add v6v4tunnel SixXS [Your IPv4 Endpoint] [PoP IPv4 Endpoint]
C:\> netsh interface ipv6 add address SixXS [Your IPv6 Endpoint]
C:\> netsh interface ipv6 add route [Tunnel Prefix]/[Prefix Length] SixXS
C:\> netsh interface ipv6 add route 0::/0 SixXS publish=yes

As your tunnel needs to ping: Allow ICMP, for Windows XP SP1 and lower:
C:\> netsh firewall set adapter SixXS icmp all=enable

For Windows XP SP2 and up, including Windows 2003 and Windows Vista:
C:\> netsh firewall set icmpsetting SixXS enable all

The tunnel should be up now and have a default route through the SixXS PoP.