List of IPv6 tunnel brokers
This is a list of IPv6 tunnel brokers that conform to the principles of RFC 3053 which describes a system with which users can request creation of an IPv6 tunnel on a host called a point of presence (PoP) that provides IPv6 connectivity to the user's network.
|Name||PoPs||Locations||Subnet||Tunnelling protocols||Features||Registration||Configuration||Language||Prefix||Server implementation|
|CITC||1||Saudi Arabia||/64||No||Yes||No||No||No||No||No||Required||No||No||Yes||No||No||English, Arabic||2001:67c:130::/48||ddtb|
|gogo6/Freenet6||3||Canada, Netherlands, Taiwan||/56 on request||No||Yes||No||No||No||No||No||Optional||No||No||Yes||No||No||English||2001:5c0::/32||gogoSERVER|
|Hurricane Electric||31||Canada, Europe (8 Countries), Hong Kong, Japan, Singapore, United States (9 States)||/64 default
/48 by request
|Indonesian IPv6||1||Indonesia||/64 or /48 on request||Yes||No||No||No||Yes||Yes||No||Required||Yes||Yes||No||No||Yes||English||2001:d68::/32||Unknown|
|IPv6Now||1||Australia||/64 or /48 on request||Yes||Yes||No||No||No||No||No||Required||No||No||Yes||No||No||English||2406:a000::/32||gogoSERVER|
|SixXS||48||Australia, Brazil, Europe (20 countries), New Zealand, New Caledonia, Russia, United States (8 States), Vietnam||/64 default
/48 on request
The columns in the table provide the following details:
|Name||The name of the organisation providing the tunnel broker, this generally maps directly to an Internet service provider.|
|PoPs||Number of PoPs deployed|
|Locations||Locations where the tunnel broker has a PoP where termination of a tunnel can occur.|
|Subnet||What subnet allocation the tunnel broker provides next to the /127 or /64 for the tunnel.|
|Which tunnelling protocols are provided by the tunnel broker. This has impact on whether one can use a tunnel behind NAT or in cases where the IPv4 address of the user changes often. Check the relevant protocol descriptions for more details, or see this tunneling comparison.|
|6in4||6in4 tunnels IPv6 packets directly inside IPv4, also called 'proto-41' due to the protocol number (41) it uses.|
|TSP||The Tunnel Setup Protocol. It uses a UDP-based tunnel, which is used for both tunnelling and configuration.|
|AYIYA||AYIYA allows users behind a NAT and/or a dynamic address to maintain connectivity even when roaming between networks. It uses a UDP-based tunnel.|
|heartbeat||heartbeat is a side-protocol for signalling the current IP address of a user's 6in4 endpoint. This allows the use of a 6in4 tunnels where the user's endpoint is a dynamic IP address.|
|Features||RDNS||Whether the tunnel broker provides reverse DNS delegations for the address space they provide over the tunnel.|
|BGP||Whether the tunnel broker accepts a BGP peering allowing one to announce one's own address space or see routing information.|
|Multicast||Whether the tunnel broker provides IPv6 Multicast over a tunnel.|
|Registration||If registration is optional or required. Registration requires the user provides real details (at minimum an email address, typically also name and address)|
|What methods are available for configuring tunnels and subnets provided by the tunnel broker|
|Script||Indicates that the broker provides a script through their website that one can run on a computer for setting up the tunnel.|
|Manual||That one can set up the tunnel manually if wanted|
|TSP||Uses the Tunnel Setup Protocol (TSP) which requires the gogoclient and which can provide configuration details for TSP protocol tunnels.|
|TIC||Uses the Tunnel Information and Control (TIC) protocol as implemented by AICCU, AVM FRITZ!Box, Draytek, Motorola and others. This can provide configuration details for static, heartbeat and AYIYA tunnels.|
|URL||URL indicates that changes to the tunnel parameters can be made on the website (e.g. enable/disable or change the endpoint)|
|Language||Which languages are supported by the providers web interface and other communication channels.|
|Prefix||Which IPv6 prefix(es) are used for the tunnel broker. If a /32 is indicated, generally only a portion is used for tunnels/subnets for the tunnel broker or the name of the tunnel broker service that is providing the address space.|
|Server implementation||The implementation of the server software used by the tunnel broker|
There are a variety of tunnel brokers that provide their own custom implementations based on different goals. Listed here are the common implementations as used by the listed IPv6 tunnel brokers.
gogoSERVER (formerly Gateway6) is used by the Freenet6 service, which is the first IPv6 tunnel broker service, going into production in 1999. It was started as a project of Viagenie and then Hexago was spun off as a commercial company selling Gateway6, which powered Freenet6, as their flagship product. In June 2009, Hexago became gogo6 through a management buyout and the Freenet6 service became part of gogoNET, a social network for IPv6 professionals.
SixXS's sixxsd is what powers all the SixXS PoPs. It is custom built software for the purpose of tunneling at high performance with low latency. Development of sixxsd started in 2002 and has evolved into the current v4 version of the software. The software is made available for ISPs who provide and run SixXS PoPs. Originally, in 2000, SixXS used shell bash scripts. Due to scalability issues and other problems sixxsd was designed and developed.
CITC Tunnel Broker, run by the Saudi Arabia IPv6 Task Force, uses their own implementation of the TSP RFC named 'ddtb'.
- AICCU - Tunnelbroker Support, lists tunnel brokers that are supported and unsupported by AICCU
- CITC Tunnel Broker
- gogo6 Service Status
- gogoNET signup for Freenet6
- HE Tunnel Server Status
- HE Endpoint update
- NetAssist URL Update instruction
- SixXS Points of Presence
- SixXS Prefixes
- What is gogoNET?
- SixXS History