AICCU - Automatic IPv6 Connectivity Client Utility

AICCU (Automatic IPv6 Connectivity Client Utility) makes it easy for users to get IPv6 connectivity. After having requested an account, tunnel and optionally a subnet, AICCU can be used to automatically configure the tunnel. AICCU supports TIC (Tunnel Information & Control protocol), which it uses for retrieving the tunnel configuration information, AYIYA, which allows tunnels to be created even behind firewalls and NAT's.

AICCU uses The GNU Transport Layer Security Library to secure TIC communications.

Award Of Excellence

AICCU has won the Award of Excellence in the Implementation Category of the 2004 Edition of the IPv6 Application Contest.

Problems?

When encountering problems, first check the FAQ, if that does not solve your issue, please report them directly to SixXS.

User contributed information can be found in the Wiki.

License

This software comes with an Open Source LICENSE.

Notes

Please read the README that is included with AICCU. Following is an important section of that text:

WARNING: Never run AICCU from DaemonTools or a similar automated 'restart' tool/script. When AICCU does not start, it has a reason not to start which it gives on either the stdout or in the (sys)log file. The TIC server *will* automatically disable accounts which are detected to run in this mode. Use 'verbose true' to see more information which is especially handy when starting fails.

Please also heed the notice in the TIC FAQ which explains what happens to clients that connect repeatively.

Downloads

Latest Windows console version: 2012.02.02
Latest UNIX/Console version: 2007.01.15

• Source:
  • source tarball [tar.gz]
• Windows 8, Windows 7, Windows Vista, Windows XP and Windows 2000
  • Console [exe]

  • For AYIYA support on Windows the Tun/Tap32 driver is needed to be installed.

    • Tap Driver (tap901 version 9.9.2) [zip] - Windows XP, Windows Vista, Windows Seven, Windows 8 (32bit + 64bit)
    • Tap32 Driver (tap801) [zip] - Windows 2000 and Windows XP (32bit only)

    AICCU upto 2006.07.23 only support the tap801 version of the driver. Newer AICCU support tap801, tap802 and tap901.

    The Tun/Tap32 driver comes from the OpenVPN project.

• Linux based:
  • Debian, Ubuntu:
    
    • Included in Debian as aiccu thanks to Philipp Kern for maintaining it! So just: apt-get install aiccu
  • Eisfair:
    • Pack-eis
  • Gentoo:
    • Gentoo E-build
  • LEAF (Linux Embedded Applicance Firewall):
    • LEAF Package
  • ArchLinux:
    • x86_64/amd64 Package
    • i686 Package
  • OpenWRT, ASUS WL-500g
    • Included in OpenWRT as 'aiccu'
    • New versions available from: the backports
  • Redhat / Fedora / CentOS:
    • Fedora Core 7+, available in the default repository
    • Fedora Cora 5-6: available through Fedora Extras
    • RHEL4/ RHEL5 and CentOS: use the Extra Packages for Enterprise Linux (How to use)
  • Slackware:
    • Slackware packages by Olivier Mehani
  • SourceMage GNU/Linux:
    • Included in the grimoire branches (test and stable-0.20 grimoire or later), use "cast aiccu" to install.
  • SUSE:
    • (Open)SUSE packages [rpm]
• FreeBSD
  • Included in the FreeBSD Ports as net/sixxs-aiccu
• OpenBSD
  • Included in the OpenBSD ports tree ('pkg_add aiccu' for platforms where precompiled binaries exist)
• NetBSD, DragonFlyBSD
  • Included in the NetBSD Package Collection as net/aiccu
  • Port information is also in the source tarball
  • For AYIYA support requires a the tun/tap driver to build and function
• Mac OS X
  • Homebrew: brew update && brew install aiccu
  • Can be build from the source tarball using XCode
  • Mac OS X Binary for i386 (thanks to Alex Le Heux for the compile, you still need to put the config file in the right place and install tun/tap support if needed; it is called .exe because that is what it is rename it to aiccu-mac-i386 for normal naming behavior)
  • Requires the tun/tap driver to build
  • Available from MacPorts, but be aware of MacPorts Bug #22872, thus disable the launchd tool from running AICCU.
• Sun Solaris
  • Can be build using the supplied Makefile
• IBM AIX
  • Can be build using the supplied Makefile

Alternatively to the above links, one can also access the AICCU download archive directly for older and alternative versions.

Next to the these editions there are various routers on the market, on a store shelf near you, that have AICCU built in and have web interface options to configure it.

An example configuration file: aiccu.conf
For the Windows version store as c:\windows\aiccu.conf or in the same directory as the binary.
For the UNIX versions store in /etc/ or the path which got configured at compile time.

Alternatives

Below listed are a few alternative implementations of the TIC/heartbeat/AYIYA protocols that can be used instead of AICCU.

• AVM Fritz!Box
  • Embedded into AVM Fritz!Box with easy configuration from web interface
  • Custom implementation (read: not based on AICCU)
  • Supports TIC and heartbeat (no AYIYA support)
• Android
  • IPv6Droid
    • Available from Google Play Store
    • Android 4.0+ (due to VpnService) tested till 5.0
    • Custom implementation of TIC and AYIYA protocols in Java using VpnService
    • Does not require rooting of device
    • Provided by Andreas Feldner
  • Androiccu
    • Available from Google Play Store
    • Android 2.2 and up (last updated 12 June 2013 though)
    • Provides a handy frontend to AICCU for use on Android devices
    • Requires rooting the device
    • Provided by Martin Herren