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 the SixXS Staff by email info@sixxs.net.

User contributed information can be found in the Wiki.

Announce Mailinglist

The AICCU-announce mailinglist exists for people who want to get notifications of new AICCU releases. The list is announce only and all messages are hand approved. As such traffic is very low. Releases of new versions are also published on the News pages.

License

This software comes with an Open Source LICENSE.

Downloads

Latest Windows GUI version: 2006.07.23
Latest Windows console version: 2008.03.15
Latest UNIX/Console version: 2007.01.15

• Source:
  • source tarball [tar.gz]
• Windows XP, Windows .Net, Windows Vista, and Windows 2000
  • GUI/Service [exe]
  • Console [exe]
  • For AYIYA support on Windows the Tun/Tap32 driver from the OpenVPN project is needed. AICCU upto 2006.07.23 only support the tap801 version of the driver. Newer AICCU support tap801, tap802 and tap901.
    • Tap32 Driver (tap801) [zip] - Windows XP and Windows 2000
    • Tap64 Driver (tap801) [zip] - Windows XP 64bit (not tested)
    • Tap32 Driver (tap901) [zip] - Windows Vista, Windows XP, Windows 2000
• 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
  • 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:
    • (untested) SUSE packages provided by Robert Schiele [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
  • 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)
  • Requires the tun/tap driver to build
• 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.

An example configuration file: aiccu.conf
For the Windows version store as c:\windows\aiccu.conf, though better use the GUI interface to create it
For the UNIX versions store in /etc/ or the path which got configured at compile time.
This configuration file is not required for the Windows GUI version as it will create it based on the input given using the GUI and the user manually saving it.