Stack Setup

Tinc is a fantastic, mesh based VPN. It can be used to build a secure, encrypted pseudo-VLAN over the public internet. Tinc is a fairly complicated process so this page is broken down into sections:


Below is an example directory tree for Tinc, which all participating nodes must hold:

hosts/ contains files, each representing a node in the Tinc network. Nodes which directly connect to each other will need to have each others hosts files. Nodes which don't directly connect will exchange keys automatically over the Tinc network once they join it. Each file contains details of the nodes public IP, private IP and the public RSA key.

tinc.conf tells the local server where to connect to, what device to use and what mode to use. The file will basically be the same for all hosts in the network:


tinc-up and tinc-down are executed by the Tinc daemon upon starting and ending, these are useful to actually bring the Tinc interface online and setup routes so your server knows how to talk to the Tinc network.

rsa_key.priv is the private key of the local server.

Installing Tinc

When installing Tinc remember it is important that the protocol versions (not the same as Tinc versions) match up across your network. I would advise using the same Tinc version on all nodes to make this easier. It's very easy to compile Tinc yourself, you will need headers/devel versions of the following: libssl, liblzo, libzlib.

tar -xf tinc-1.0.23.tar.gz
cd tinc-1.0.23
./configure --prefix=
sudo make install

Basic two node Tinc setup

For this second we're going to deploy two servers to talk to each other via Tinc, I shall refer to them as the 'master' and 'client'. Note that technically Tinc is a mesh network, so there's no real 'master' server, simply a node which doesn't connect to any others, but is connected to. This is great because we can use multiple ConnectTo statements in tinc.conf to achieve a highly-available VPN. For this we are building our Tinc network on the VPN which allows us to use addresses in the range => We will set the master on and the client on

We're going to call our VPN interface vpn, so on both servers install Tinc as per the above instructions and then lets create some directories/files we're going to use:

mkdir -p /etc/tinc/vpn/hosts/
touch /etc/tinc/vpn/tinc.conf
touch /etc/tinc/vpn/tinc-up
touch /etc/tinc/vpn/tinc-down

Firstly, let's edit tinc.conf on the master:


And on the client:


Now we've named each machine, we're ready to have Tinc generate private/public key pairs for each node. On each run:

tincd -n vpn -K4096
Please enter a file to save private RSA key to [/etc/tinc/vpn/rsa_key.priv]: 
Please enter a file to save public RSA key to [/etc/tinc/vpn/hosts/master]:

Save the keys with the default names (/etc/tinc/vpn/hosts/master and /etc/tinc/vpn/hosts/client). Now let's setup these files completely. On the master edit /etc/tinc/vpn/hosts/master, and put at the top:



And do exactly the same on the client to /etc/tinc/vpn/hosts/client, except change the address to Next you need to copy the hosts/client file to the master node and the hosts/master file to the client node, so both nodes have identical copies of both hosts/master and hosts/client. That's everything directly Tinc related complete!

However, the network won't run yet, we need to edit tinc-up and tinc-down on each node to setup the interface, IP (must be configured in tinc-up AND the hosts file) and routing. These files will look very similar on both master & client, only the IP of the interface will change:

$ cat tinc-up:
# Up tinc, add IP
ifconfig vpn IP_TO_CHANGE netmask up
route add -net netmask gw dev vpn

All you do is replace IP_TO_CHANGE with the IP of whichever node you are on (master or client). Note the gateway IP is, the IP of the master. Finally:

$ cat tinc-down:
# Down tinc
ifconfig vpn down

And, that should be that! Just run sudo tincd -n vpn on each box and hopefully they should both be able to ping each other on and Not working? Checkout the debug section below to ways to find out what's going wrong:

Debugging Tinc

Tinc isn't the most user friendly application, and documentation is scarce, especially when you're seeing weird routing or network issues. Luckily there's a bunch of things we can use to get more information from Tinc. The best is simply running in the foregroud with a high debug level:

tincd -D -d 5

-D keeps tincd in the foreground and -d sets the debug level (0-5). Once running, ctrl+c to switch between debug levels.

It's also possible to get some information out of running daemon tincd's: