Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tayga(8) [debian man page]

TAYGA(8)																  TAYGA(8)

NAME

       tayga - stateless NAT64 daemon

SYNOPSIS

       tayga [OPTION]...

       tayga --mktun [OPTION]...

       tayga --rmtun [OPTION]...

DESCRIPTION

       TAYGA  is a stateless NAT64 daemon for Linux.  Using the in-kernel TUN network driver, TAYGA receives IPv4 and IPv6 packets from the host's
       network stack, translates them to the other protocol, and then sends the translated packets back to the host using the same TUN interface.

       Translation is compliant with IETF Internet-Draft draft-ietf-behave-v6v4-xlate-23, and address mapping is performed in accordance with  RFC
       6052.  Optionally, TAYGA may be configured to dynamically map IPv6 hosts to addresses drawn from a configured IPv4 address pool.

       As  a stateless NAT, TAYGA requires a one-to-one mapping between IPv4 addresses and IPv6 addresses.  Mapping multiple IPv6 addresses onto a
       single IPv4 address can be achieved by mapping IPv6 addresses to private IPv4 addresses with TAYGA and then using a stateful NAT44 (such as
       the iptables(8) MASQUERADE target) to map the private IPv4 addresses onto the desired single IPv4 address.

       TAYGA's configuration is stored in the tayga.conf(5) file, which is usually found in /etc/tayga.conf or /usr/local/etc/tayga.conf.

INVOCATION

       Without the --mktun or --rmtun options, the `tayga` executable runs as a daemon, translating packets as described above.

       The  --mktun  and  --rmtun options instruct TAYGA to create or destroy, respectively, its configured TUN device as a "persistent" interface
       and then immediately exit.

       Persistent TUN devices remain present on the host system even when TAYGA is not running.  This  allows  host-side  network  parameters  and
       firewall  rules	to  be	configured  prior to commencement of packet translation.  This may simplify network configuration on the host; for
       example, systems which use a Debian-style /etc/network/interfaces file may configure TAYGA's TUN device at boot by running `tayga  --mktun`
       as a "pre-up" command and then configuring the TUN device as any other network interface.

OPTIONS

       -c configfile | --config configfile
	      Read configuration options from configfile

       -d     Enable debug messages (enables --nodetach as well)

       -n | --nodetach
	      Do not detach from terminal

       -u userid | --user userid
	      Set uid to userid after initialization

       -g groupid | --group groupid
	      Set gid to groupid after initialization

       -r | --chroot
	      chroot() to data-dir (specified in config file)

       -p pidfile | --pidfile pidfile
	      Write process ID of daemon to pidfile

AUTHOR

       Written by Nathan Lutchansky <lutchann@litech.org>

COPYRIGHT

       Copyright (C) 2010 Nathan Lutchansky
       License GPLv2+: GNU GPL version 2 or later
       This is free software: you are free to change and redistribute it.  There is NO WARRANTY, to the extent permitted by law.

SEE ALSO

       tayga.conf(5)
       <http://www.litech.org/tayga/>

TAYGA 0.9.2							     June 2011								  TAYGA(8)

Check Out this Related Man Page

FAITH(4)						   BSD Kernel Interfaces Manual 						  FAITH(4)

NAME

     faith -- IPv6-to-IPv4 TCP relay capturing interface

SYNOPSIS

     device faith

DESCRIPTION

     The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).

     Each faith interface is created at runtime using interface cloning.  This is most easily done with the ifconfig(8) create command or using
     the cloned_interfaces variable in rc.conf(5).

     Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
     In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router.  The
     packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs.  As a result, faith
     will let you capture IPv6 TCP traffic to some specific destination addresses.  Userland programs, such as faithd(8) can use this behavior to
     relay IPv6 TCP traffic to IPv4 TCP traffic.  The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
     destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.

     The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.

     To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.

     To understand how faith can be used, take a look at the source code of faithd(8).

     As the faith interface implements potentially dangerous operations, great care must be taken when configuring it.	To avoid possible misuse,
     the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface.  When net.inet6.ip6.keepfaith is 0, no packets
     will be captured by the faith interface.

     The faith interface is intended to be used on routers, not on hosts.

SEE ALSO

     inet(4), inet6(4), faithd(8)

     Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.

HISTORY

     The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.

BSD
								  April 10, 1999							       BSD
Man Page