AICCU - Tunnelbroker Support

AICCU is not only meant as a client for SixXS but can be used by any tunnel broker system that uses either TIC or TSP (Tunnel Setup Protocol) as their setup protocols. This allows many users to use this tool, who are then free to have a choice of provider, which also helps in furthering IPv6 Deployment which is one of SixXS's main goals.

AICCU will, on startup, automatically fetch the current list of supported and known Tunnel brokers from DNS by querying for TXT records found under _aiccu.sixxs.net. This allows us to update the list without having to ask all the to update the already installed AICCU tools.

Supported Tunnel Brokers

The following list shows the entries which are currently to be found under the _aiccu.sixxs.net DNS entry and thus the ones that show up in AICCU's login screen.

Tunnel Broker	Countries	Website	TIC/TSP
SixXS		http://www.sixxs.net	tic://tic.sixxs.net

Unsupported Tunnel Brokers

Following is a list of brokers that don't have TSP or TIC support and thus can't be used in combination with AICCU. Typically these brokers only have a website where one can request a tunnel. Some providers listed below only offer their service for their paying customers.

Tunnel Broker	Countries	Comments
Ameri.ca
BT Exact
CERNET		tbclient (uses CGI), no configuration
Consulintel / Euro6IX
Dolphins / AS8758
Earthlink R&D		Special Linksys WRT54G image uses an IPv4 IPSEC tunnel with DHCPv6 Prefix Delegation
FCCN
Hurricane Electric
IIJ
MANIS
MyTBS		Ruby based updater tool
NECTEC
NGNet.It		TILAB client (uses CGI)
Nerim
SCC
SingNet
Unix-Servers.de
XS26
XS4All

Teredo Servers

There are several open and closed Teredo Servers, see below for a small list of servers.

Provider	Countries	IPv4 address	IPv6 prefix	Comment
debian-miredo.progsoc.org		Unofficial Miredo Debian Package standard server
teredo.remlab.net		Miredo

IANA has allocated 2001::/32 for Teredo usage. There was a list of 6bone-based Teredo servers but as the 6bone has ceased to exist we have removed these entries. The Teredo prefix can be configured by adding/altering the following REG_DWORD value: \HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters\GlobalParams\TeredoPrefix. The DWORD value is interpreted as a 32 bit prefix, in network byte order.

Note that the above are Teredo Servers, which only are used for minor control traffic. Teredo Relays are anycasted and handle the bulk of the traffic. See Wikipedia's Teredo page for a detailed description.

Note: 6bone address space ceased to exist on 6/6/2006, thus Teredo services operating using it have to change over to 2001::/32.

Getting Listed

When you are a Tunnel Broker and your broker is not listed yet, then please contact SixXS, providing them with a description, name, tic, tsp or l2tp url and the location of the website for further information. We then will add this information to the _aiccu.sixxs.net label and after DNS has updated this will be visible in all the AICCU clients. When the username contains a domain name, eg user@example.org, then _aiccu.example.org will also be queried and, when available, listed in the selection box, thus allowing local services to be defined. For services with multiple domains a DNAME from one _aiccu subdomain to the other can be handy for easily defining all the services in one place.

The TIC/TSP url format is: (tic|tsp|l2tp)://<hostname>[:<portname|portnumber>].
Portname/number will be ommited usually, AICCU will then use the default value.

6to4?

6to4 relays are not listed as these should be using 192.88.99.1. If one still wants to manually configure a 6to4 host, thus not using the above endpoint, then see Nick Sayer's Public 6to4 Relay Routers List.