| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 4.1 Configuration introduction | ||
| 4.2 Multiple networks | ||
| 4.3 How connections work | ||
| 4.4 Configuration files | ||
| 4.5 Generating keypairs | ||
| 4.6 Network interfaces | ||
| 4.7 Example configuration |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Before actually starting to configure tinc and editing files, make sure you have read this entire section so you know what to expect. Then, make it clear to yourself how you want to organize your VPN: What are the nodes (computers running tinc)? What IP addresses/subnets do they have? What is the network mask of the entire VPN? Do you need special firewall rules? Do you have to set up masquerading or forwarding rules? Do you want to run tinc in router mode or switch mode? These questions can only be answered by yourself, you will not find the answers in this documentation. Make sure you have an adequate understanding of networks in general. A good resource on networking is the Linux Network Administrators Guide.
If you have everything clearly pictured in your mind, proceed in the following order: First, generate the configuration files (‘tinc.conf’, your host configuration file, ‘tinc-up’ and perhaps ‘tinc-down’). Then generate the keypairs. Finally, distribute the host configuration files. These steps are described in the subsections below.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In order to allow you to run more than one tinc daemon on one computer, for instance if your computer is part of more than one VPN, you can assign a netname to your VPN. It is not required if you only run one tinc daemon, it doesn’t even have to be the same on all the sites of your VPN, but it is recommended that you choose one anyway.
We will asume you use a netname throughout this document. This means that you call tincd with the -n argument, which will assign a netname to this daemon.
The effect of this is that the daemon will set its configuration root to ‘/etc/tinc/netname/’, where netname is your argument to the -n option. You’ll notice that it appears in syslog as ‘tinc.netname’.
However, it is not strictly necessary that you call tinc with the -n option. In this case, the network name would just be empty, and it will be used as such. tinc now looks for files in ‘/etc/tinc/’, instead of ‘/etc/tinc/netname/’; the configuration file should be ‘/etc/tinc/tinc.conf’, and the host configuration files are now expected to be in ‘/etc/tinc/hosts/’.
But it is highly recommended that you use this feature of tinc, because it will be so much clearer whom your daemon talks to. Hence, we will assume that you use it.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When tinc starts up, it parses the command-line options and then reads in the configuration file tinc.conf. If it sees one or more ‘ConnectTo’ values pointing to other tinc daemons in that file, it will try to connect to those other daemons. Whether this succeeds or not and whether ‘ConnectTo’ is specified or not, tinc will listen for incoming connection from other deamons. If you did specify a ‘ConnectTo’ value and the other side is not responding, tinc will keep retrying. This means that once started, tinc will stay running until you tell it to stop, and failures to connect to other tinc daemons will not stop your tinc daemon for trying again later. This means you don’t have to intervene if there are temporary network problems.
There is no real distinction between a server and a client in tinc. If you wish, you can view a tinc daemon without a ‘ConnectTo’ value as a server, and one which does specify such a value as a client. It does not matter if two tinc daemons have a ‘ConnectTo’ value pointing to each other however.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The actual configuration of the daemon is done in the file ‘/etc/tinc/netname/tinc.conf’ and at least one other file in the directory ‘/etc/tinc/netname/hosts/’.
These file consists of comments (lines started with a #) or assignments in the form of
Variable = Value. |
The variable names are case insensitive, and any spaces, tabs, newlines and carriage returns are ignored. Note: it is not required that you put in the ‘=’ sign, but doing so improves readability. If you leave it out, remember to replace it with at least one space character.
The server configuration is complemented with host specific configuration (see the next section). Although all host configuration options for the local node listed in this document can also be put in ‘/etc/tinc/netname/tinc.conf’, it is recommended to put host specific configuration options in the host configuration file, as this makes it easy to exchange with other nodes.
In this section all valid variables are listed in alphabetical order. The default value is given between parentheses, other comments are between square brackets.
| 4.4.1 Main configuration variables | ||
| 4.4.2 Host configuration variables | ||
| 4.4.3 Scripts | ||
| 4.4.4 How to configure |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This option affects the address family of listening and outgoing sockets. If any is selected, then depending on the operating system both IPv4 and IPv6 or just IPv6 listening sockets will be created.
If your computer has more than one IPv4 or IPv6 address, tinc will by default listen on all of them for incoming connections. Multiple BindToAddress variables may be specified, in which case listening sockets for each specified address are made.
If no port is specified, the socket will be bound to the port specified by the Port option, or to port 655 if neither is given. To only bind to a specific port but not to a specific address, use "*" for the address.
This option may not work on all platforms.
If you have more than one network interface in your computer, tinc will by default listen on all of them for incoming connections. It is possible to bind tinc to a single interface like eth0 or ppp0 with this variable.
This option may not work on all platforms.
This option selects the way broadcast packets are sent to other daemons. NOTE: all nodes in a VPN must use the same Broadcast mode, otherwise routing loops can form.
Broadcast packets are never sent to other nodes.
Broadcast packets are sent and forwarded via the VPN’s Minimum Spanning Tree. This ensures broadcast packets reach all nodes.
Broadcast packets are sent directly to all nodes that can be reached directly. Broadcast packets received from other nodes are never forwarded. If the IndirectData option is also set, broadcast packets will only be sent to nodes which we have a meta connection to.
Specifies which other tinc daemon to connect to on startup. Multiple ConnectTo variables may be specified, in which case outgoing connections to each specified tinc daemon are made. The names should be known to this tinc daemon (i.e., there should be a host configuration file for the name on the ConnectTo line).
If you don’t specify a host with ConnectTo, tinc won’t try to connect to other daemons at all, and will instead just listen for incoming connections.
When enabled, tinc will decrement the Time To Live field in IPv4 packets, or the Hop Limit field in IPv6 packets, before forwarding a received packet to the virtual network device or to another node, and will drop packets that have a TTL value of zero, in which case it will send an ICMP Time Exceeded packet back.
Do not use this option if you use switch mode and want to use IPv6.
The virtual network device to use. Tinc will automatically detect what kind of device it is. Note that you can only use one device per daemon. Under Windows, use Interface instead of Device. Note that you can only use one device per daemon. See also Device files.
The type of the virtual network device. Tinc will normally automatically select the right type of tun/tap interface, and this option should not be used. However, this option can be used to select one of the special interface types, if support for them is compiled in.
Use a dummy interface. No packets are ever read or written to a virtual network device. Useful for testing, or when setting up a node that only forwards packets for other nodes.
Open a raw socket, and bind it to a pre-existing Interface (eth0 by default). All packets are read from this interface. Packets received for the local node are written to the raw socket. However, at least on Linux, the operating system does not process IP packets destined for the local host.
Open a multicast UDP socket and bind it to the address and port (separated by spaces) and optionally a TTL value specified using Device. Packets are read from and written to this multicast socket. This can be used to connect to UML, QEMU or KVM instances listening on the same multicast address. Do NOT connect multiple tinc daemons to the same multicast address, this will very likely cause routing loops. Also note that this can cause decrypted VPN packets to be sent out on a real network if misconfigured.
Create a UNIX socket with the filename specified by Device, or ‘/var/run/netname.umlsocket’ if not specified. Tinc will wait for a User Mode Linux instance to connect to this socket.
Uses the libvdeplug library to connect to a Virtual Distributed Ethernet switch, using the UNIX socket specified by Device, or ‘/var/run/vde.ctl’ if not specified.
Also, in case tinc does not seem to correctly interpret packets received from the virtual network device, it can be used to change the way packets are interpreted:
Set type to tun. Depending on the platform, this can either be with or without an address family header (see below).
Set type to tun without an address family header. Tinc will expect packets read from the virtual network device to start with an IP header. On some platforms IPv6 packets cannot be read from or written to the device in this mode.
Set type to tun with an address family header. Tinc will expect packets read from the virtual network device to start with a four byte header containing the address family, followed by an IP header. This mode should support both IPv4 and IPv6 packets.
Set type to tap. Tinc will expect packets read from the virtual network device to start with an Ethernet header.
When this option is enabled, packets that cannot be sent directly to the destination node, but which would have to be forwarded by an intermediate node, are dropped instead. When combined with the IndirectData option, packets for nodes for which we do not have a meta connection with are also dropped.
This option selects the way indirect packets are forwarded.
Incoming packets that are not meant for the local node, but which should be forwarded to another node, are dropped.
Incoming packets that are meant for another node are forwarded by tinc internally.
This is the default mode, and unless you really know you need another forwarding mode, don’t change it.
Incoming packets are always sent to the TUN/TAP device, even if the packets are not for the local node. This is less efficient, but allows the kernel to apply its routing and firewall rules on them, and can also help debugging.
If this option is present, tinc will dump the current network graph to the file filename every minute, unless there were no changes to the graph. The file is in a format that can be read by graphviz tools. If filename starts with a pipe symbol |, then the rest of the filename is interpreted as a shell command that is executed, the graph is then sent to stdin.
This option selects whether IP addresses (both real and on the VPN) should be resolved. Since DNS lookups are blocking, it might affect tinc’s efficiency, even stopping the daemon for a few seconds everytime it does a lookup if your DNS server is not responding.
This does not affect resolving hostnames to IP addresses from the configuration file.
Defines the name of the interface corresponding to the virtual network device. Depending on the operating system and the type of device this may or may not actually set the name of the interface. Under Windows, this variable is used to select which network interface will be used. If you specified a Device, this variable is almost always already correctly set.
When enabled, tinc will try to detect peers that are on the same local network. This will allow direct communication using LAN addresses, even if both peers are behind a NAT and they only ConnectTo a third node outside the NAT, which normally would prevent the peers from learning each other’s LAN address.
Currently, local discovery is implemented by sending broadcast packets to the LAN during path MTU discovery. This feature may not work in all possible situations.
This option selects the way packets are routed to other daemons.
In this mode Subnet variables in the host configuration files will be used to form a routing table. Only unicast packets of routable protocols (IPv4 and IPv6) are supported in this mode.
This is the default mode, and unless you really know you need another mode, don’t change it.
In this mode the MAC addresses of the packets on the VPN will be used to dynamically create a routing table just like an Ethernet switch does. Unicast, multicast and broadcast packets of every protocol that runs over Ethernet are supported in this mode at the cost of frequent broadcast ARP requests and routing table updates.
This mode is primarily useful if you want to bridge Ethernet segments.
This mode is almost the same as the switch mode, but instead every packet will be broadcast to the other daemons while no routing table is managed.
This option controls the time the encryption keys used to encrypt the data are valid. It is common practice to change keys at regular intervals to make it even harder for crackers, even though it is thought to be nearly impossible to crack a single key.
This option controls the amount of time MAC addresses are kept before they are removed. This only has effect when Mode is set to "switch".
This is a symbolic name for this connection. The name should consist only of alfanumeric and underscore characters (a-z, A-Z, 0-9 and _).
If Name starts with a $, then the contents of the environment variable that follows will be used. In that case, invalid characters will be converted to underscores. If Name is $HOST, but no such environment variable exist, the hostname will be read using the gethostnname() system call.
The number of seconds of inactivity that tinc will wait before sending a probe to the other end.
The number of seconds to wait for a response to pings or to allow meta connections to block. If the other end doesn’t respond within this time, the connection is terminated, and the others will be notified of this.
When this option is enabled the value of the TOS field of tunneled IPv4 packets will be inherited by the UDP packets that are sent out.
This is the RSA private key for tinc. However, for safety reasons it is advised to store private keys of any kind in separate files. This prevents accidental eavesdropping if you are editting the configuration file.
This is the full path name of the RSA private key file that was generated by ‘tincd --generate-keys’. It must be a full path, not a relative directory.
Note that there must be exactly one of PrivateKey or PrivateKeyFile specified in the configuration file.
When this option is used the priority of the tincd process will be adjusted. Increasing the priority may help to reduce latency and packet loss on the VPN.
Use a proxy when making outgoing connections. The following proxy types are currently supported:
Connects to the proxy using the SOCKS version 4 protocol. Optionally, a username can be supplied which will be passed on to the proxy server.
Connect to the proxy using the SOCKS version 5 protocol. If a username and password are given, basic username/password authentication will be used, otherwise no authentication will be used.
Connects to the proxy and sends a HTTP CONNECT request.
Executes the given command which should set up the outgoing connection.
The environment variables NAME, NODE, REMOTEADDRES and REMOTEPORT are available.
This is the size of the replay tracking window for each remote node, in bytes. The window is a bitfield which tracks 1 packet per bit, so for example the default setting of 16 will track up to 128 packets in the window. In high bandwidth scenarios, setting this to a higher value can reduce packet loss from the interaction of replay tracking with underlying real packet loss and/or reordering. Setting this to zero will disable replay tracking completely and pass all traffic, but leaves tinc vulnerable to replay-based attacks on your traffic.
When this option is enabled tinc will only use Subnet statements which are present in the host config files in the local ‘/etc/tinc/netname/hosts/’ directory.
When this option is enabled tinc will no longer forward information between other tinc daemons, and will only allow connections with nodes for which host config files are present in the local ‘/etc/tinc/netname/hosts/’ directory. Setting this options also implicitly sets StrictSubnets.
Sets the socket receive buffer size for the UDP socket, in bytes. If unset, the default buffer size will be used by the operating system.
Sets the socket send buffer size for the UDP socket, in bytes. If unset, the default buffer size will be used by the operating system.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This variable is only required if you want to connect to this host. It must resolve to the external IP address where the host can be reached, not the one that is internal to the VPN. If no port is specified, the default Port is used.
The symmetric cipher algorithm used to encrypt UDP packets. Any cipher supported by OpenSSL is recognized. Furthermore, specifying "none" will turn off packet encryption. It is best to use only those ciphers which support CBC mode.
This option specifies whether tinc should clamp the maximum segment size (MSS) of TCP packets to the path MTU. This helps in situations where ICMP Fragmentation Needed or Packet too Big messages are dropped by firewalls.
This option sets the level of compression used for UDP packets. Possible values are 0 (off), 1 (fast zlib) and any integer up to 9 (best zlib), 10 (fast lzo) and 11 (best lzo).
The digest algorithm used to authenticate UDP packets. Any digest supported by OpenSSL is recognized. Furthermore, specifying "none" will turn off packet authentication.
This option specifies whether other tinc daemons besides the one you specified with ConnectTo can make a direct connection to you. This is especially useful if you are behind a firewall and it is impossible to make a connection from the outside to your tinc daemon. Otherwise, it is best to leave this option out or set it to no.
The length of the message authentication code used to authenticate UDP packets. Can be anything from 0 up to the length of the digest produced by the digest algorithm.
This option controls the initial path MTU to this node.
When this option is enabled, tinc will try to discover the path MTU to this node. After the path MTU has been discovered, it will be enforced on the VPN.
This is the port this tinc daemon listens on. You can use decimal portnumbers or symbolic names (as listed in ‘/etc/services’).
This is the RSA public key for this host.
This is the full path name of the RSA public key file that was generated by ‘tincd --generate-keys’. It must be a full path, not a relative directory.
From version 1.0pre4 on tinc will store the public key directly into the host configuration file in PEM format, the above two options then are not necessary. Either the PEM format is used, or exactly one of the above two options must be specified in each host configuration file, if you want to be able to establish a connection with that host.
The subnet which this tinc daemon will serve. Tinc tries to look up which other daemon it should send a packet to by searching the appropiate subnet. If the packet matches a subnet, it will be sent to the daemon who has this subnet in his host configuration file. Multiple subnet lines can be specified for each daemon.
Subnets can either be single MAC, IPv4 or IPv6 addresses, in which case a subnet consisting of only that single address is assumed, or they can be a IPv4 or IPv6 network address with a prefixlength. For example, IPv4 subnets must be in a form like 192.168.1.0/24, where 192.168.1.0 is the network address and 24 is the number of bits set in the netmask. Note that subnets like 192.168.1.1/24 are invalid! Read a networking HOWTO/FAQ/guide if you don’t understand this. IPv6 subnets are notated like fec0:0:0:1::/64. MAC addresses are notated like 0:1a:2b:3c:4d:5e.
Prefixlength is the number of bits set to 1 in the netmask part; for example: netmask 255.255.255.0 would become /24, 255.255.252.0 becomes /22. This conforms to standard CIDR notation as described in RFC1519
A Subnet can be given a weight to indicate its priority over identical Subnets owned by different nodes. The default weight is 10. Lower values indicate higher priority. Packets will be sent to the node with the highest priority, unless that node is not reachable, in which case the node with the next highest priority will be tried, and so on.
If this variable is set to yes, then the packets are tunnelled over a TCP connection instead of a UDP connection. This is especially useful for those who want to run a tinc daemon from behind a masquerading firewall, or if UDP packet routing is disabled somehow. Setting this options also implicitly sets IndirectData.
Since version 1.0.10, tinc will automatically detect whether communication via UDP is possible or not.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Apart from reading the server and host configuration files, tinc can also run scripts at certain moments. Under Windows (not Cygwin), the scripts should have the extension .bat.
This is the most important script. If it is present it will be executed right after the tinc daemon has been started and has connected to the virtual network device. It should be used to set up the corresponding network interface, but can also be used to start other things. Under Windows you can use the Network Connections control panel instead of creating this script.
This script is started right before the tinc daemon quits.
This script is started when the tinc daemon with name host becomes reachable.
This script is started when the tinc daemon with name host becomes unreachable.
This script is started when any host becomes reachable.
This script is started when any host becomes unreachable.
This script is started when a Subnet becomes reachable. The Subnet and the node it belongs to are passed in environment variables.
This script is started when a Subnet becomes unreachable.
The scripts are started without command line arguments, but can make use of certain environment variables. Under UNIX like operating systems the names of environment variables must be preceded by a $ in scripts. Under Windows, in ‘.bat’ files, they have to be put between % signs.
NETNAMEIf a netname was specified, this environment variable contains it.
NAMEContains the name of this tinc daemon.
DEVICEContains the name of the virtual network device that tinc uses.
INTERFACEContains the name of the virtual network interface that tinc uses. This should be used for commands like ifconfig.
NODEWhen a host becomes (un)reachable, this is set to its name. If a subnet becomes (un)reachable, this is set to the owner of that subnet.
REMOTEADDRESSWhen a host becomes (un)reachable, this is set to its real address.
REMOTEPORTWhen a host becomes (un)reachable, this is set to the port number it uses for communication with other tinc daemons.
SUBNETWhen a subnet becomes (un)reachable, this is set to the subnet.
WEIGHTWhen a subnet becomes (un)reachable, this is set to the subnet weight.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The main configuration file will be called ‘/etc/tinc/netname/tinc.conf’. Adapt the following example to create a basic configuration file:
Name = yourname Device = ‘/dev/tap0’ |
Then, if you know to which other tinc daemon(s) yours is going to connect, add ‘ConnectTo’ values.
If you added a line containing ‘Name = yourname’ in the main configuarion file, you will need to create a host configuration file ‘/etc/tinc/netname/hosts/yourname’. Adapt the following example to create a host configuration file:
Address = your.real.hostname.org Subnet = 192.168.1.0/24 |
You can also use an IP address instead of a hostname. The ‘Subnet’ specifies the address range that is local for your part of the VPN only. If you have multiple address ranges you can specify more than one ‘Subnet’. You might also need to add a ‘Port’ if you want your tinc daemon to run on a different port number than the default (655).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Now that you have already created the main configuration file and your host configuration file, you can easily create a public/private keypair by entering the following command:
tincd -n netname -K |
Tinc will generate a public and a private key and ask you where to put them. Just press enter to accept the defaults.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Before tinc can start transmitting data over the tunnel, it must set up the virtual network interface.
First, decide which IP addresses you want to have associated with these devices, and what network mask they must have.
Tinc will open a virtual network device (‘/dev/tun’, ‘/dev/tap0’ or similar), which will also create a network interface called something like ‘tun0’, ‘tap0’. If you are using the Linux tun/tap driver, the network interface will by default have the same name as the netname. Under Windows you can change the name of the network interface from the Network Connections control panel.
You can configure the network interface by putting ordinary ifconfig, route, and other commands to a script named ‘/etc/tinc/netname/tinc-up’. When tinc starts, this script will be executed. When tinc exits, it will execute the script named ‘/etc/tinc/netname/tinc-down’, but normally you don’t need to create that script.
An example ‘tinc-up’ script:
#!/bin/sh ifconfig $INTERFACE 192.168.1.1 netmask 255.255.0.0 |
This script gives the interface an IP address and a netmask. The kernel will also automatically add a route to this interface, so normally you don’t need to add route commands to the ‘tinc-up’ script. The kernel will also bring the interface up after this command. The netmask is the mask of the entire VPN network, not just your own subnet.
The exact syntax of the ifconfig and route commands differs from platform to platform. You can look up the commands for setting addresses and adding routes in Platform specific information, but it is best to consult the manpages of those utilities on your platform.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Imagine the following situation. Branch A of our example ‘company’ wants to connect three branch offices in B, C and D using the Internet. All four offices have a 24/7 connection to the Internet.
A is going to serve as the center of the network. B and C will connect to A, and D will connect to C. Each office will be assigned their own IP network, 10.x.0.0.
A: net 10.1.0.0 mask 255.255.0.0 gateway 10.1.54.1 internet IP 1.2.3.4 B: net 10.2.0.0 mask 255.255.0.0 gateway 10.2.1.12 internet IP 2.3.4.5 C: net 10.3.0.0 mask 255.255.0.0 gateway 10.3.69.254 internet IP 3.4.5.6 D: net 10.4.0.0 mask 255.255.0.0 gateway 10.4.3.32 internet IP 4.5.6.7 |
Here, “gateway” is the VPN IP address of the machine that is running the tincd, and “internet IP” is the IP address of the firewall, which does not need to run tincd, but it must do a port forwarding of TCP and UDP on port 655 (unless otherwise configured).
In this example, it is assumed that eth0 is the interface that points to the inner (physical) LAN of the office, although this could also be the same as the interface that leads to the Internet. The configuration of the real interface is also shown as a comment, to give you an idea of how these example host is set up. All branches use the netname ‘company’ for this particular VPN.
BranchA would be configured like this:
In ‘/etc/tinc/company/tinc-up’:
# Real interface of internal network: # ifconfig eth0 10.1.54.1 netmask 255.255.0.0 ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0 |
and in ‘/etc/tinc/company/tinc.conf’:
Name = BranchA Device = /dev/tap0 |
On all hosts, ‘/etc/tinc/company/hosts/BranchA’ contains:
Subnet = 10.1.0.0/16 Address = 1.2.3.4 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- |
Note that the IP addresses of eth0 and tap0 are the same. This is quite possible, if you make sure that the netmasks of the interfaces are different. It is in fact recommended to give both real internal network interfaces and tap interfaces the same IP address, since that will make things a lot easier to remember and set up.
In ‘/etc/tinc/company/tinc-up’:
# Real interface of internal network: # ifconfig eth0 10.2.43.8 netmask 255.255.0.0 ifconfig $INTERFACE 10.2.1.12 netmask 255.0.0.0 |
and in ‘/etc/tinc/company/tinc.conf’:
Name = BranchB ConnectTo = BranchA |
Note here that the internal address (on eth0) doesn’t have to be the same as on the tap0 device. Also, ConnectTo is given so that this node will always try to connect to BranchA.
On all hosts, in ‘/etc/tinc/company/hosts/BranchB’:
Subnet = 10.2.0.0/16 Address = 2.3.4.5 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- |
In ‘/etc/tinc/company/tinc-up’:
# Real interface of internal network: # ifconfig eth0 10.3.69.254 netmask 255.255.0.0 ifconfig $INTERFACE 10.3.69.254 netmask 255.0.0.0 |
and in ‘/etc/tinc/company/tinc.conf’:
Name = BranchC ConnectTo = BranchA Device = /dev/tap1 |
C already has another daemon that runs on port 655, so they have to reserve another port for tinc. It knows the portnumber it has to listen on from it’s own host configuration file.
On all hosts, in ‘/etc/tinc/company/hosts/BranchC’:
Address = 3.4.5.6 Subnet = 10.3.0.0/16 Port = 2000 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- |
In ‘/etc/tinc/company/tinc-up’:
# Real interface of internal network: # ifconfig eth0 10.4.3.32 netmask 255.255.0.0 ifconfig $INTERFACE 10.4.3.32 netmask 255.0.0.0 |
and in ‘/etc/tinc/company/tinc.conf’:
Name = BranchD ConnectTo = BranchC Device = /dev/net/tun |
D will be connecting to C, which has a tincd running for this network on port 2000. It knows the port number from the host configuration file. Also note that since D uses the tun/tap driver, the network interface will not be called ‘tun’ or ‘tap0’ or something like that, but will have the same name as netname.
On all hosts, in ‘/etc/tinc/company/hosts/BranchD’:
Subnet = 10.4.0.0/16 Address = 4.5.6.7 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- |
A, B, C and D all have generated a public/private keypair with the following command:
tincd -n company -K |
The private key is stored in ‘/etc/tinc/company/rsa_key.priv’, the public key is put into the host configuration file in the ‘/etc/tinc/company/hosts/’ directory. During key generation, tinc automatically guesses the right filenames based on the -n option and the Name directive in the ‘tinc.conf’ file (if it is available).
After each branch has finished configuration and they have distributed the host configuration files amongst them, they can start their tinc daemons. They don’t necessarily have to wait for the other branches to have started their daemons, tinc will try connecting until they are available.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Build Daemon on May 1, 2013 using texi2html 1.82.