1 \input texinfo @c -*-texinfo-*-
8 @include tincinclude.texi
11 @dircategory Networking tools
13 * tinc: (tinc). The tinc Manual.
16 This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon.
18 Copyright @copyright{} 1998-2011 Ivo Timmermans,
19 Guus Sliepen <guus@@tinc-vpn.org> and
20 Wessel Dankers <wsl@@tinc-vpn.org>.
22 Permission is granted to make and distribute verbatim copies of this
23 manual provided the copyright notice and this permission notice are
24 preserved on all copies.
26 Permission is granted to copy and distribute modified versions of this
27 manual under the conditions for verbatim copying, provided that the
28 entire resulting derived work is distributed under the terms of a
29 permission notice identical to this one.
35 @subtitle Setting up a Virtual Private Network with tinc
36 @author Ivo Timmermans and Guus Sliepen
39 @vskip 0pt plus 1filll
40 This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon.
42 Copyright @copyright{} 1998-2011 Ivo Timmermans,
43 Guus Sliepen <guus@@tinc-vpn.org> and
44 Wessel Dankers <wsl@@tinc-vpn.org>.
46 Permission is granted to make and distribute verbatim copies of this
47 manual provided the copyright notice and this permission notice are
48 preserved on all copies.
50 Permission is granted to copy and distribute modified versions of this
51 manual under the conditions for verbatim copying, provided that the
52 entire resulting derived work is distributed under the terms of a
53 permission notice identical to this one.
58 @c ==================================================================
69 * Technical information::
70 * Platform specific information::
72 * Concept Index:: All used terms explained
76 @c ==================================================================
81 Tinc is a Virtual Private Network (VPN) daemon that uses tunneling and
82 encryption to create a secure private network between hosts on the
85 Because the tunnel appears to the IP level network code as a normal
86 network device, there is no need to adapt any existing software.
87 The encrypted tunnels allows VPN sites to share information with each other
88 over the Internet without exposing any information to others.
90 This document is the manual for tinc. Included are chapters on how to
91 configure your computer to use tinc, as well as the configuration
92 process of tinc itself.
95 * Virtual Private Networks::
97 * Supported platforms::
100 @c ==================================================================
101 @node Virtual Private Networks
102 @section Virtual Private Networks
105 A Virtual Private Network or VPN is a network that can only be accessed
106 by a few elected computers that participate. This goal is achievable in
107 more than just one way.
110 Private networks can consist of a single stand-alone Ethernet LAN. Or
111 even two computers hooked up using a null-modem cable. In these cases,
113 obvious that the network is @emph{private}, no one can access it from the
114 outside. But if your computers are linked to the Internet, the network
115 is not private anymore, unless one uses firewalls to block all private
116 traffic. But then, there is no way to send private data to trusted
117 computers on the other end of the Internet.
120 This problem can be solved by using @emph{virtual} networks. Virtual
121 networks can live on top of other networks, but they use encapsulation to
122 keep using their private address space so they do not interfere with
123 the Internet. Mostly, virtual networks appear like a single LAN, even though
124 they can span the entire world. But virtual networks can't be secured
125 by using firewalls, because the traffic that flows through it has to go
126 through the Internet, where other people can look at it.
128 As is the case with either type of VPN, anybody could eavesdrop. Or
129 worse, alter data. Hence it's probably advisable to encrypt the data
130 that flows over the network.
132 When one introduces encryption, we can form a true VPN. Other people may
133 see encrypted traffic, but if they don't know how to decipher it (they
134 need to know the key for that), they cannot read the information that flows
135 through the VPN. This is what tinc was made for.
138 @c ==================================================================
143 I really don't quite remember what got us started, but it must have been
144 Guus' idea. He wrote a simple implementation (about 50 lines of C) that
145 used the ethertap device that Linux knows of since somewhere
146 about kernel 2.1.60. It didn't work immediately and he improved it a
147 bit. At this stage, the project was still simply called "vpnd".
149 Since then, a lot has changed---to say the least.
152 Tinc now supports encryption, it consists of a single daemon (tincd) for
153 both the receiving and sending end, it has become largely
154 runtime-configurable---in short, it has become a full-fledged
155 professional package.
157 @cindex traditional VPNs
159 Tinc also allows more than two sites to connect to eachother and form a single VPN.
160 Traditionally VPNs are created by making tunnels, which only have two endpoints.
161 Larger VPNs with more sites are created by adding more tunnels.
162 Tinc takes another approach: only endpoints are specified,
163 the software itself will take care of creating the tunnels.
164 This allows for easier configuration and improved scalability.
166 A lot can---and will be---changed. We have a number of things that we would like to
167 see in the future releases of tinc. Not everything will be available in
168 the near future. Our first objective is to make tinc work perfectly as
169 it stands, and then add more advanced features.
171 Meanwhile, we're always open-minded towards new ideas. And we're
175 @c ==================================================================
176 @node Supported platforms
177 @section Supported platforms
180 Tinc has been verified to work under Linux, FreeBSD, OpenBSD, NetBSD, MacOS/X (Darwin), Solaris, and Windows (both natively and in a Cygwin environment),
181 with various hardware architectures. These are some of the platforms
182 that are supported by the universal tun/tap device driver or other virtual network device drivers.
183 Without such a driver, tinc will most
184 likely compile and run, but it will not be able to send or receive data
188 For an up to date list of supported platforms, please check the list on
190 @uref{http://www.tinc-vpn.org/platforms}.
198 @c Preparing your system
205 @c ==================================================================
207 @chapter Preparations
209 This chapter contains information on how to prepare your system to
213 * Configuring the kernel::
218 @c ==================================================================
219 @node Configuring the kernel
220 @section Configuring the kernel
223 * Configuration of Linux kernels::
224 * Configuration of FreeBSD kernels::
225 * Configuration of OpenBSD kernels::
226 * Configuration of NetBSD kernels::
227 * Configuration of Solaris kernels::
228 * Configuration of Darwin (MacOS/X) kernels::
229 * Configuration of Windows::
233 @c ==================================================================
234 @node Configuration of Linux kernels
235 @subsection Configuration of Linux kernels
237 @cindex Universal tun/tap
238 For tinc to work, you need a kernel that supports the Universal tun/tap device.
239 Most distributions come with kernels that already support this.
240 Here are the options you have to turn on when configuring a new kernel:
243 Code maturity level options
244 [*] Prompt for development and/or incomplete code/drivers
245 Network device support
246 <M> Universal tun/tap device driver support
249 It's not necessary to compile this driver as a module, even if you are going to
250 run more than one instance of tinc.
252 If you decide to build the tun/tap driver as a kernel module, add these lines
253 to @file{/etc/modules.conf}:
256 alias char-major-10-200 tun
260 @c ==================================================================
261 @node Configuration of FreeBSD kernels
262 @subsection Configuration of FreeBSD kernels
264 For FreeBSD version 4.1 and higher, tun and tap drivers are included in the default kernel configuration.
265 Using tap devices is recommended.
268 @c ==================================================================
269 @node Configuration of OpenBSD kernels
270 @subsection Configuration of OpenBSD kernels
272 For OpenBSD version 2.9 and higher,
273 the tun driver is included in the default kernel configuration.
274 There is also a kernel patch from @uref{http://diehard.n-r-g.com/stuff/openbsd/}
275 which adds a tap device to OpenBSD which should work with tinc,
276 but with recent versions of OpenBSD,
277 a tun device can act as a tap device by setting the link0 option with ifconfig.
279 @c ==================================================================
280 @node Configuration of NetBSD kernels
281 @subsection Configuration of NetBSD kernels
283 For NetBSD version 1.5.2 and higher,
284 the tun driver is included in the default kernel configuration.
286 Tunneling IPv6 may not work on NetBSD's tun device.
289 @c ==================================================================
290 @node Configuration of Solaris kernels
291 @subsection Configuration of Solaris kernels
293 For Solaris 8 (SunOS 5.8) and higher,
294 the tun driver may or may not be included in the default kernel configuration.
295 If it isn't, the source can be downloaded from @uref{http://vtun.sourceforge.net/tun/}.
296 For x86 and sparc64 architectures, precompiled versions can be found at @uref{http://www.monkey.org/~dugsong/fragroute/}.
297 If the @file{net/if_tun.h} header file is missing, install it from the source package.
300 @c ==================================================================
301 @node Configuration of Darwin (MacOS/X) kernels
302 @subsection Configuration of Darwin (MacOS/X) kernels
304 Tinc on Darwin relies on a tunnel driver for its data acquisition from the kernel.
305 Tinc supports either the driver from @uref{http://tuntaposx.sourceforge.net/},
306 which supports both tun and tap style devices,
307 and also the driver from from @uref{http://chrisp.de/en/projects/tunnel.html}.
308 The former driver is recommended.
309 The tunnel driver must be loaded before starting tinc with the following command:
316 @c ==================================================================
317 @node Configuration of Windows
318 @subsection Configuration of Windows
320 You will need to install the latest TAP-Win32 driver from OpenVPN.
321 You can download it from @uref{http://openvpn.sourceforge.net}.
322 Using the Network Connections control panel,
323 configure the TAP-Win32 network interface in the same way as you would do from the tinc-up script,
324 as explained in the rest of the documentation.
327 @c ==================================================================
333 Before you can configure or build tinc, you need to have the OpenSSL,
334 zlib and lzo libraries installed on your system. If you try to configure tinc without
335 having them installed, configure will give you an error message, and stop.
345 @c ==================================================================
350 For all cryptography-related functions, tinc uses the functions provided
351 by the OpenSSL library.
353 If this library is not installed, you wil get an error when configuring
354 tinc for build. Support for running tinc without having OpenSSL
355 installed @emph{may} be added in the future.
357 You can use your operating system's package manager to install this if
358 available. Make sure you install the development AND runtime versions
361 If you have to install OpenSSL manually, you can get the source code
362 from @url{http://www.openssl.org/}. Instructions on how to configure,
363 build and install this package are included within the package. Please
364 make sure you build development and runtime libraries (which is the
367 If you installed the OpenSSL libraries from source, it may be necessary
368 to let configure know where they are, by passing configure one of the
369 --with-openssl-* parameters.
372 --with-openssl=DIR OpenSSL library and headers prefix
373 --with-openssl-include=DIR OpenSSL headers directory
374 (Default is OPENSSL_DIR/include)
375 --with-openssl-lib=DIR OpenSSL library directory
376 (Default is OPENSSL_DIR/lib)
380 @subsubheading License
383 The complete source code of tinc is covered by the GNU GPL version 2.
384 Since the license under which OpenSSL is distributed is not directly
385 compatible with the terms of the GNU GPL
386 @uref{http://www.openssl.org/support/faq.html#LEGAL2}, we
387 include an exemption to the GPL (see also the file COPYING.README) to allow
388 everyone to create a statically or dynamically linked executable:
391 This program is released under the GPL with the additional exemption
392 that compiling, linking, and/or using OpenSSL is allowed. You may
393 provide binary packages linked to the OpenSSL libraries, provided that
394 all other requirements of the GPL are met.
397 Since the LZO library used by tinc is also covered by the GPL,
398 we also present the following exemption:
401 Hereby I grant a special exception to the tinc VPN project
402 (http://www.tinc-vpn.org/) to link the LZO library with the OpenSSL library
403 (http://www.openssl.org).
405 Markus F.X.J. Oberhumer
409 @c ==================================================================
414 For the optional compression of UDP packets, tinc uses the functions provided
417 If this library is not installed, you wil get an error when configuring
418 tinc for build. Support for running tinc without having zlib
419 installed @emph{may} be added in the future.
421 You can use your operating system's package manager to install this if
422 available. Make sure you install the development AND runtime versions
425 If you have to install zlib manually, you can get the source code
426 from @url{http://www.gzip.org/zlib/}. Instructions on how to configure,
427 build and install this package are included within the package. Please
428 make sure you build development and runtime libraries (which is the
432 @c ==================================================================
437 Another form of compression is offered using the lzo library.
439 If this library is not installed, you wil get an error when configuring
440 tinc for build. Support for running tinc without having lzo
441 installed @emph{may} be added in the future.
443 You can use your operating system's package manager to install this if
444 available. Make sure you install the development AND runtime versions
447 If you have to install lzo manually, you can get the source code
448 from @url{http://www.oberhumer.com/opensource/lzo/}. Instructions on how to configure,
449 build and install this package are included within the package. Please
450 make sure you build development and runtime libraries (which is the
454 @c ==================================================================
459 For the main event loop, tinc uses the libevent library.
461 If this library is not installed, you wil get an error when configuring
464 You can use your operating system's package manager to install this if
465 available. Make sure you install the development AND runtime versions
468 If you have to install libevent manually, you can get the source code
469 from @url{http://monkey.org/~provos/libevent/}. Instructions on how to configure,
470 build and install this package are included within the package. Please
471 make sure you build development and runtime libraries (which is the
484 @c ==================================================================
486 @chapter Installation
488 If you use Debian, you may want to install one of the
489 precompiled packages for your system. These packages are equipped with
490 system startup scripts and sample configurations.
492 If you cannot use one of the precompiled packages, or you want to compile tinc
493 for yourself, you can use the source. The source is distributed under
494 the GNU General Public License (GPL). Download the source from the
495 @uref{http://www.tinc-vpn.org/download, download page}, which has
496 the checksums of these files listed; you may wish to check these with
497 md5sum before continuing.
499 Tinc comes in a convenient autoconf/automake package, which you can just
500 treat the same as any other package. Which is just untar it, type
501 `./configure' and then `make'.
502 More detailed instructions are in the file @file{INSTALL}, which is
503 included in the source distribution.
506 * Building and installing tinc::
511 @c ==================================================================
512 @node Building and installing tinc
513 @section Building and installing tinc
515 Detailed instructions on configuring the source, building tinc and installing tinc
516 can be found in the file called @file{INSTALL}.
518 @cindex binary package
519 If you happen to have a binary package for tinc for your distribution,
520 you can use the package management tools of that distribution to install tinc.
521 The documentation that comes along with your distribution will tell you how to do that.
524 * Darwin (MacOS/X) build environment::
525 * Cygwin (Windows) build environment::
526 * MinGW (Windows) build environment::
530 @c ==================================================================
531 @node Darwin (MacOS/X) build environment
532 @subsection Darwin (MacOS/X) build environment
534 In order to build tinc on Darwin, you need to install the MacOS/X Developer Tools
535 from @uref{http://developer.apple.com/tools/macosxtools.html} and
536 a recent version of Fink from @uref{http://fink.sourceforge.net/}.
538 After installation use fink to download and install the following packages:
539 autoconf25, automake, dlcompat, m4, openssl, zlib and lzo.
541 @c ==================================================================
542 @node Cygwin (Windows) build environment
543 @subsection Cygwin (Windows) build environment
545 If Cygwin hasn't already been installed, install it directly from
546 @uref{http://www.cygwin.com/}.
548 When tinc is compiled in a Cygwin environment, it can only be run in this environment,
549 but all programs, including those started outside the Cygwin environment, will be able to use the VPN.
550 It will also support all features.
552 @c ==================================================================
553 @node MinGW (Windows) build environment
554 @subsection MinGW (Windows) build environment
556 You will need to install the MinGW environment from @uref{http://www.mingw.org}.
558 When tinc is compiled using MinGW it runs natively under Windows,
559 it is not necessary to keep MinGW installed.
561 When detaching, tinc will install itself as a service,
562 which will be restarted automatically after reboots.
565 @c ==================================================================
567 @section System files
569 Before you can run tinc, you must make sure you have all the needed
570 files on your system.
578 @c ==================================================================
580 @subsection Device files
583 Most operating systems nowadays come with the necessary device files by default,
584 or they have a mechanism to create them on demand.
586 If you use Linux and do not have udev installed,
587 you may need to create the following device file if it does not exist:
590 mknod -m 600 /dev/net/tun c 10 200
594 @c ==================================================================
596 @subsection Other files
598 @subsubheading @file{/etc/networks}
600 You may add a line to @file{/etc/networks} so that your VPN will get a
601 symbolic name. For example:
607 @subsubheading @file{/etc/services}
610 You may add this line to @file{/etc/services}. The effect is that you
611 may supply a @samp{tinc} as a valid port number to some programs. The
612 number 655 is registered with the IANA.
617 # Ivo Timmermans <ivo@@tinc-vpn.org>
632 @c ==================================================================
634 @chapter Configuration
637 * Configuration introduction::
638 * Multiple networks::
639 * How connections work::
640 * Configuration files::
641 * Generating keypairs::
642 * Network interfaces::
643 * Example configuration::
646 @c ==================================================================
647 @node Configuration introduction
648 @section Configuration introduction
650 Before actually starting to configure tinc and editing files,
651 make sure you have read this entire section so you know what to expect.
652 Then, make it clear to yourself how you want to organize your VPN:
653 What are the nodes (computers running tinc)?
654 What IP addresses/subnets do they have?
655 What is the network mask of the entire VPN?
656 Do you need special firewall rules?
657 Do you have to set up masquerading or forwarding rules?
658 Do you want to run tinc in router mode or switch mode?
659 These questions can only be answered by yourself,
660 you will not find the answers in this documentation.
661 Make sure you have an adequate understanding of networks in general.
662 @cindex Network Administrators Guide
663 A good resource on networking is the
664 @uref{http://www.linuxdoc.org/LDP/nag2/, Linux Network Administrators Guide}.
666 If you have everything clearly pictured in your mind,
667 proceed in the following order:
668 First, generate the configuration files (@file{tinc.conf}, your host configuration file, @file{tinc-up} and perhaps @file{tinc-down}).
669 Then generate the keypairs.
670 Finally, distribute the host configuration files.
671 These steps are described in the subsections below.
674 @c ==================================================================
675 @node Multiple networks
676 @section Multiple networks
678 @cindex multiple networks
680 In order to allow you to run more than one tinc daemon on one computer,
681 for instance if your computer is part of more than one VPN,
682 you can assign a @var{netname} to your VPN.
683 It is not required if you only run one tinc daemon,
684 it doesn't even have to be the same on all the sites of your VPN,
685 but it is recommended that you choose one anyway.
687 We will asume you use a netname throughout this document.
688 This means that you call tincd with the -n argument,
689 which will assign a netname to this daemon.
691 The effect of this is that the daemon will set its configuration
692 root to @file{@value{sysconfdir}/tinc/@var{netname}/}, where @var{netname} is your argument to the -n
693 option. You'll notice that it appears in syslog as @file{tinc.@var{netname}}.
695 However, it is not strictly necessary that you call tinc with the -n
696 option. In this case, the network name would just be empty, and it will
697 be used as such. tinc now looks for files in @file{@value{sysconfdir}/tinc/}, instead of
698 @file{@value{sysconfdir}/tinc/@var{netname}/}; the configuration file should be @file{@value{sysconfdir}/tinc/tinc.conf},
699 and the host configuration files are now expected to be in @file{@value{sysconfdir}/tinc/hosts/}.
701 But it is highly recommended that you use this feature of tinc, because
702 it will be so much clearer whom your daemon talks to. Hence, we will
703 assume that you use it.
706 @c ==================================================================
707 @node How connections work
708 @section How connections work
710 When tinc starts up, it parses the command-line options and then
711 reads in the configuration file tinc.conf.
712 If it sees one or more `ConnectTo' values pointing to other tinc daemons in that file,
713 it will try to connect to those other daemons.
714 Whether this succeeds or not and whether `ConnectTo' is specified or not,
715 tinc will listen for incoming connection from other deamons.
716 If you did specify a `ConnectTo' value and the other side is not responding,
717 tinc will keep retrying.
718 This means that once started, tinc will stay running until you tell it to stop,
719 and failures to connect to other tinc daemons will not stop your tinc daemon
720 for trying again later.
721 This means you don't have to intervene if there are temporary network problems.
725 There is no real distinction between a server and a client in tinc.
726 If you wish, you can view a tinc daemon without a `ConnectTo' value as a server,
727 and one which does specify such a value as a client.
728 It does not matter if two tinc daemons have a `ConnectTo' value pointing to each other however.
731 @c ==================================================================
732 @node Configuration files
733 @section Configuration files
735 The actual configuration of the daemon is done in the file
736 @file{@value{sysconfdir}/tinc/@var{netname}/tinc.conf} and at least one other file in the directory
737 @file{@value{sysconfdir}/tinc/@var{netname}/hosts/}.
739 These file consists of comments (lines started with a #) or assignments
746 The variable names are case insensitive, and any spaces, tabs, newlines
747 and carriage returns are ignored. Note: it is not required that you put
748 in the `=' sign, but doing so improves readability. If you leave it
749 out, remember to replace it with at least one space character.
751 The server configuration is complemented with host specific configuration (see
752 the next section). Although all host configuration options for the local node
753 listed in this document can also be put in
754 @file{@value{sysconfdir}/tinc/@var{netname}/tinc.conf}, it is recommended to
755 put host specific configuration options in the host configuration file, as this
756 makes it easy to exchange with other nodes.
758 In this section all valid variables are listed in alphabetical order.
759 The default value is given between parentheses,
760 other comments are between square brackets.
763 * Main configuration variables::
764 * Host configuration variables::
770 @c ==================================================================
771 @node Main configuration variables
772 @subsection Main configuration variables
775 @cindex AddressFamily
776 @item AddressFamily = <ipv4|ipv6|any> (any)
777 This option affects the address family of listening and outgoing sockets.
778 If any is selected, then depending on the operating system
779 both IPv4 and IPv6 or just IPv6 listening sockets will be created.
781 @cindex BindToAddress
782 @item BindToAddress = <@var{address}> [experimental]
783 If your computer has more than one IPv4 or IPv6 address, tinc
784 will by default listen on all of them for incoming connections.
785 It is possible to bind only to a single address with this variable.
787 This option may not work on all platforms.
789 @cindex BindToInterface
790 @item BindToInterface = <@var{interface}> [experimental]
791 If you have more than one network interface in your computer, tinc will
792 by default listen on all of them for incoming connections. It is
793 possible to bind tinc to a single interface like eth0 or ppp0 with this
796 This option may not work on all platforms.
799 @item ConnectTo = <@var{name}>
800 Specifies which other tinc daemon to connect to on startup.
801 Multiple ConnectTo variables may be specified,
802 in which case outgoing connections to each specified tinc daemon are made.
803 The names should be known to this tinc daemon
804 (i.e., there should be a host configuration file for the name on the ConnectTo line).
806 If you don't specify a host with ConnectTo,
807 tinc won't try to connect to other daemons at all,
808 and will instead just listen for incoming connections.
811 @item Device = <@var{device}> (@file{/dev/tap0}, @file{/dev/net/tun} or other depending on platform)
812 The virtual network device to use.
813 Tinc will automatically detect what kind of device it is.
814 Note that you can only use one device per daemon.
815 Under Windows, use @var{Interface} instead of @var{Device}.
816 Note that you can only use one device per daemon.
817 See also @ref{Device files}.
820 @item DeviceType = <tun|tunnohead|tunifhead|tap> (only supported on BSD platforms)
821 The type of the virtual network device.
822 Tinc will normally automatically select the right type, and this option should not be used.
823 However, in case tinc does not seem to correctly interpret packets received from the virtual network device,
824 using this option might help.
829 Depending on the platform, this can either be with or without an address family header (see below).
833 Set type to tun without an address family header.
834 Tinc will expect packets read from the virtual network device to start with an IP header.
835 On some platforms IPv6 packets cannot be read from or written to the device in this mode.
839 Set type to tun with an address family header.
840 Tinc will expect packets read from the virtual network device
841 to start with a four byte header containing the address family,
842 followed by an IP header.
843 This mode should support both IPv4 and IPv6 packets.
847 Tinc will expect packets read from the virtual network device
848 to start with an Ethernet header.
852 @item DirectOnly = <yes|no> (no) [experimental]
853 When this option is enabled, packets that cannot be sent directly to the destination node,
854 but which would have to be forwarded by an intermediate node, are dropped instead.
855 When combined with the IndirectData option,
856 packets for nodes for which we do not have a meta connection with are also dropped.
858 @cindex ECDSAPrivateKeyFile
859 @item ECDSAPrivateKeyFile = <@var{path}> (@file{@value{sysconfdir}/tinc/@var{netname}/ecdsa_key.priv})
860 The file in which the private ECDSA key of this tinc daemon resides.
861 This is only used if ExperimentalProtocol is enabled.
863 @cindex ExperimentalProtocol
864 @item ExperimentalProtocol = <yes|no> (no) [experimental]
865 When this option is enabled, experimental protocol enhancements will be used.
866 Ephemeral ECDH will be used for key exchanges,
867 and ECDSA will be used instead of RSA for authentication.
868 When enabled, an ECDSA key must have been generated before with
869 @samp{tincctl generate-ecdsa-keys}.
870 The experimental protocol may change at any time,
871 and there is no guarantee that tinc will run stable when it is used.
874 @item Forwarding = <off|internal|kernel> (internal) [experimental]
875 This option selects the way indirect packets are forwarded.
879 Incoming packets that are not meant for the local node,
880 but which should be forwarded to another node, are dropped.
883 Incoming packets that are meant for another node are forwarded by tinc internally.
885 This is the default mode, and unless you really know you need another forwarding mode, don't change it.
888 Incoming packets are always sent to the TUN/TAP device, even if the packets are not for the local node.
889 This is less efficient, but allows the kernel to apply its routing and firewall rules on them,
890 and can also help debugging.
893 @cindex GraphDumpFile
894 @item GraphDumpFile = <@var{filename}> [experimental]
895 If this option is present,
896 tinc will dump the current network graph to the file @var{filename}
897 every minute, unless there were no changes to the graph.
898 The file is in a format that can be read by graphviz tools.
899 If @var{filename} starts with a pipe symbol |,
900 then the rest of the filename is interpreted as a shell command
901 that is executed, the graph is then sent to stdin.
904 @item Hostnames = <yes|no> (no)
905 This option selects whether IP addresses (both real and on the VPN)
906 should be resolved. Since DNS lookups are blocking, it might affect
907 tinc's efficiency, even stopping the daemon for a few seconds everytime
908 it does a lookup if your DNS server is not responding.
910 This does not affect resolving hostnames to IP addresses from the
914 @item Interface = <@var{interface}>
915 Defines the name of the interface corresponding to the virtual network device.
916 Depending on the operating system and the type of device this may or may not actually set the name of the interface.
917 Under Windows, this variable is used to select which network interface will be used.
918 If you specified a Device, this variable is almost always already correctly set.
921 @item Mode = <router|switch|hub> (router)
922 This option selects the way packets are routed to other daemons.
928 variables in the host configuration files will be used to form a routing table.
929 Only unicast packets of routable protocols (IPv4 and IPv6) are supported in this mode.
931 This is the default mode, and unless you really know you need another mode, don't change it.
935 In this mode the MAC addresses of the packets on the VPN will be used to
936 dynamically create a routing table just like an Ethernet switch does.
937 Unicast, multicast and broadcast packets of every protocol that runs over Ethernet are supported in this mode
938 at the cost of frequent broadcast ARP requests and routing table updates.
940 This mode is primarily useful if you want to bridge Ethernet segments.
944 This mode is almost the same as the switch mode, but instead
945 every packet will be broadcast to the other daemons
946 while no routing table is managed.
950 @item KeyExpire = <@var{seconds}> (3600)
951 This option controls the time the encryption keys used to encrypt the data
952 are valid. It is common practice to change keys at regular intervals to
953 make it even harder for crackers, even though it is thought to be nearly
954 impossible to crack a single key.
957 @item MACExpire = <@var{seconds}> (600)
958 This option controls the amount of time MAC addresses are kept before they are removed.
959 This only has effect when Mode is set to "switch".
962 @item Name = <@var{name}> [required]
963 This is a symbolic name for this connection.
964 The name should consist only of alfanumeric and underscore characters (a-z, A-Z, 0-9 and _).
967 @item PingInterval = <@var{seconds}> (60)
968 The number of seconds of inactivity that tinc will wait before sending a
969 probe to the other end.
972 @item PingTimeout = <@var{seconds}> (5)
973 The number of seconds to wait for a response to pings or to allow meta
974 connections to block. If the other end doesn't respond within this time,
975 the connection is terminated, and the others will be notified of this.
977 @cindex PriorityInheritance
978 @item PriorityInheritance = <yes|no> (no) [experimental]
979 When this option is enabled the value of the TOS field of tunneled IPv4 packets
980 will be inherited by the UDP packets that are sent out.
983 @item PrivateKey = <@var{key}> [obsolete]
984 This is the RSA private key for tinc. However, for safety reasons it is
985 advised to store private keys of any kind in separate files. This prevents
986 accidental eavesdropping if you are editting the configuration file.
988 @cindex PrivateKeyFile
989 @item PrivateKeyFile = <@var{path}> (@file{@value{sysconfdir}/tinc/@var{netname}/rsa_key.priv})
990 This is the full path name of the RSA private key file that was
991 generated by @samp{tincctl generate-keys}. It must be a full path, not a
994 Note that there must be exactly one of PrivateKey
996 specified in the configuration file.
998 @cindex ProcessPriority
999 @item ProcessPriority = <low|normal|high>
1000 When this option is used the priority of the tincd process will be adjusted.
1001 Increasing the priority may help to reduce latency and packet loss on the VPN.
1003 @cindex ReplayWindow
1004 @item ReplayWindow = <bytes> (16)
1005 This is the size of the replay tracking window for each remote node, in bytes.
1006 The window is a bitfield which tracks 1 packet per bit, so for example
1007 the default setting of 16 will track up to 128 packets in the window. In high
1008 bandwidth scenarios, setting this to a higher value can reduce packet loss from
1009 the interaction of replay tracking with underlying real packet loss and/or
1010 reordering. Setting this to zero will disable replay tracking completely and
1011 pass all traffic, but leaves tinc vulnerable to replay-based attacks on your
1015 @cindex StrictSubnets
1016 @item StrictSubnets <yes|no> (no) [experimental]
1017 When this option is enabled tinc will only use Subnet statements which are
1018 present in the host config files in the local
1019 @file{@value{sysconfdir}/tinc/@var{netname}/hosts/} directory.
1021 @cindex TunnelServer
1022 @item TunnelServer = <yes|no> (no) [experimental]
1023 When this option is enabled tinc will no longer forward information between other tinc daemons,
1024 and will only allow connections with nodes for which host config files are present in the local
1025 @file{@value{sysconfdir}/tinc/@var{netname}/hosts/} directory.
1026 Setting this options also implicitly sets StrictSubnets.
1029 @item UDPRcvBuf = <bytes> (OS default)
1030 Sets the socket receive buffer size for the UDP socket, in bytes.
1031 If unset, the default buffer size will be used by the operating system.
1034 @item UDPSndBuf = <bytes> Pq OS default
1035 Sets the socket send buffer size for the UDP socket, in bytes.
1036 If unset, the default buffer size will be used by the operating system.
1041 @c ==================================================================
1042 @node Host configuration variables
1043 @subsection Host configuration variables
1047 @item Address = <@var{IP address}|@var{hostname}> [<port>] [recommended]
1048 This variable is only required if you want to connect to this host. It
1049 must resolve to the external IP address where the host can be reached,
1050 not the one that is internal to the VPN.
1051 If no port is specified, the default Port is used.
1054 @item Cipher = <@var{cipher}> (blowfish)
1055 The symmetric cipher algorithm used to encrypt UDP packets.
1056 Any cipher supported by OpenSSL is recognized.
1057 Furthermore, specifying "none" will turn off packet encryption.
1058 It is best to use only those ciphers which support CBC mode.
1061 @item ClampMSS = <yes|no> (yes)
1062 This option specifies whether tinc should clamp the maximum segment size (MSS)
1063 of TCP packets to the path MTU. This helps in situations where ICMP
1064 Fragmentation Needed or Packet too Big messages are dropped by firewalls.
1067 @item Compression = <@var{level}> (0)
1068 This option sets the level of compression used for UDP packets.
1069 Possible values are 0 (off), 1 (fast zlib) and any integer up to 9 (best zlib),
1070 10 (fast lzo) and 11 (best lzo).
1073 @item Digest = <@var{digest}> (sha1)
1074 The digest algorithm used to authenticate UDP packets.
1075 Any digest supported by OpenSSL is recognized.
1076 Furthermore, specifying "none" will turn off packet authentication.
1078 @cindex IndirectData
1079 @item IndirectData = <yes|no> (no)
1080 This option specifies whether other tinc daemons besides the one you
1081 specified with ConnectTo can make a direct connection to you. This is
1082 especially useful if you are behind a firewall and it is impossible to
1083 make a connection from the outside to your tinc daemon. Otherwise, it
1084 is best to leave this option out or set it to no.
1087 @item MACLength = <@var{bytes}> (4)
1088 The length of the message authentication code used to authenticate UDP packets.
1089 Can be anything from 0
1090 up to the length of the digest produced by the digest algorithm.
1093 @item PMTU = <@var{mtu}> (1514)
1094 This option controls the initial path MTU to this node.
1096 @cindex PMTUDiscovery
1097 @item PMTUDiscovery = <yes|no> (yes)
1098 When this option is enabled, tinc will try to discover the path MTU to this node.
1099 After the path MTU has been discovered, it will be enforced on the VPN.
1102 @item Port = <@var{port}> (655)
1103 This is the port this tinc daemon listens on.
1104 You can use decimal portnumbers or symbolic names (as listed in @file{/etc/services}).
1107 @item PublicKey = <@var{key}> [obsolete]
1108 This is the RSA public key for this host.
1110 @cindex PublicKeyFile
1111 @item PublicKeyFile = <@var{path}> [obsolete]
1112 This is the full path name of the RSA public key file that was generated
1113 by @samp{tincctl generate-keys}. It must be a full path, not a relative
1117 From version 1.0pre4 on tinc will store the public key directly into the
1118 host configuration file in PEM format, the above two options then are not
1119 necessary. Either the PEM format is used, or exactly
1120 @strong{one of the above two options} must be specified
1121 in each host configuration file, if you want to be able to establish a
1122 connection with that host.
1125 @item Subnet = <@var{address}[/@var{prefixlength}[#@var{weight}]]>
1126 The subnet which this tinc daemon will serve.
1127 Tinc tries to look up which other daemon it should send a packet to by searching the appropiate subnet.
1128 If the packet matches a subnet,
1129 it will be sent to the daemon who has this subnet in his host configuration file.
1130 Multiple subnet lines can be specified for each daemon.
1132 Subnets can either be single MAC, IPv4 or IPv6 addresses,
1133 in which case a subnet consisting of only that single address is assumed,
1134 or they can be a IPv4 or IPv6 network address with a prefixlength.
1135 Shorthand notations are not supported.
1136 For example, IPv4 subnets must be in a form like 192.168.1.0/24,
1137 where 192.168.1.0 is the network address and 24 is the number of bits set in the netmask.
1138 Note that subnets like 192.168.1.1/24 are invalid!
1139 Read a networking HOWTO/FAQ/guide if you don't understand this.
1140 IPv6 subnets are notated like fec0:0:0:1:0:0:0:0/64.
1141 MAC addresses are notated like 0:1a:2b:3c:4d:5e.
1143 @cindex CIDR notation
1144 Prefixlength is the number of bits set to 1 in the netmask part; for
1145 example: netmask 255.255.255.0 would become /24, 255.255.252.0 becomes
1146 /22. This conforms to standard CIDR notation as described in
1147 @uref{ftp://ftp.isi.edu/in-notes/rfc1519.txt, RFC1519}
1149 A Subnet can be given a weight to indicate its priority over identical Subnets
1150 owned by different nodes. The default weight is 10. Lower values indicate
1151 higher priority. Packets will be sent to the node with the highest priority,
1152 unless that node is not reachable, in which case the node with the next highest
1153 priority will be tried, and so on.
1156 @item TCPonly = <yes|no> (no)
1157 If this variable is set to yes, then the packets are tunnelled over a
1158 TCP connection instead of a UDP connection. This is especially useful
1159 for those who want to run a tinc daemon from behind a masquerading
1160 firewall, or if UDP packet routing is disabled somehow.
1161 Setting this options also implicitly sets IndirectData.
1165 @c ==================================================================
1170 Apart from reading the server and host configuration files,
1171 tinc can also run scripts at certain moments.
1172 Under Windows (not Cygwin), the scripts should have the extension .bat.
1176 @item @value{sysconfdir}/tinc/@var{netname}/tinc-up
1177 This is the most important script.
1178 If it is present it will be executed right after the tinc daemon has been
1179 started and has connected to the virtual network device.
1180 It should be used to set up the corresponding network interface,
1181 but can also be used to start other things.
1182 Under Windows you can use the Network Connections control panel instead of creating this script.
1185 @item @value{sysconfdir}/tinc/@var{netname}/tinc-down
1186 This script is started right before the tinc daemon quits.
1188 @item @value{sysconfdir}/tinc/@var{netname}/hosts/@var{host}-up
1189 This script is started when the tinc daemon with name @var{host} becomes reachable.
1191 @item @value{sysconfdir}/tinc/@var{netname}/hosts/@var{host}-down
1192 This script is started when the tinc daemon with name @var{host} becomes unreachable.
1194 @item @value{sysconfdir}/tinc/@var{netname}/host-up
1195 This script is started when any host becomes reachable.
1197 @item @value{sysconfdir}/tinc/@var{netname}/host-down
1198 This script is started when any host becomes unreachable.
1200 @item @value{sysconfdir}/tinc/@var{netname}/subnet-up
1201 This script is started when a Subnet becomes reachable.
1202 The Subnet and the node it belongs to are passed in environment variables.
1204 @item @value{sysconfdir}/tinc/@var{netname}/subnet-down
1205 This script is started when a Subnet becomes unreachable.
1208 @cindex environment variables
1209 The scripts are started without command line arguments,
1210 but can make use of certain environment variables.
1211 Under UNIX like operating systems the names of environment variables must be preceded by a $ in scripts.
1212 Under Windows, in @file{.bat} files, they have to be put between % signs.
1217 If a netname was specified, this environment variable contains it.
1221 Contains the name of this tinc daemon.
1225 Contains the name of the virtual network device that tinc uses.
1229 Contains the name of the virtual network interface that tinc uses.
1230 This should be used for commands like ifconfig.
1234 When a host becomes (un)reachable, this is set to its name.
1235 If a subnet becomes (un)reachable, this is set to the owner of that subnet.
1237 @cindex REMOTEADDRESS
1239 When a host becomes (un)reachable, this is set to its real address.
1243 When a host becomes (un)reachable,
1244 this is set to the port number it uses for communication with other tinc daemons.
1248 When a subnet becomes (un)reachable, this is set to the subnet.
1253 @c ==================================================================
1254 @node How to configure
1255 @subsection How to configure
1257 @subsubheading Step 1. Creating the main configuration file
1259 The main configuration file will be called @file{@value{sysconfdir}/tinc/@var{netname}/tinc.conf}.
1260 Adapt the following example to create a basic configuration file:
1263 Name = @var{yourname}
1264 Device = @file{/dev/tap0}
1267 Then, if you know to which other tinc daemon(s) yours is going to connect,
1268 add `ConnectTo' values.
1270 @subsubheading Step 2. Creating your host configuration file
1272 If you added a line containing `Name = yourname' in the main configuarion file,
1273 you will need to create a host configuration file @file{@value{sysconfdir}/tinc/@var{netname}/hosts/yourname}.
1274 Adapt the following example to create a host configuration file:
1277 Address = your.real.hostname.org
1278 Subnet = 192.168.1.0/24
1281 You can also use an IP address instead of a hostname.
1282 The `Subnet' specifies the address range that is local for @emph{your part of the VPN only}.
1283 If you have multiple address ranges you can specify more than one `Subnet'.
1284 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).
1287 @c ==================================================================
1288 @node Generating keypairs
1289 @section Generating keypairs
1291 @cindex key generation
1292 Now that you have already created the main configuration file and your host configuration file,
1293 you can easily create a public/private keypair by entering the following command:
1296 tincctl -n @var{netname} generate-keys
1299 Tinc will generate a public and a private key and ask you where to put them.
1300 Just press enter to accept the defaults.
1303 @c ==================================================================
1304 @node Network interfaces
1305 @section Network interfaces
1307 Before tinc can start transmitting data over the tunnel, it must
1308 set up the virtual network interface.
1310 First, decide which IP addresses you want to have associated with these
1311 devices, and what network mask they must have.
1313 Tinc will open a virtual network device (@file{/dev/tun}, @file{/dev/tap0} or similar),
1314 which will also create a network interface called something like @samp{tun0}, @samp{tap0}.
1315 If you are using the Linux tun/tap driver, the network interface will by default have the same name as the @var{netname}.
1316 Under Windows you can change the name of the network interface from the Network Connections control panel.
1319 You can configure the network interface by putting ordinary ifconfig, route, and other commands
1320 to a script named @file{@value{sysconfdir}/tinc/@var{netname}/tinc-up}.
1321 When tinc starts, this script will be executed. When tinc exits, it will execute the script named
1322 @file{@value{sysconfdir}/tinc/@var{netname}/tinc-down}, but normally you don't need to create that script.
1324 An example @file{tinc-up} script:
1328 ifconfig $INTERFACE 192.168.1.1 netmask 255.255.0.0
1331 This script gives the interface an IP address and a netmask.
1332 The kernel will also automatically add a route to this interface, so normally you don't need
1333 to add route commands to the @file{tinc-up} script.
1334 The kernel will also bring the interface up after this command.
1336 The netmask is the mask of the @emph{entire} VPN network, not just your
1339 The exact syntax of the ifconfig and route commands differs from platform to platform.
1340 You can look up the commands for setting addresses and adding routes in @ref{Platform specific information},
1341 but it is best to consult the manpages of those utilities on your platform.
1344 @c ==================================================================
1345 @node Example configuration
1346 @section Example configuration
1350 Imagine the following situation. Branch A of our example `company' wants to connect
1351 three branch offices in B, C and D using the Internet. All four offices
1352 have a 24/7 connection to the Internet.
1354 A is going to serve as the center of the network. B and C will connect
1355 to A, and D will connect to C. Each office will be assigned their own IP
1359 A: net 10.1.0.0 mask 255.255.0.0 gateway 10.1.54.1 internet IP 1.2.3.4
1360 B: net 10.2.0.0 mask 255.255.0.0 gateway 10.2.1.12 internet IP 2.3.4.5
1361 C: net 10.3.0.0 mask 255.255.0.0 gateway 10.3.69.254 internet IP 3.4.5.6
1362 D: net 10.4.0.0 mask 255.255.0.0 gateway 10.4.3.32 internet IP 4.5.6.7
1365 Here, ``gateway'' is the VPN IP address of the machine that is running the
1366 tincd, and ``internet IP'' is the IP address of the firewall, which does not
1367 need to run tincd, but it must do a port forwarding of TCP and UDP on port
1368 655 (unless otherwise configured).
1370 In this example, it is assumed that eth0 is the interface that points to
1371 the inner (physical) LAN of the office, although this could also be the
1372 same as the interface that leads to the Internet. The configuration of
1373 the real interface is also shown as a comment, to give you an idea of
1374 how these example host is set up. All branches use the netname `company'
1375 for this particular VPN.
1377 @subsubheading For Branch A
1379 @emph{BranchA} would be configured like this:
1381 In @file{@value{sysconfdir}/tinc/company/tinc-up}:
1384 # Real interface of internal network:
1385 # ifconfig eth0 10.1.54.1 netmask 255.255.0.0
1387 ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0
1390 and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
1397 On all hosts, @file{@value{sysconfdir}/tinc/company/hosts/BranchA} contains:
1400 Subnet = 10.1.0.0/16
1403 -----BEGIN RSA PUBLIC KEY-----
1405 -----END RSA PUBLIC KEY-----
1408 Note that the IP addresses of eth0 and tap0 are the same.
1409 This is quite possible, if you make sure that the netmasks of the interfaces are different.
1410 It is in fact recommended to give both real internal network interfaces and tap interfaces the same IP address,
1411 since that will make things a lot easier to remember and set up.
1414 @subsubheading For Branch B
1416 In @file{@value{sysconfdir}/tinc/company/tinc-up}:
1419 # Real interface of internal network:
1420 # ifconfig eth0 10.2.43.8 netmask 255.255.0.0
1422 ifconfig $INTERFACE 10.2.1.12 netmask 255.0.0.0
1425 and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
1432 Note here that the internal address (on eth0) doesn't have to be the
1433 same as on the tap0 device. Also, ConnectTo is given so that this node will
1434 always try to connect to BranchA.
1436 On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchB}:
1439 Subnet = 10.2.0.0/16
1442 -----BEGIN RSA PUBLIC KEY-----
1444 -----END RSA PUBLIC KEY-----
1448 @subsubheading For Branch C
1450 In @file{@value{sysconfdir}/tinc/company/tinc-up}:
1453 # Real interface of internal network:
1454 # ifconfig eth0 10.3.69.254 netmask 255.255.0.0
1456 ifconfig $INTERFACE 10.3.69.254 netmask 255.0.0.0
1459 and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
1467 C already has another daemon that runs on port 655, so they have to
1468 reserve another port for tinc. It knows the portnumber it has to listen on
1469 from it's own host configuration file.
1471 On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchC}:
1475 Subnet = 10.3.0.0/16
1478 -----BEGIN RSA PUBLIC KEY-----
1480 -----END RSA PUBLIC KEY-----
1484 @subsubheading For Branch D
1486 In @file{@value{sysconfdir}/tinc/company/tinc-up}:
1489 # Real interface of internal network:
1490 # ifconfig eth0 10.4.3.32 netmask 255.255.0.0
1492 ifconfig $INTERFACE 10.4.3.32 netmask 255.0.0.0
1495 and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
1500 Device = /dev/net/tun
1503 D will be connecting to C, which has a tincd running for this network on
1504 port 2000. It knows the port number from the host configuration file.
1505 Also note that since D uses the tun/tap driver, the network interface
1506 will not be called `tun' or `tap0' or something like that, but will
1507 have the same name as netname.
1509 On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchD}:
1512 Subnet = 10.4.0.0/16
1515 -----BEGIN RSA PUBLIC KEY-----
1517 -----END RSA PUBLIC KEY-----
1520 @subsubheading Key files
1522 A, B, C and D all have generated a public/private keypair with the following command:
1525 tincctl -n company generate-keys
1528 The private key is stored in @file{@value{sysconfdir}/tinc/company/rsa_key.priv},
1529 the public key is put into the host configuration file in the @file{@value{sysconfdir}/tinc/company/hosts/} directory.
1530 During key generation, tinc automatically guesses the right filenames based on the -n option and
1531 the Name directive in the @file{tinc.conf} file (if it is available).
1533 @subsubheading Starting
1535 After each branch has finished configuration and they have distributed
1536 the host configuration files amongst them, they can start their tinc daemons.
1537 They don't necessarily have to wait for the other branches to have started
1538 their daemons, tinc will try connecting until they are available.
1541 @c ==================================================================
1543 @chapter Running tinc
1545 If everything else is done, you can start tinc by typing the following command:
1548 tincd -n @var{netname}
1552 Tinc will detach from the terminal and continue to run in the background like a good daemon.
1553 If there are any problems however you can try to increase the debug level
1554 and look in the syslog to find out what the problems are.
1560 * Solving problems::
1562 * Sending bug reports::
1566 @c ==================================================================
1567 @node Runtime options
1568 @section Runtime options
1570 Besides the settings in the configuration file, tinc also accepts some
1571 command line options.
1573 @cindex command line
1574 @cindex runtime options
1578 @item -c, --config=@var{path}
1579 Read configuration options from the directory @var{path}. The default is
1580 @file{@value{sysconfdir}/tinc/@var{netname}/}.
1582 @item -D, --no-detach
1583 Don't fork and detach.
1584 This will also disable the automatic restart mechanism for fatal errors.
1587 @item -d, --debug=@var{level}
1588 Set debug level to @var{level}. The higher the debug level, the more gets
1589 logged. Everything goes via syslog.
1591 @item -n, --net=@var{netname}
1592 Use configuration for net @var{netname}.
1593 This will let tinc read all configuration files from
1594 @file{@value{sysconfdir}/tinc/@var{netname}/}.
1595 Specifying . for @var{netname} is the same as not specifying any @var{netname}.
1596 @xref{Multiple networks}.
1598 @item --pidfile=@var{filename}
1599 Store a cookie in @var{filename} which allows tincctl to authenticate.
1600 If unspecified, the default is
1601 @file{@value{localstatedir}/run/tinc.@var{netname}.pid}.
1604 Lock tinc into main memory.
1605 This will prevent sensitive data like shared private keys to be written to the system swap files/partitions.
1607 @item --logfile[=@var{file}]
1608 Write log entries to a file instead of to the system logging facility.
1609 If @var{file} is omitted, the default is @file{@value{localstatedir}/log/tinc.@var{netname}.log}.
1611 @item --bypass-security
1612 Disables encryption and authentication.
1613 Only useful for debugging.
1616 Change process root directory to the directory where the config file is
1617 located (@file{@value{sysconfdir}/tinc/@var{netname}/} as determined by
1618 -n/--net option or as given by -c/--config option), for added security.
1619 The chroot is performed after all the initialization is done, after
1620 writing pid files and opening network sockets.
1622 Note that this option alone does not do any good without -U/--user, below.
1624 Note also that tinc can't run scripts anymore (such as tinc-down or host-up),
1625 unless it's setup to be runnable inside chroot environment.
1627 @item -U, --user=@var{user}
1628 Switch to the given @var{user} after initialization, at the same time as
1629 chroot is performed (see --chroot above). With this option tinc drops
1630 privileges, for added security.
1633 Display a short reminder of these runtime options and terminate.
1636 Output version information and exit.
1640 @c ==================================================================
1645 You can also send the following signals to a running tincd process:
1651 Forces tinc to try to connect to all uplinks immediately.
1652 Usually tinc attempts to do this itself,
1653 but increases the time it waits between the attempts each time it failed,
1654 and if tinc didn't succeed to connect to an uplink the first time after it started,
1655 it defaults to the maximum time of 15 minutes.
1658 Partially rereads configuration files.
1659 Connections to hosts whose host config file are removed are closed.
1660 New outgoing connections specified in @file{tinc.conf} will be made.
1661 If the --logfile option is used, this will also close and reopen the log file,
1662 useful when log rotation is used.
1666 @c ==================================================================
1668 @section Debug levels
1670 @cindex debug levels
1671 The tinc daemon can send a lot of messages to the syslog.
1672 The higher the debug level, the more messages it will log.
1673 Each level inherits all messages of the previous level:
1679 This will log a message indicating tinc has started along with a version number.
1680 It will also log any serious error.
1683 This will log all connections that are made with other tinc daemons.
1686 This will log status and error messages from scripts and other tinc daemons.
1689 This will log all requests that are exchanged with other tinc daemons. These include
1690 authentication, key exchange and connection list updates.
1693 This will log a copy of everything received on the meta socket.
1696 This will log all network traffic over the virtual private network.
1700 @c ==================================================================
1701 @node Solving problems
1702 @section Solving problems
1704 If tinc starts without problems, but if the VPN doesn't work, you will have to find the cause of the problem.
1705 The first thing to do is to start tinc with a high debug level in the foreground,
1706 so you can directly see everything tinc logs:
1709 tincd -n @var{netname} -d5 -D
1712 If tinc does not log any error messages, then you might want to check the following things:
1715 @item @file{tinc-up} script
1716 Does this script contain the right commands?
1717 Normally you must give the interface the address of this host on the VPN, and the netmask must be big enough so that the entire VPN is covered.
1720 Does the Subnet (or Subnets) in the host configuration file of this host match the portion of the VPN that belongs to this host?
1722 @item Firewalls and NATs
1723 Do you have a firewall or a NAT device (a masquerading firewall or perhaps an ADSL router that performs masquerading)?
1724 If so, check that it allows TCP and UDP traffic on port 655.
1725 If it masquerades and the host running tinc is behind it, make sure that it forwards TCP and UDP traffic to port 655 to the host running tinc.
1726 You can add @samp{TCPOnly = yes} to your host config file to force tinc to only use a single TCP connection,
1727 this works through most firewalls and NATs.
1732 @c ==================================================================
1733 @node Error messages
1734 @section Error messages
1736 What follows is a list of the most common error messages you might find in the logs.
1737 Some of them will only be visible if the debug level is high enough.
1740 @item Could not open /dev/tap0: No such device
1743 @item You forgot to `modprobe netlink_dev' or `modprobe ethertap'.
1744 @item You forgot to compile `Netlink device emulation' in the kernel.
1747 @item Can't write to /dev/net/tun: No such device
1750 @item You forgot to `modprobe tun'.
1751 @item You forgot to compile `Universal TUN/TAP driver' in the kernel.
1752 @item The tun device is located somewhere else in @file{/dev/}.
1755 @item Network address and prefix length do not match!
1758 @item The Subnet field must contain a @emph{network} address, trailing bits should be 0.
1759 @item If you only want to use one IP address, set the netmask to /32.
1762 @item Error reading RSA key file `rsa_key.priv': No such file or directory
1765 @item You forgot to create a public/private keypair.
1766 @item Specify the complete pathname to the private key file with the @samp{PrivateKeyFile} option.
1769 @item Warning: insecure file permissions for RSA private key file `rsa_key.priv'!
1772 @item The private key file is readable by users other than root.
1773 Use chmod to correct the file permissions.
1776 @item Creating metasocket failed: Address family not supported
1779 @item By default tinc tries to create both IPv4 and IPv6 sockets.
1780 On some platforms this might not be implemented.
1781 If the logs show @samp{Ready} later on, then at least one metasocket was created,
1782 and you can ignore this message.
1783 You can add @samp{AddressFamily = ipv4} to @file{tinc.conf} to prevent this from happening.
1786 @item Cannot route packet: unknown IPv4 destination 1.2.3.4
1789 @item You try to send traffic to a host on the VPN for which no Subnet is known.
1790 @item If it is a broadcast address (ending in .255), it probably is a samba server or a Windows host sending broadcast packets.
1794 @item Cannot route packet: ARP request for unknown address 1.2.3.4
1797 @item You try to send traffic to a host on the VPN for which no Subnet is known.
1800 @item Packet with destination 1.2.3.4 is looping back to us!
1803 @item Something is not configured right. Packets are being sent out to the
1804 virtual network device, but according to the Subnet directives in your host configuration
1805 file, those packets should go to your own host. Most common mistake is that
1806 you have a Subnet line in your host configuration file with a prefix length which is
1807 just as large as the prefix of the virtual network interface. The latter should in almost all
1808 cases be larger. Rethink your configuration.
1809 Note that you will only see this message if you specified a debug
1810 level of 5 or higher!
1811 @item Chances are that a @samp{Subnet = ...} line in the host configuration file of this tinc daemon is wrong.
1812 Change it to a subnet that is accepted locally by another interface,
1813 or if that is not the case, try changing the prefix length into /32.
1816 @item Node foo (1.2.3.4) is not reachable
1819 @item Node foo does not have a connection anymore, its tinc daemon is not running or its connection to the Internet is broken.
1822 @item Received UDP packet from unknown source 1.2.3.4 (port 12345)
1825 @item If you see this only sporadically, it is harmless and caused by a node sending packets using an old key.
1826 @item If you see this often and another node is not reachable anymore, then a NAT (masquerading firewall) is changing the source address of UDP packets.
1827 You can add @samp{TCPOnly = yes} to host configuration files to force all VPN traffic to go over a TCP connection.
1830 @item Got bad/bogus/unauthorized REQUEST from foo (1.2.3.4 port 12345)
1833 @item Node foo does not have the right public/private keypair.
1834 Generate new keypairs and distribute them again.
1835 @item An attacker tries to gain access to your VPN.
1836 @item A network error caused corruption of metadata sent from foo.
1841 @c ==================================================================
1842 @node Sending bug reports
1843 @section Sending bug reports
1845 If you really can't find the cause of a problem, or if you suspect tinc is not working right,
1846 you can send us a bugreport, see @ref{Contact information}.
1847 Be sure to include the following information in your bugreport:
1850 @item A clear description of what you are trying to achieve and what the problem is.
1851 @item What platform (operating system, version, hardware architecture) and which version of tinc you use.
1852 @item If compiling tinc fails, a copy of @file{config.log} and the error messages you get.
1853 @item Otherwise, a copy of @file{tinc.conf}, @file{tinc-up} and all files in the @file{hosts/} directory.
1854 @item The output of the commands @samp{ifconfig -a} and @samp{route -n} (or @samp{netstat -rn} if that doesn't work).
1855 @item The output of any command that fails to work as it should (like ping or traceroute).
1858 @c ==================================================================
1859 @node Controlling tinc
1860 @chapter Controlling tinc
1862 You can control and inspect a running tincd through the tincctl
1863 command. A quick example:
1866 tincctl -n @var{netname} reload
1870 * tincctl runtime options::
1871 * tincctl commands::
1872 * tincctl examples::
1877 @c ==================================================================
1878 @node tincctl runtime options
1879 @section tincctl runtime options
1883 @item -c, --config=@var{path}
1884 Read configuration options from the directory @var{path}. The default is
1885 @file{@value{sysconfdir}/tinc/@var{netname}/}.
1887 @item -n, --net=@var{netname}
1888 Use configuration for net @var{netname}. @xref{Multiple networks}.
1890 @item --pidfile=@var{filename}
1891 Use the cookie from @var{filename} to authenticate with a running tinc daemon.
1892 If unspecified, the default is
1893 @file{@value{localstatedir}/run/tinc.@var{netname}.pid}.
1896 Display a short reminder of runtime options and commands, then terminate.
1899 Output version information and exit.
1904 @c ==================================================================
1905 @node tincctl commands
1906 @section tincctl commands
1918 Restart @samp{tincd}.
1921 Partially rereads configuration files. Connections to hosts whose host
1922 config files are removed are closed. New outgoing connections specified
1923 in @file{tinc.conf} will be made.
1926 Shows the PID of the currently running @samp{tincd}.
1928 @item generate-keys [@var{bits}]
1929 Generate public/private keypair of @var{bits} length. If @var{bits} is not specified,
1930 1024 is the default. tinc will ask where you want to store the files,
1931 but will default to the configuration directory (you can use the -c or -n
1935 Dump a list of all known nodes in the VPN.
1938 Dump a list of all known connections in the VPN.
1941 Dump a list of all known subnets in the VPN.
1943 @item dump connections
1944 Dump a list of all meta connections with ourself.
1947 Dump a graph of the VPN in dotty format.
1950 Purges all information remembered about unreachable nodes.
1952 @item debug @var{level}
1953 Sets debug level to @var{level}.
1956 Forces tinc to try to connect to all uplinks immediately.
1957 Usually tinc attempts to do this itself,
1958 but increases the time it waits between the attempts each time it failed,
1959 and if tinc didn't succeed to connect to an uplink the first time after it started,
1960 it defaults to the maximum time of 15 minutes.
1962 @item disconnect @var{node}
1963 Closes the meta connection with the given @var{node}.
1966 If tincctl is compiled with libcurses support, this will display live traffic statistics for all the known nodes,
1967 similar to the UNIX top command.
1968 See below for more information.
1971 Dump VPN traffic going through the local tinc node in pcap-savefile format to standard output,
1972 from where it can be redirected to a file or piped through a program that can parse it directly,
1977 @c ==================================================================
1978 @node tincctl examples
1979 @section tincctl examples
1981 Examples of some commands:
1984 tincctl -n vpn dump graph | circo -Txlib
1985 tincctl -n vpn pcap | tcpdump -r -
1989 @c ==================================================================
1991 @section tincctl top
1993 The top command connects to a running tinc daemon and repeatedly queries its per-node traffic counters.
1994 It displays a list of all the known nodes in the left-most column,
1995 and the amount of bytes and packets read from and sent to each node in the other columns.
1996 By default, the information is updated every second.
1997 The behaviour of the top command can be changed using the following keys:
2002 Change the interval between updates.
2003 After pressing the @key{s} key, enter the desired interval in seconds, followed by enter.
2004 Fractional seconds are honored.
2005 Intervals lower than 0.1 seconds are not allowed.
2008 Toggle between displaying current traffic rates (in packets and bytes per second)
2009 and cummulative traffic (total packets and bytes since the tinc daemon started).
2012 Sort the list of nodes by name.
2015 Sort the list of nodes by incoming amount of bytes.
2018 Sort the list of nodes by incoming amount of packets.
2021 Sort the list of nodes by outgoing amount of bytes.
2024 Sort the list of nodes by outgoing amount of packets.
2027 Sort the list of nodes by sum of incoming and outgoing amount of bytes.
2030 Sort the list of nodes by sum of incoming and outgoing amount of packets.
2033 Show amount of traffic in bytes.
2036 Show amount of traffic in kilobytes.
2039 Show amount of traffic in megabytes.
2042 Show amount of traffic in gigabytes.
2050 @c ==================================================================
2051 @node Technical information
2052 @chapter Technical information
2057 * The meta-protocol::
2062 @c ==================================================================
2063 @node The connection
2064 @section The connection
2067 Tinc is a daemon that takes VPN data and transmit that to another host
2068 computer over the existing Internet infrastructure.
2072 * The meta-connection::
2076 @c ==================================================================
2077 @node The UDP tunnel
2078 @subsection The UDP tunnel
2080 @cindex virtual network device
2082 The data itself is read from a character device file, the so-called
2083 @emph{virtual network device}. This device is associated with a network
2084 interface. Any data sent to this interface can be read from the device,
2085 and any data written to the device gets sent from the interface.
2086 There are two possible types of virtual network devices:
2087 `tun' style, which are point-to-point devices which can only handle IPv4 and/or IPv6 packets,
2088 and `tap' style, which are Ethernet devices and handle complete Ethernet frames.
2090 So when tinc reads an Ethernet frame from the device, it determines its
2091 type. When tinc is in it's default routing mode, it can handle IPv4 and IPv6
2092 packets. Depending on the Subnet lines, it will send the packets off to their destination IP address.
2093 In the `switch' and `hub' mode, tinc will use broadcasts and MAC address discovery
2094 to deduce the destination of the packets.
2095 Since the latter modes only depend on the link layer information,
2096 any protocol that runs over Ethernet is supported (for instance IPX and Appletalk).
2097 However, only `tap' style devices provide this information.
2099 After the destination has been determined,
2100 the packet will be compressed (optionally),
2101 a sequence number will be added to the packet,
2102 the packet will then be encrypted
2103 and a message authentication code will be appended.
2105 @cindex encapsulating
2107 When that is done, time has come to actually transport the
2108 packet to the destination computer. We do this by sending the packet
2109 over an UDP connection to the destination host. This is called
2110 @emph{encapsulating}, the VPN packet (though now encrypted) is
2111 encapsulated in another IP datagram.
2113 When the destination receives this packet, the same thing happens, only
2114 in reverse. So it checks the message authentication code, decrypts the contents of the UDP datagram,
2115 checks the sequence number
2116 and writes the decrypted information to its own virtual network device.
2118 If the virtual network device is a `tun' device (a point-to-point tunnel),
2119 there is no problem for the kernel to accept a packet.
2120 However, if it is a `tap' device (this is the only available type on FreeBSD),
2121 the destination MAC address must match that of the virtual network interface.
2122 If tinc is in it's default routing mode, ARP does not work, so the correct destination MAC
2123 can not be known by the sending host.
2124 Tinc solves this by letting the receiving end detect the MAC address of its own virtual network interface
2125 and overwriting the destination MAC address of the received packet.
2127 In switch or hub modes ARP does work so the sender already knows the correct destination MAC address.
2128 In those modes every interface should have a unique MAC address, so make sure they are not the same.
2129 Because switch and hub modes rely on MAC addresses to function correctly,
2130 these modes cannot be used on the following operating systems which don't have a `tap' style virtual network device:
2131 OpenBSD, NetBSD, Darwin and Solaris.
2134 @c ==================================================================
2135 @node The meta-connection
2136 @subsection The meta-connection
2138 Having only a UDP connection available is not enough. Though suitable
2139 for transmitting data, we want to be able to reliably send other
2140 information, such as routing and session key information to somebody.
2143 TCP is a better alternative, because it already contains protection
2144 against information being lost, unlike UDP.
2146 So we establish two connections. One for the encrypted VPN data, and one
2147 for other information, the meta-data. Hence, we call the second
2148 connection the meta-connection. We can now be sure that the
2149 meta-information doesn't get lost on the way to another computer.
2151 @cindex data-protocol
2152 @cindex meta-protocol
2153 Like with any communication, we must have a protocol, so that everybody
2154 knows what everything stands for, and how she should react. Because we
2155 have two connections, we also have two protocols. The protocol used for
2156 the UDP data is the ``data-protocol,'' the other one is the
2159 The reason we don't use TCP for both protocols is that UDP is much
2160 better for encapsulation, even while it is less reliable. The real
2161 problem is that when TCP would be used to encapsulate a TCP stream
2162 that's on the private network, for every packet sent there would be
2163 three ACKs sent instead of just one. Furthermore, if there would be
2164 a timeout, both TCP streams would sense the timeout, and both would
2165 start re-sending packets.
2168 @c ==================================================================
2169 @node The meta-protocol
2170 @section The meta-protocol
2172 The meta protocol is used to tie all tinc daemons together, and
2173 exchange information about which tinc daemon serves which virtual
2176 The meta protocol consists of requests that can be sent to the other
2177 side. Each request has a unique number and several parameters. All
2178 requests are represented in the standard ASCII character set. It is
2179 possible to use tools such as telnet or netcat to connect to a tinc
2180 daemon started with the --bypass-security option
2181 and to read and write requests by hand, provided that one
2182 understands the numeric codes sent.
2184 The authentication scheme is described in @ref{Authentication protocol}. After a
2185 successful authentication, the server and the client will exchange all the
2186 information about other tinc daemons and subnets they know of, so that both
2187 sides (and all the other tinc daemons behind them) have their information
2194 ------------------------------------------------------------------
2195 ADD_EDGE node1 node2 21.32.43.54 655 222 0
2196 | | | | | +-> options
2197 | | | | +----> weight
2198 | | | +--------> UDP port of node2
2199 | | +----------------> real address of node2
2200 | +-------------------------> name of destination node
2201 +-------------------------------> name of source node
2203 ADD_SUBNET node 192.168.1.0/24
2204 | | +--> prefixlength
2205 | +--------> network address
2206 +------------------> owner of this subnet
2207 ------------------------------------------------------------------
2210 The ADD_EDGE messages are to inform other tinc daemons that a connection between
2211 two nodes exist. The address of the destination node is available so that
2212 VPN packets can be sent directly to that node.
2214 The ADD_SUBNET messages inform other tinc daemons that certain subnets belong
2215 to certain nodes. tinc will use it to determine to which node a VPN packet has
2222 ------------------------------------------------------------------
2223 DEL_EDGE node1 node2
2224 | +----> name of destination node
2225 +----------> name of source node
2227 DEL_SUBNET node 192.168.1.0/24
2228 | | +--> prefixlength
2229 | +--------> network address
2230 +------------------> owner of this subnet
2231 ------------------------------------------------------------------
2234 In case a connection between two daemons is closed or broken, DEL_EDGE messages
2235 are sent to inform the other daemons of that fact. Each daemon will calculate a
2236 new route to the the daemons, or mark them unreachable if there isn't any.
2243 ------------------------------------------------------------------
2244 REQ_KEY origin destination
2245 | +--> name of the tinc daemon it wants the key from
2246 +----------> name of the daemon that wants the key
2248 ANS_KEY origin destination 4ae0b0a82d6e0078 91 64 4
2249 | | \______________/ | | +--> MAC length
2250 | | | | +-----> digest algorithm
2251 | | | +--------> cipher algorithm
2252 | | +--> 128 bits key
2253 | +--> name of the daemon that wants the key
2254 +----------> name of the daemon that uses this key
2257 +--> daemon that has changed it's packet key
2258 ------------------------------------------------------------------
2261 The keys used to encrypt VPN packets are not sent out directly. This is
2262 because it would generate a lot of traffic on VPNs with many daemons, and
2263 chances are that not every tinc daemon will ever send a packet to every
2264 other daemon. Instead, if a daemon needs a key it sends a request for it
2265 via the meta connection of the nearest hop in the direction of the
2272 ------------------------------------------------------------------
2275 ------------------------------------------------------------------
2278 There is also a mechanism to check if hosts are still alive. Since network
2279 failures or a crash can cause a daemon to be killed without properly
2280 shutting down the TCP connection, this is necessary to keep an up to date
2281 connection list. PINGs are sent at regular intervals, except when there
2282 is also some other traffic. A little bit of salt (random data) is added
2283 with each PING and PONG message, to make sure that long sequences of PING/PONG
2284 messages without any other traffic won't result in known plaintext.
2286 This basically covers what is sent over the meta connection by tinc.
2289 @c ==================================================================
2295 Tinc got its name from ``TINC,'' short for @emph{There Is No Cabal}; the
2296 alleged Cabal was/is an organisation that was said to keep an eye on the
2297 entire Internet. As this is exactly what you @emph{don't} want, we named
2298 the tinc project after TINC.
2301 But in order to be ``immune'' to eavesdropping, you'll have to encrypt
2302 your data. Because tinc is a @emph{Secure} VPN (SVPN) daemon, it does
2303 exactly that: encrypt.
2304 Tinc by default uses blowfish encryption with 128 bit keys in CBC mode, 32 bit
2305 sequence numbers and 4 byte long message authentication codes to make sure
2306 eavesdroppers cannot get and cannot change any information at all from the
2307 packets they can intercept. The encryption algorithm and message authentication
2308 algorithm can be changed in the configuration. The length of the message
2309 authentication codes is also adjustable. The length of the key for the
2310 encryption algorithm is always the default length used by OpenSSL.
2313 * Authentication protocol::
2314 * Encryption of network packets::
2319 @c ==================================================================
2320 @node Authentication protocol
2321 @subsection Authentication protocol
2323 @cindex authentication
2324 A new scheme for authentication in tinc has been devised, which offers some
2325 improvements over the protocol used in 1.0pre2 and 1.0pre3. Explanation is
2335 --------------------------------------------------------------------------
2336 client <attempts connection>
2338 server <accepts connection>
2342 +-------> name of tinc daemon
2346 +-------> name of tinc daemon
2348 client META_KEY 5f0823a93e35b69e...7086ec7866ce582b
2349 \_________________________________/
2350 +-> RSAKEYLEN bits totally random string S1,
2351 encrypted with server's public RSA key
2353 server META_KEY 6ab9c1640388f8f0...45d1a07f8a672630
2354 \_________________________________/
2355 +-> RSAKEYLEN bits totally random string S2,
2356 encrypted with client's public RSA key
2359 - the client will symmetrically encrypt outgoing traffic using S1
2360 - the server will symmetrically encrypt outgoing traffic using S2
2362 client CHALLENGE da02add1817c1920989ba6ae2a49cecbda0
2363 \_________________________________/
2364 +-> CHALLEN bits totally random string H1
2366 server CHALLENGE 57fb4b2ccd70d6bb35a64c142f47e61d57f
2367 \_________________________________/
2368 +-> CHALLEN bits totally random string H2
2370 client CHAL_REPLY 816a86
2371 +-> 160 bits SHA1 of H2
2373 server CHAL_REPLY 928ffe
2374 +-> 160 bits SHA1 of H1
2376 After the correct challenge replies are received, both ends have proved
2377 their identity. Further information is exchanged.
2379 client ACK 655 123 0
2381 | +----> estimated weight
2382 +--------> listening port of client
2384 server ACK 655 321 0
2386 | +----> estimated weight
2387 +--------> listening port of server
2388 --------------------------------------------------------------------------
2391 This new scheme has several improvements, both in efficiency and security.
2393 First of all, the server sends exactly the same kind of messages over the wire
2394 as the client. The previous versions of tinc first authenticated the client,
2395 and then the server. This scheme even allows both sides to send their messages
2396 simultaneously, there is no need to wait for the other to send something first.
2397 This means that any calculations that need to be done upon sending or receiving
2398 a message can also be done in parallel. This is especially important when doing
2399 RSA encryption/decryption. Given that these calculations are the main part of
2400 the CPU time spent for the authentication, speed is improved by a factor 2.
2402 Second, only one RSA encrypted message is sent instead of two. This reduces the
2403 amount of information attackers can see (and thus use for a cryptographic
2404 attack). It also improves speed by a factor two, making the total speedup a
2407 Third, and most important:
2408 The symmetric cipher keys are exchanged first, the challenge is done
2409 afterwards. In the previous authentication scheme, because a man-in-the-middle
2410 could pass the challenge/chal_reply phase (by just copying the messages between
2411 the two real tinc daemons), but no information was exchanged that was really
2412 needed to read the rest of the messages, the challenge/chal_reply phase was of
2413 no real use. The man-in-the-middle was only stopped by the fact that only after
2414 the ACK messages were encrypted with the symmetric cipher. Potentially, it
2415 could even send it's own symmetric key to the server (if it knew the server's
2416 public key) and read some of the metadata the server would send it (it was
2417 impossible for the mitm to read actual network packets though). The new scheme
2418 however prevents this.
2420 This new scheme makes sure that first of all, symmetric keys are exchanged. The
2421 rest of the messages are then encrypted with the symmetric cipher. Then, each
2422 side can only read received messages if they have their private key. The
2423 challenge is there to let the other side know that the private key is really
2424 known, because a challenge reply can only be sent back if the challenge is
2425 decrypted correctly, and that can only be done with knowledge of the private
2428 Fourth: the first thing that is sent via the symmetric cipher encrypted
2429 connection is a totally random string, so that there is no known plaintext (for
2430 an attacker) in the beginning of the encrypted stream.
2433 @c ==================================================================
2434 @node Encryption of network packets
2435 @subsection Encryption of network packets
2438 A data packet can only be sent if the encryption key is known to both
2439 parties, and the connection is activated. If the encryption key is not
2440 known, a request is sent to the destination using the meta connection
2441 to retrieve it. The packet is stored in a queue while waiting for the
2445 The UDP packet containing the network packet from the VPN has the following layout:
2448 ... | IP header | UDP header | seqno | VPN packet | MAC | UDP trailer
2449 \___________________/\_____/
2451 V +---> digest algorithm
2452 Encrypted with symmetric cipher
2455 So, the entire VPN packet is encrypted using a symmetric cipher, including a 32 bits
2456 sequence number that is added in front of the actual VPN packet, to act as a unique
2457 IV for each packet and to prevent replay attacks. A message authentication code
2458 is added to the UDP packet to prevent alteration of packets. By default the
2459 first 4 bytes of the digest are used for this, but this can be changed using
2460 the MACLength configuration variable.
2462 @c ==================================================================
2463 @node Security issues
2464 @subsection Security issues
2466 In August 2000, we discovered the existence of a security hole in all versions
2467 of tinc up to and including 1.0pre2. This had to do with the way we exchanged
2468 keys. Since then, we have been working on a new authentication scheme to make
2469 tinc as secure as possible. The current version uses the OpenSSL library and
2470 uses strong authentication with RSA keys.
2472 On the 29th of December 2001, Jerome Etienne posted a security analysis of tinc
2473 1.0pre4. Due to a lack of sequence numbers and a message authentication code
2474 for each packet, an attacker could possibly disrupt certain network services or
2475 launch a denial of service attack by replaying intercepted packets. The current
2476 version adds sequence numbers and message authentication codes to prevent such
2479 On the 15th of September 2003, Peter Gutmann posted a security analysis of tinc
2480 1.0.1. He argues that the 32 bit sequence number used by tinc is not a good IV,
2481 that tinc's default length of 4 bytes for the MAC is too short, and he doesn't
2482 like tinc's use of RSA during authentication. We do not know of a security hole
2483 in this version of tinc, but tinc's security is not as strong as TLS or IPsec.
2484 We will address these issues in tinc 2.0.
2486 Cryptography is a hard thing to get right. We cannot make any
2487 guarantees. Time, review and feedback are the only things that can
2488 prove the security of any cryptographic product. If you wish to review
2489 tinc or give us feedback, you are stronly encouraged to do so.
2492 @c ==================================================================
2493 @node Platform specific information
2494 @chapter Platform specific information
2497 * Interface configuration::
2501 @c ==================================================================
2502 @node Interface configuration
2503 @section Interface configuration
2505 When configuring an interface, one normally assigns it an address and a
2506 netmask. The address uniquely identifies the host on the network attached to
2507 the interface. The netmask, combined with the address, forms a subnet. It is
2508 used to add a route to the routing table instructing the kernel to send all
2509 packets which fall into that subnet to that interface. Because all packets for
2510 the entire VPN should go to the virtual network interface used by tinc, the
2511 netmask should be such that it encompasses the entire VPN.
2515 @multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
2517 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2518 @item Linux iproute2
2519 @tab @code{ip addr add} @var{address}@code{/}@var{prefixlength} @code{dev} @var{interface}
2521 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2523 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2525 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2527 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2528 @item Darwin (MacOS/X)
2529 @tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
2531 @tab @code{netsh interface ip set address} @var{interface} @code{static} @var{address} @var{netmask}
2537 @multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
2539 @tab @code{ifconfig} @var{interface} @code{add} @var{address}@code{/}@var{prefixlength}
2541 @tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
2543 @tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
2545 @tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
2547 @tab @code{ifconfig} @var{interface} @code{inet6 plumb up}
2549 @tab @code{ifconfig} @var{interface} @code{inet6 addif} @var{address} @var{address}
2550 @item Darwin (MacOS/X)
2551 @tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
2553 @tab @code{netsh interface ipv6 add address} @var{interface} @code{static} @var{address}/@var{prefixlength}
2557 @c ==================================================================
2561 In some cases it might be necessary to add more routes to the virtual network
2562 interface. There are two ways to indicate which interface a packet should go
2563 to, one is to use the name of the interface itself, another way is to specify
2564 the (local) address that is assigned to that interface (@var{local_address}). The
2565 former way is unambiguous and therefore preferable, but not all platforms
2568 Adding routes to IPv4 subnets:
2570 @multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
2572 @tab @code{route add -net} @var{network_address} @code{netmask} @var{netmask} @var{interface}
2573 @item Linux iproute2
2574 @tab @code{ip route add} @var{network_address}@code{/}@var{prefixlength} @code{dev} @var{interface}
2576 @tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2578 @tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2580 @tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2582 @tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address} @code{-interface}
2583 @item Darwin (MacOS/X)
2584 @tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2586 @tab @code{netsh routing ip add persistentroute} @var{network_address} @var{netmask} @var{interface} @var{local_address}
2589 Adding routes to IPv6 subnets:
2591 @multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
2593 @tab @code{route add -A inet6} @var{network_address}@code{/}@var{prefixlength} @var{interface}
2594 @item Linux iproute2
2595 @tab @code{ip route add} @var{network_address}@code{/}@var{prefixlength} @code{dev} @var{interface}
2597 @tab @code{route add -inet6} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2599 @tab @code{route add -inet6} @var{network_address} @var{local_address} @code{-prefixlen} @var{prefixlength}
2601 @tab @code{route add -inet6} @var{network_address} @var{local_address} @code{-prefixlen} @var{prefixlength}
2603 @tab @code{route add -inet6} @var{network_address}@code{/}@var{prefixlength} @var{local_address} @code{-interface}
2604 @item Darwin (MacOS/X)
2607 @tab @code{netsh interface ipv6 add route} @var{network address}/@var{prefixlength} @var{interface}
2611 @c ==================================================================
2617 * Contact information::
2622 @c ==================================================================
2623 @node Contact information
2624 @section Contact information
2627 Tinc's website is at @url{http://www.tinc-vpn.org/},
2628 this server is located in the Netherlands.
2631 We have an IRC channel on the FreeNode and OFTC IRC networks. Connect to
2632 @uref{http://www.freenode.net/, irc.freenode.net}
2634 @uref{http://www.oftc.net/, irc.oftc.net}
2635 and join channel #tinc.
2638 @c ==================================================================
2643 @item Ivo Timmermans (zarq)
2644 @item Guus Sliepen (guus) (@email{guus@@tinc-vpn.org})
2647 We have received a lot of valuable input from users. With their help,
2648 tinc has become the flexible and robust tool that it is today. We have
2649 composed a list of contributions, in the file called @file{THANKS} in
2650 the source distribution.
2653 @c ==================================================================
2655 @unnumbered Concept Index
2657 @c ==================================================================
2661 @c ==================================================================