3 tinc - mesh peer to peer VPN
30 Tinc implements the mesh peer to peer VPN protocol from
31 .I https://www.tinc-vpn.org/
32 as of version 1.0.32. Within a tinc VPN one can reach all
33 the subnets of all hosts within the network even when not
34 directly connected to the owning host of the subnet.
36 Each host that is directly connected to us has its own hostfile under
37 .IR confdir /hosts/ hostname
38 containing its public address, owned subnets, options and RSA public key.
39 The hostfile format is the same as the original tinc implementation.
44 option or defaults to the current working directory.
45 Other hosts might exist behind these directly connected nodes but
46 this information is distributed automatically within the protocol.
50 creates an ip interface with the address
56 ip stack (specified with
58 option) and starts listening for incoming connections on the
60 ip stack (specified with the
62 option). When optional
64 are specified on the command line, then it will also do outgoing connections
69 usually is a supernet of all the subnets within the VPN. Our own hostname
73 option or is assumed to be the
76 This host's RSA private key needs to be present in factotum and tagged with
84 Enable debug output and do not fork to the background.
87 Limit the number of client processes (incoming and
88 outgoing connections per protocol) to
96 network stack directory where the tinc ip interface is bound. Defaults to
102 network stack directory where incoming and outgoing tinc connections
103 are made. Defaults to
107 Specifies the configuration directory
118 .I https://www.tinc-vpn.org/documentation/
120 .B /sys/src/cmd/ip/tinc.c
123 first appeared in 9front (October, 2017).