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

NetBSD

Also see the NetBSD IPv6 FAQ.

System requirements:

• NetBSD 1.4.x w/ KAME patches
• NetBSD 1.5.x/2.x/3.x or up

First make sure you have INET6 enabled in your kernel. Look if your ifconfig reports link-local addresses for your interfaces, if it does you have IPv6 in your kernel.

For NetBSD 1.5.x and up, which support dynamic creating of interfaces, you will first have to create the tunnel interface, using:
ifconfig gif0 create

Next step is configuring the tunnel:
# ifconfig gif0 tunnel [Your IPv4 Endpoint] [PoP IPv4 Endpoint]
# ifconfig gif0 inet6 [Your IPv6 address] [PoP IPv6 Endpoint] prefixlen 128

The tunnel should be up now. Route your IPv6 traffic via the SixXS PoP:
# route add -inet6 default [PoP IPv6 Endpoint]
If you plan to use your machine as a router:
# sysctl -w net.inet6.ip6.forwarding=1

To configure the tunnel at boot time create the file /etc/ifconfig.gif0 at put the following content into it:

  create                                                                  
  tunnel [Your IPv4 Endpoint] [PoP IPv4 Endpoint]                         
  inet6 [Your IPv6 address] [PoP IPv6 Endpoint] prefixlen 128             
  !route add -inet6 default ::1                                           
  !route change -inet6 default -ifp $int                                  

If net.inet6.ip6.forwarding is not set to 1 by default (it isn't in a default NetBSD install, you can add the following line to /etc/sysctl.conf:

  net.inet6.ip6.forwarding=1