Section: Maintenance Commands (8)
Updated: 17 Aug 2009
Return to Main Contents
tunnelit-p2p - Tunnel Ethernet links over TCP or UDP
[ -VFhluo ]
is a utility to tunnel Ethernet links over a TCP or a UDP socket. This is done by creating a local interface (using the TUN/TAP driver) on two systems that can reach each other over TCP or UDP, and forwarding whatever is received by one to the other. It is intentionally simple, and has no authentication or encryption. The same client program is used on both the sender and the receiver.
Print version and exit
Run in foreground, the default behavior is to background after creating the TUN/TAP interface.
Print usage information and exit in success.
Be a listener, the default action is to connect to a remote host
Use a UDP socket instead of a TCP socket. This option implies the
Only allow one host to connect to our listener. It is generally a good idea to only have one host connect to a listener for bandwidth reasons. Anything received by one socket is transmitted to all connected sockets.
Specify the port to connect to the remote host (specified using the
option) on, or to listen on if the
option was specified. The default is 656.
Specify the host to connect to. Can be either a DNS name or an IP address. This option is required unless the
option is specified.
Specify the local TUN/TAP device name to create. The default is to let the system decide (usually "tap%d"). It can include a "%d" to indicate a numeric value should be generated for you. (i.e., "eth%d" will create an interface named "eth3" if you already have "eth0", "eth1", and "eth2").
Specify the path to TUN/TAP user-space interface (i.e., "/dev/net/tun").
Specify how often, in seconds, to send empty keep-alive packets to maintain the connection. The value 0 may be used to specify that keep-alives are never sent. The default is 900 seconds.
This document was created by
using the manual pages.
Time: 13:56:16 GMT, August 17, 2009