AICCU

Last updated
AICCU
Original author(s) Jeroen Massar
Initial releaseAugust 1, 2004;19 years ago (2004-08-01) [1]
Stable release 2012-02-02 (February 2, 2012;11 years ago (2012-02-02)) [±]
Preview release Non [±]
Written in C
Operating system Cross-platform
Available inEnglish
Type Internet
License 3-clause BSD
Website www.sixxs.net/tools/aiccu/

AICCU (Automatic IPv6 Connectivity Client Utility) was a popular [2] cross-platform utility for automatically configuring an IPv6 tunnel. It is free software available under a BSD license. The utility was originally provided for the SixXS Tunnel Broker but it can also be used by a variety of other tunnel brokers.

Contents

History and development

AICCU was written and maintained by Jeroen Massar. Various patches from other persons have been incorporated, these persons are acknowledged in the field [3] for their contributions. AICCU is the successor of the Windows-only and Linux/BSD-variety of the Heartbeat tool that was provided by SixXS, solely to use the Heartbeat protocol. When the AYIYA protocol came into existence it was decided that to support this new protocol it would be better to merge the Windows and Unix trees into one program and give it a better appearance. The name of the Heartbeat tool was then changed to reflect that it did more than providing mere support for the heartbeats.

Award of excellence

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

Supported protocols

The following tunneling protocols are currently supported:

AICCU primarily uses the TIC protocol to retrieve the configuration parameters of the tunnel automatically that the user wants to have configured.

Support for other tunnel brokers

AICCU finds available tunnel brokers by looking up the TXT DNS records from "_aiccu.sixxs.net". [5] The latter allowed a local network to add their own tunnel broker(s) by adding records in the domains configured in their search path. Non-local tunnel brokers could then be added by requesting the SixXS staff to add an entry to the global DNS records.

Supported platforms

The following operating systems/platforms/distributions are supported by AICCU:

Various distributions have an AICCU package included in their distribution. [6] [7] [8] [9] [10] [11] [12]

Usage

The main usage of AICCU was in combination with the SixXS tunnel broker service.

There are other ISPs who have implemented parts of the protocols that AICCU support, for instance the Czech ISP NetBox uses AICCU to configure tunnels automatically for their users [13] by providing a TIC (Tunnel Information and Control protocol) implementation that ignores the username/password/tunnel_id but uses the source address where the TIC connection originates from to determine and return the tunnel configuration using the TIC protocol, which AICCU then uses to configure the tunnel.

See also

Free and open-source software logo (2009).svg  Free softwareportal

Related Research Articles

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

A virtual private network (VPN) is a mechanism for creating a secure connection between a computing device and a computer network, or between two networks, using an insecure communication medium such as the public Internet.

Zero-configuration networking (zeroconf) is a set of technologies that automatically creates a usable computer network based on the Internet Protocol Suite (TCP/IP) when computers or network peripherals are interconnected. It does not require manual operator intervention or special configuration servers. Without zeroconf, a network administrator must set up network services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), or configure each computer's network settings manually.

6to4 is an Internet transition mechanism for migrating from Internet Protocol version 4 (IPv4) to version 6 (IPv6) and a system that allows IPv6 packets to be transmitted over an IPv4 network without the need to configure explicit tunnels. Special relay servers are also in place that allow 6to4 networks to communicate with native IPv6 networks.

A BNC is a piece of software that is used to relay traffic and connections in computer networks, much like a proxy. Using a BNC allows a user to hide the original source of the user's connection, providing privacy as well as the ability to route traffic through a specific location. A BNC can also be used to hide the true target to which a user connects.

OpenVPN is a virtual private network (VPN) system that implements techniques to create secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities. It implements both client and server applications.

In computer networking, Teredo is a transition technology that gives full IPv6 connectivity for IPv6-capable hosts that are on the IPv4 Internet but have no native connection to an IPv6 network. Unlike similar protocols such as 6to4, it can perform its function even from behind network address translation (NAT) devices such as home routers.

