| Application | Package | Version | Worked By | URLs | Comment | Status |
|---|---|---|---|---|---|---|
| NAT-PT | ||||||
naptd | naptd | 0.4.2 | Maintainers |
| NAT-PT (Network Address Translation - Protocol Translation) is an IETF RFC specification for an IPv4 to IPv6 protocol translator. This is a NAT-PT implementation for the Linux platform designed to run in userspace. |  |
| IPv4-to-IPv6 and IPv6-to-IPv4 Bouncers | ||||||
46Bouncer | 46Bouncer | 3.0 | Maintainers |
| 46Bouncer is a very simple tool that is able to accept TCP/UDP connections in IPv4/6 and forward them to an application in IPv6/4. In other words, it acts as a proxy between the IPv4 and IPv6 world (and vice versa). | |
| Dynamic Tunnel Configuration Protocol | ||||||
dtcpc and dtcps | dtcp | 20030228 | Maintainers |
| dtcpc and dtcps implement the server part of the Dynamic Tunnel Configuration Protocol (DTCP for short) proposed by Trumpet: http://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm | |
dtcpclient | dtcpclient | 20030324 | Maintainers |
| dtcpclient implement the client part of the Dynamic Tunnel Configuration Protocol (DTCP for short) proposed by Trumpet: http://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm | |
| Teredo | ||||||
ng_teredo | ng_teredo | 1.13 | Maintainers |
| Teredo allows nodes located behind an IPv4 NAT to obtain IPv6 unicast connectivity by tunnelling packets over UDP/IPv4. This service has 3 entities: the "Teredo Server", the "Teredo Relay" and the "Teredo client". A Teredo Server is stateless whereas the Teredo Relay keeps a state of each peer. ng_teredo is a Teredo implementation for FreeBSD. | |
miredo | miredo | (implicit IPv6 support) | Maintainers |
| Miredo is a Unix daemon which implements the "Teredo: Tunneling IPv6 over UDP through NATs" Internet draft specification. It can be used to provide IPv6 connectivity to users behind NATs which do not support IPv6 or even Proto-41 forwarding. For this to work, users need to have Teredo clients running on their systems. Miredo runs on GNU/Linux and BSD. | |
| Bump-in-the-API (BIA) | ||||||
BIAsed | BIAsed | (implicit IPv6 support) | Maintainers |
| BIAsed is an explanation and partial implementation of the "Bump-in-the-API" (BIA) technique, which allows for the hosts to communicate with other IPv6 hosts using existing IPv4 applications. | |
| NAT64 | ||||||
TAYGA | tayga | (implicit IPv6 support) | Maintainers |
| TAYGA is an out-of-kernel stateless NAT64 implementation for Linux that uses the TUN driver to exchange IPv4 and IPv6 packets with the kernel. It is intended to provide production-quality NAT64 service for networks where dedicated NAT64 hardware would be overkill. | |
| Transport Relay Translator | ||||||
pTRTd | pTRTd | 0.5.2 | Maintainers |
| The Portable Transport Relay Translator Daemon (pTRTd) is a method of allowing IPv6 hosts to communicate with IPv4 hosts. It is a TRT as specified by RFC 3142, similar to the Faith package implemented by the KAME project. However, unlike Faith, it doesn't depend on special support in the kernel IPv6 stack, and thus should be fairly easy to port to most Unix-like operating systems. Since December 2010 this project is officially declared as dead! |  |