In the context of computer networking, a tunnel broker is a service which provides a network tunnel. These tunnels can provide encapsulated connectivity over existing infrastructure to another infrastructure.

Anything In Anything (AYIYA) is a computer networking protocol for managing IP tunneling protocols in use between separated Internet Protocol networks. It is most often used to provide IPv6 transit over an IPv4 network link when network address translation masquerades a private network with a single IP address that may change frequently because of DHCP provisioning by Internet service providers.

In computer networking, a host model is an option of designing the TCP/IP stack of a networking operating system like Microsoft Windows or Linux. When a unicast packet arrives at a host, IP must determine whether the packet is locally destined. If the IP stack is implemented with a weak host model, it accepts any locally destined packet regardless of the network interface on which the packet was received. If the IP stack is implemented with a strong host model, it only accepts locally destined packets if the destination IP address in the packet matches an IP address assigned to the network interface on which the packet was received.

ISATAP is an IPv6 transition mechanism meant to transmit IPv6 packets between dual-stack nodes on top of an IPv4 network. It is defined in the informational RFC 5214.

This article presents a comparison of the features, platform support, and packaging of many independent implementations of Domain Name System (DNS) name server software.

The domain name .local is a special-use domain name reserved by the Internet Engineering Task Force (IETF) so that it may not be installed as a top-level domain in the Domain Name System (DNS) of the Internet. As such it is similar to the other special domain names, such as .localhost. However, .local has since been designated for use in link-local networking, in applications of multicast DNS (mDNS) and zero-configuration networking (zeroconf) so that DNS service may be established without local installations of conventional DNS infrastructure on local area networks.

The Dynamic Host Configuration Protocol version 6 (DHCPv6) is a network protocol for configuring Internet Protocol version 6 (IPv6) hosts with IP addresses, IP prefixes, default route, local segment MTU, and other configuration data required to operate in an IPv6 network. It is not just the IPv6 equivalent of the Dynamic Host Configuration Protocol for IPv4.

6in4 is an IPv6 transition mechanism for migrating from Internet Protocol version 4 (IPv4) to IPv6. It is a tunneling protocol that encapsulates IPv6 packets on specially configured IPv4 links according to the specifications of RFC 4213. The IP protocol number for 6in4 is 41, per IANA reservation.

In computer networking, the Tunnel Setup Protocol (TSP) is an experimental networking control protocol used to negotiate IP tunnel setup parameters between a tunnel client host and a tunnel broker server, the tunnel end-points. A major use of TSP is in IPv6 transition mechanisms.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

NicheStack is a closed source IPv4 network layer and application implementation for operating systems, written in ANSI "C" and is one of three available from InterNiche Technologies, Inc., designed for use in embedded systems. Its transport layer implementation has historical roots in BSD and the IP layer was derived from a Carnegie Mellon University (CMU) implementation.

This is a comparison of operating systems in regard to their support of the IPv6 protocol.

WireGuard is a communication protocol and free and open-source software that implements encrypted virtual private networks (VPNs), and was designed with the goals of ease of use, high speed performance, and low attack surface. It aims for better performance and more power than IPsec and OpenVPN, two common tunneling protocols. The WireGuard protocol passes traffic over UDP.

References

  1. 1 August 2004 (beta1)
  2. AICCU - Changelog
  3. 2004 Edition of the IPv6 Application Contest
  4. AICCU - Tunnelbroker Support Archived October 26, 2006, at the Wayback Machine
  5. Debian AICCU package
  6. Gentoo AICCU package Archived December 3, 2008, at the Wayback Machine
  7. Ubuntu 10.04 LTS (Lucid) AICCU package
  8. OpenWRT AICCU package Archived July 27, 2011, at the Wayback Machine
  9. Red Hat AICCU package Archived May 26, 2008, at the Wayback Machine
  10. FreeBSD AICCU package
  11. NetBSD AICCU package Archived July 6, 2008, at the Wayback Machine
  12. "AICCU usage at NetBox (Czech language)". Archived from the original on 2012-10-08. Retrieved 2012-09-28.