2000-03-26 00:33:07 +00:00
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename tinc.info
@settitle tinc Manual
@setchapternewpage odd
@c %**end of header
2003-08-08 14:07:12 +00:00
@include tincinclude.texi
2000-03-26 00:33:07 +00:00
@ifinfo
2002-02-10 21:57:54 +00:00
@dircategory Networking tools
2000-04-26 22:42:15 +00:00
@direntry
* tinc: (tinc). The tinc Manual.
@end direntry
2000-03-26 00:33:07 +00:00
2003-08-08 14:07:12 +00:00
This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon.
2000-03-26 00:33:07 +00:00
2009-03-05 13:12:36 +00:00
Copyright @copyright{} 1998-2009 Ivo Timmermans,
2006-04-26 13:52:58 +00:00
Guus Sliepen <guus@@tinc-vpn.org> and
2004-03-21 14:21:22 +00:00
Wessel Dankers <wsl@@tinc-vpn.org>.
2000-03-26 00:33:07 +00:00
2000-09-27 20:32:29 +00:00
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
2000-03-26 00:33:07 +00:00
@end ifinfo
@titlepage
@title tinc Manual
@subtitle Setting up a Virtual Private Network with tinc
2000-09-27 20:32:29 +00:00
@author Ivo Timmermans and Guus Sliepen
2000-03-26 00:33:07 +00:00
@page
@vskip 0pt plus 1filll
2000-09-27 20:32:29 +00:00
@cindex copyright
2003-08-08 14:07:12 +00:00
This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon.
2009-03-05 13:12:36 +00:00
Copyright @copyright{} 1998-2009 Ivo Timmermans,
2006-04-26 13:52:58 +00:00
Guus Sliepen <guus@@tinc-vpn.org> and
2004-03-21 14:21:22 +00:00
Wessel Dankers <wsl@@tinc-vpn.org>.
2000-03-26 00:33:07 +00:00
2000-09-27 20:32:29 +00:00
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
2000-03-26 00:33:07 +00:00
2000-09-27 20:32:29 +00:00
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
2000-03-26 00:33:07 +00:00
@end titlepage
2003-10-09 21:33:15 +00:00
@ifinfo
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Top
@top Top
2000-03-26 00:33:07 +00:00
@menu
2003-08-09 00:53:22 +00:00
* Introduction::
2001-05-24 20:24:12 +00:00
* Preparations::
* Installation::
* Configuration::
* Running tinc::
* Technical information::
2003-10-09 21:33:15 +00:00
* Platform specific information::
2001-05-24 20:24:12 +00:00
* About us::
2000-03-26 00:33:07 +00:00
* Concept Index:: All used terms explained
@end menu
2003-10-09 21:33:15 +00:00
@end ifinfo
2000-09-27 20:32:29 +00:00
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Introduction
2000-03-26 00:33:07 +00:00
@chapter Introduction
2000-09-27 20:32:29 +00:00
@cindex tinc
2003-10-09 21:33:15 +00:00
Tinc is a Virtual Private Network (VPN) daemon that uses tunneling and
2000-03-26 00:33:07 +00:00
encryption to create a secure private network between hosts on the
Internet.
Because the tunnel appears to the IP level network code as a normal
network device, there is no need to adapt any existing software.
2001-05-24 20:24:12 +00:00
The encrypted tunnels allows VPN sites to share information with each other
2000-03-26 00:33:07 +00:00
over the Internet without exposing any information to others.
2000-11-30 23:39:55 +00:00
This document is the manual for tinc. Included are chapters on how to
2000-03-26 00:33:07 +00:00
configure your computer to use tinc, as well as the configuration
process of tinc itself.
@menu
2003-08-09 00:53:22 +00:00
* Virtual Private Networks::
* tinc:: About tinc
2001-05-24 20:24:12 +00:00
* Supported platforms::
2000-03-26 00:33:07 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Virtual Private Networks
2000-03-26 00:33:07 +00:00
@section Virtual Private Networks
2000-09-27 20:32:29 +00:00
@cindex VPN
2000-03-26 00:33:07 +00:00
A Virtual Private Network or VPN is a network that can only be accessed
2000-11-30 23:39:55 +00:00
by a few elected computers that participate. This goal is achievable in
2000-03-26 00:33:07 +00:00
more than just one way.
@cindex private
2001-05-24 20:24:12 +00:00
Private networks can consist of a single stand-alone Ethernet LAN. Or
2000-11-30 23:39:55 +00:00
even two computers hooked up using a null-modem cable. In these cases,
2000-05-27 13:21:20 +00:00
it is
2000-08-18 14:45:38 +00:00
obvious that the network is @emph{private}, no one can access it from the
2001-05-24 20:24:12 +00:00
outside. But if your computers are linked to the Internet, the network
2000-05-27 13:21:20 +00:00
is not private anymore, unless one uses firewalls to block all private
2000-11-30 23:39:55 +00:00
traffic. But then, there is no way to send private data to trusted
2001-05-24 20:24:12 +00:00
computers on the other end of the Internet.
2000-05-27 13:21:20 +00:00
@cindex virtual
2000-11-30 23:39:55 +00:00
This problem can be solved by using @emph{virtual} networks. Virtual
2001-01-06 20:02:21 +00:00
networks can live on top of other networks, but they use encapsulation to
keep using their private address space so they do not interfere with
2001-05-24 20:24:12 +00:00
the Internet. Mostly, virtual networks appear like a singe LAN, even though
2000-11-30 23:39:55 +00:00
they can span the entire world. But virtual networks can't be secured
2000-05-27 13:21:20 +00:00
by using firewalls, because the traffic that flows through it has to go
2001-05-24 20:24:12 +00:00
through the Internet, where other people can look at it.
As is the case with either type of VPN, anybody could eavesdrop. Or
worse, alter data. Hence it's probably advisable to encrypt the data
that flows over the network.
2000-05-27 13:21:20 +00:00
2000-11-30 23:39:55 +00:00
When one introduces encryption, we can form a true VPN. Other people may
2000-05-27 13:21:20 +00:00
see encrypted traffic, but if they don't know how to decipher it (they
need to know the key for that), they cannot read the information that flows
2000-11-30 23:39:55 +00:00
through the VPN. This is what tinc was made for.
2000-03-26 00:33:07 +00:00
2000-04-25 01:45:34 +00:00
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node tinc
2000-03-26 00:33:07 +00:00
@section tinc
2000-09-27 20:32:29 +00:00
@cindex vpnd
2000-03-26 00:33:07 +00:00
I really don't quite remember what got us started, but it must have been
2000-11-30 23:39:55 +00:00
Guus' idea. He wrote a simple implementation (about 50 lines of C) that
2001-05-24 20:24:12 +00:00
used the ethertap device that Linux knows of since somewhere
2000-11-30 23:39:55 +00:00
about kernel 2.1.60. It didn't work immediately and he improved it a
2003-10-09 21:33:15 +00:00
bit. At this stage, the project was still simply called "vpnd".
2000-03-26 00:33:07 +00:00
Since then, a lot has changed---to say the least.
@cindex tincd
2003-10-09 21:33:15 +00:00
Tinc now supports encryption, it consists of a single daemon (tincd) for
2000-04-25 01:45:34 +00:00
both the receiving and sending end, it has become largely
2000-03-26 00:33:07 +00:00
runtime-configurable---in short, it has become a full-fledged
professional package.
2003-10-11 14:42:30 +00:00
@cindex traditional VPNs
2001-05-24 20:24:12 +00:00
@cindex scalability
2003-10-09 21:33:15 +00:00
Tinc also allows more than two sites to connect to eachother and form a single VPN.
2001-05-24 20:24:12 +00:00
Traditionally VPNs are created by making tunnels, which only have two endpoints.
Larger VPNs with more sites are created by adding more tunnels.
2003-10-09 21:33:15 +00:00
Tinc takes another approach: only endpoints are specified,
2001-05-24 20:24:12 +00:00
the software itself will take care of creating the tunnels.
This allows for easier configuration and improved scalability.
2001-01-06 20:02:21 +00:00
A lot can---and will be---changed. We have a number of things that we would like to
2000-11-30 23:39:55 +00:00
see in the future releases of tinc. Not everything will be available in
the near future. Our first objective is to make tinc work perfectly as
2000-03-26 00:33:07 +00:00
it stands, and then add more advanced features.
2000-11-30 23:39:55 +00:00
Meanwhile, we're always open-minded towards new ideas. And we're
2000-03-26 00:33:07 +00:00
available too.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Supported platforms
2000-09-27 20:32:29 +00:00
@section Supported platforms
2001-05-24 20:24:12 +00:00
@cindex platforms
2003-10-09 21:33:15 +00:00
Tinc has been verified to work under Linux, FreeBSD, OpenBSD, NetBSD, MacOS/X (Darwin), Solaris, and Windows (both natively and in a Cygwin environment),
2003-07-21 19:58:58 +00:00
with various hardware architectures. These are some of the platforms
2002-02-10 21:57:54 +00:00
that are supported by the universal tun/tap device driver or other virtual network device drivers.
Without such a driver, tinc will most
2000-09-27 20:32:29 +00:00
likely compile and run, but it will not be able to send or receive data
packets.
2001-05-24 20:24:12 +00:00
@cindex release
2001-01-06 20:02:21 +00:00
For an up to date list of supported platforms, please check the list on
our website:
2004-03-21 14:21:22 +00:00
@uref{http://www.tinc-vpn.org/platforms}.
2000-11-24 14:13:51 +00:00
2000-09-27 20:32:29 +00:00
@c
@c
@c
@c
@c
@c
@c Preparing your system
@c
@c
@c
@c
@c
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Preparations
2001-05-24 20:24:12 +00:00
@chapter Preparations
2000-03-26 00:33:07 +00:00
2000-09-27 20:32:29 +00:00
This chapter contains information on how to prepare your system to
support tinc.
2000-03-26 00:33:07 +00:00
@menu
2001-05-24 20:24:12 +00:00
* Configuring the kernel::
* Libraries::
2000-03-26 00:33:07 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuring the kernel
2000-03-26 00:33:07 +00:00
@section Configuring the kernel
2000-09-27 20:32:29 +00:00
@menu
2008-12-22 21:29:21 +00:00
* Configuration of Linux kernels::
2001-05-24 20:24:12 +00:00
* Configuration of FreeBSD kernels::
2002-02-10 21:57:54 +00:00
* Configuration of OpenBSD kernels::
2002-06-12 13:45:23 +00:00
* Configuration of NetBSD kernels::
2001-05-24 20:24:12 +00:00
* Configuration of Solaris kernels::
2002-06-12 13:45:23 +00:00
* Configuration of Darwin (MacOS/X) kernels::
2003-08-09 00:53:22 +00:00
* Configuration of Windows::
2000-09-27 20:32:29 +00:00
@end menu
@c ==================================================================
2008-12-22 21:29:21 +00:00
@node Configuration of Linux kernels
@subsection Configuration of Linux kernels
2001-05-19 15:50:51 +00:00
2004-11-10 23:21:41 +00:00
@cindex Universal tun/tap
2008-12-22 21:29:21 +00:00
For tinc to work, you need a kernel that supports the Universal tun/tap device.
2004-11-10 23:21:41 +00:00
Most distributions come with kernels that already support this.
2001-05-24 20:24:12 +00:00
Here are the options you have to turn on when configuring a new kernel:
2000-09-27 20:32:29 +00:00
@example
Code maturity level options
[*] Prompt for development and/or incomplete code/drivers
Network device support
2002-02-10 21:57:54 +00:00
<M> Universal tun/tap device driver support
2000-09-27 20:32:29 +00:00
@end example
2001-05-19 15:50:51 +00:00
It's not necessary to compile this driver as a module, even if you are going to
run more than one instance of tinc.
2000-09-27 20:32:29 +00:00
2002-02-10 21:57:54 +00:00
If you decide to build the tun/tap driver as a kernel module, add these lines
2001-05-19 15:50:51 +00:00
to @file{/etc/modules.conf}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
alias char-major-10-200 tun
2000-03-26 00:33:07 +00:00
@end example
2000-09-27 20:32:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of FreeBSD kernels
2001-05-24 20:24:12 +00:00
@subsection Configuration of FreeBSD kernels
2000-09-27 20:32:29 +00:00
2004-11-10 23:21:41 +00:00
For FreeBSD version 4.1 and higher, tun and tap drivers are included in the default kernel configuration.
Using tap devices is recommended.
2000-09-27 20:32:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of OpenBSD kernels
2002-02-10 21:57:54 +00:00
@subsection Configuration of OpenBSD kernels
2003-07-30 09:22:29 +00:00
For OpenBSD version 2.9 and higher,
the tun driver is included in the default kernel configuration.
2004-11-10 23:21:41 +00:00
There is also a kernel patch from @uref{http://diehard.n-r-g.com/stuff/openbsd/}
2008-12-22 21:29:21 +00:00
which adds a tap device to OpenBSD which should work with tinc,
but with recent versions of OpenBSD,
a tun device can act as a tap device by setting the link0 option with ifconfig.
2002-02-10 21:57:54 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of NetBSD kernels
2002-06-12 13:45:23 +00:00
@subsection Configuration of NetBSD kernels
2003-07-30 09:22:29 +00:00
For NetBSD version 1.5.2 and higher,
the tun driver is included in the default kernel configuration.
2002-06-12 13:45:23 +00:00
2004-11-10 23:21:41 +00:00
Tunneling IPv6 may not work on NetBSD's tun device.
2002-06-12 13:45:23 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of Solaris kernels
2001-05-24 20:24:12 +00:00
@subsection Configuration of Solaris kernels
2000-09-27 20:32:29 +00:00
2003-07-30 09:22:29 +00:00
For Solaris 8 (SunOS 5.8) and higher,
2003-10-09 21:33:15 +00:00
the tun driver may or may not be included in the default kernel configuration.
If it isn't, the source can be downloaded from @uref{http://vtun.sourceforge.net/tun/}.
For x86 and sparc64 architectures, precompiled versions can be found at @uref{http://www.monkey.org/~dugsong/fragroute/}.
If the @file{net/if_tun.h} header file is missing, install it from the source package.
2000-09-27 20:32:29 +00:00
2002-06-12 13:45:23 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of Darwin (MacOS/X) kernels
2002-06-12 13:45:23 +00:00
@subsection Configuration of Darwin (MacOS/X) kernels
2004-11-10 23:21:41 +00:00
Tinc on Darwin relies on a tunnel driver for its data acquisition from the kernel.
2009-05-24 15:13:00 +00:00
Tinc supports either the driver from @uref{http://tuntaposx.sourceforge.net/},
2004-11-10 23:21:41 +00:00
which supports both tun and tap style devices,
and also the driver from from @uref{http://chrisp.de/en/projects/tunnel.html}.
The former driver is recommended.
The tunnel driver must be loaded before starting tinc with the following command:
2002-06-12 13:45:23 +00:00
@example
kmodload tunnel
@end example
2003-07-21 19:58:58 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration of Windows
2003-08-09 00:53:22 +00:00
@subsection Configuration of Windows
2003-07-21 19:58:58 +00:00
2004-11-10 21:57:04 +00:00
You will need to install the latest TAP-Win32 driver from OpenVPN.
You can download it from @uref{http://openvpn.sourceforge.net}.
Using the Network Connections control panel,
configure the TAP-Win32 network interface in the same way as you would do from the tinc-up script,
as explained in the rest of the documentation.
2003-07-21 19:58:58 +00:00
2000-09-27 20:32:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Libraries
2000-09-27 20:32:29 +00:00
@section Libraries
@cindex requirements
2001-05-24 20:24:12 +00:00
@cindex libraries
2003-06-11 20:18:48 +00:00
Before you can configure or build tinc, you need to have the OpenSSL,
zlib and lzo libraries installed on your system. If you try to configure tinc without
2002-09-15 22:19:38 +00:00
having them installed, configure will give you an error message, and stop.
2000-09-27 20:32:29 +00:00
@menu
2001-05-24 20:24:12 +00:00
* OpenSSL::
2002-03-25 15:01:32 +00:00
* zlib::
2003-06-11 20:18:48 +00:00
* lzo::
2000-09-27 20:32:29 +00:00
@end menu
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node OpenSSL
2000-09-27 20:32:29 +00:00
@subsection OpenSSL
@cindex OpenSSL
For all cryptography-related functions, tinc uses the functions provided
2001-05-19 15:50:51 +00:00
by the OpenSSL library.
2000-09-27 20:32:29 +00:00
2000-10-14 22:17:29 +00:00
If this library is not installed, you wil get an error when configuring
tinc for build. Support for running tinc without having OpenSSL
installed @emph{may} be added in the future.
You can use your operating system's package manager to install this if
available. Make sure you install the development AND runtime versions
of this package.
2000-09-27 20:32:29 +00:00
If you have to install OpenSSL manually, you can get the source code
from @url{http://www.openssl.org/}. Instructions on how to configure,
build and install this package are included within the package. Please
make sure you build development and runtime libraries (which is the
default).
2000-11-24 14:13:51 +00:00
If you installed the OpenSSL libraries from source, it may be necessary
to let configure know where they are, by passing configure one of the
--with-openssl-* parameters.
@example
--with-openssl=DIR OpenSSL library and headers prefix
--with-openssl-include=DIR OpenSSL headers directory
(Default is OPENSSL_DIR/include)
--with-openssl-lib=DIR OpenSSL library directory
(Default is OPENSSL_DIR/lib)
@end example
2000-09-27 20:32:29 +00:00
2000-12-05 08:54:22 +00:00
@subsubheading License
2001-05-24 20:24:12 +00:00
@cindex license
2003-10-09 21:33:15 +00:00
The complete source code of tinc is covered by the GNU GPL version 2.
2000-12-05 08:54:22 +00:00
Since the license under which OpenSSL is distributed is not directly
compatible with the terms of the GNU GPL
2003-10-09 21:33:15 +00:00
@uref{http://www.openssl.org/support/faq.html#LEGAL2}, we
include an exemption to the GPL (see also the file COPYING.README) to allow
everyone to create a statically or dynamically linked executable:
2000-12-05 08:54:22 +00:00
@quotation
This program is released under the GPL with the additional exemption
that compiling, linking, and/or using OpenSSL is allowed. You may
provide binary packages linked to the OpenSSL libraries, provided that
all other requirements of the GPL are met.
@end quotation
2003-10-09 21:33:15 +00:00
Since the LZO library used by tinc is also covered by the GPL,
we also present the following exemption:
@quotation
Hereby I grant a special exception to the tinc VPN project
2004-03-21 14:21:22 +00:00
(http://www.tinc-vpn.org/) to link the LZO library with the OpenSSL library
2003-10-09 21:33:15 +00:00
(http://www.openssl.org).
Markus F.X.J. Oberhumer
@end quotation
2000-12-05 08:54:22 +00:00
2002-03-25 15:01:32 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node zlib
2002-03-25 15:01:32 +00:00
@subsection zlib
@cindex zlib
For the optional compression of UDP packets, tinc uses the functions provided
by the zlib library.
If this library is not installed, you wil get an error when configuring
tinc for build. Support for running tinc without having zlib
installed @emph{may} be added in the future.
You can use your operating system's package manager to install this if
available. Make sure you install the development AND runtime versions
of this package.
If you have to install zlib manually, you can get the source code
from @url{http://www.gzip.org/zlib/}. Instructions on how to configure,
build and install this package are included within the package. Please
make sure you build development and runtime libraries (which is the
default).
2003-06-11 20:18:48 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node lzo
2003-06-11 20:18:48 +00:00
@subsection lzo
@cindex lzo
Another form of compression is offered using the lzo library.
If this library is not installed, you wil get an error when configuring
tinc for build. Support for running tinc without having lzo
installed @emph{may} be added in the future.
You can use your operating system's package manager to install this if
available. Make sure you install the development AND runtime versions
of this package.
If you have to install lzo manually, you can get the source code
from @url{http://www.oberhumer.com/opensource/lzo/}. Instructions on how to configure,
build and install this package are included within the package. Please
make sure you build development and runtime libraries (which is the
default).
2000-09-27 20:32:29 +00:00
@c
@c
@c
@c Installing tinc
@c
@c
@c
@c
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Installation
2001-05-24 20:24:12 +00:00
@chapter Installation
2000-09-27 20:32:29 +00:00
2002-02-10 21:57:54 +00:00
If you use Debian, you may want to install one of the
2000-09-27 20:32:29 +00:00
precompiled packages for your system. These packages are equipped with
system startup scripts and sample configurations.
2002-02-10 21:57:54 +00:00
If you cannot use one of the precompiled packages, or you want to compile tinc
2000-09-27 20:32:29 +00:00
for yourself, you can use the source. The source is distributed under
the GNU General Public License (GPL). Download the source from the
2004-03-21 14:21:22 +00:00
@uref{http://www.tinc-vpn.org/download, download page}, which has
2000-09-27 20:32:29 +00:00
the checksums of these files listed; you may wish to check these with
md5sum before continuing.
2003-10-09 21:33:15 +00:00
Tinc comes in a convenient autoconf/automake package, which you can just
2000-11-30 23:39:55 +00:00
treat the same as any other package. Which is just untar it, type
2002-09-15 22:19:38 +00:00
`./configure' and then `make'.
2000-09-27 20:32:29 +00:00
More detailed instructions are in the file @file{INSTALL}, which is
included in the source distribution.
@menu
2001-05-24 20:24:12 +00:00
* Building and installing tinc::
* System files::
2000-09-27 20:32:29 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Building and installing tinc
2001-05-24 20:24:12 +00:00
@section Building and installing tinc
Detailed instructions on configuring the source, building tinc and installing tinc
can be found in the file called @file{INSTALL}.
2000-09-27 20:32:29 +00:00
2001-05-24 20:24:12 +00:00
@cindex binary package
If you happen to have a binary package for tinc for your distribution,
you can use the package management tools of that distribution to install tinc.
The documentation that comes along with your distribution will tell you how to do that.
2000-09-27 20:32:29 +00:00
2002-06-12 13:45:23 +00:00
@menu
* Darwin (MacOS/X) build environment::
2003-07-30 09:22:29 +00:00
* Cygwin (Windows) build environment::
* MinGW (Windows) build environment::
2002-06-12 13:45:23 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Darwin (MacOS/X) build environment
2002-06-12 13:45:23 +00:00
@subsection Darwin (MacOS/X) build environment
In order to build tinc on Darwin, you need to install the MacOS/X Developer Tools
from @uref{http://developer.apple.com/tools/macosxtools.html} and
a recent version of Fink from @uref{http://fink.sourceforge.net/}.
After installation use fink to download and install the following packages:
2003-06-11 20:18:48 +00:00
autoconf25, automake, dlcompat, m4, openssl, zlib and lzo.
2002-06-12 13:45:23 +00:00
2003-07-30 09:22:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Cygwin (Windows) build environment
2003-07-30 09:22:29 +00:00
@subsection Cygwin (Windows) build environment
If Cygwin hasn't already been installed, install it directly from
@uref{http://www.cygwin.com/}.
When tinc is compiled in a Cygwin environment, it can only be run in this environment,
but all programs, including those started outside the Cygwin environment, will be able to use the VPN.
It will also support all features.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node MinGW (Windows) build environment
2003-07-30 09:22:29 +00:00
@subsection MinGW (Windows) build environment
You will need to install the MinGW environment from @uref{http://www.mingw.org}.
When tinc is compiled using MinGW it runs natively under Windows,
it is not necessary to keep MinGW installed.
2003-08-02 21:55:12 +00:00
When detaching, tinc will install itself as a service,
which will be restarted automatically after reboots.
2003-07-30 09:22:29 +00:00
2000-09-27 20:32:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node System files
2000-09-27 20:32:29 +00:00
@section System files
2000-12-05 08:54:22 +00:00
Before you can run tinc, you must make sure you have all the needed
files on your system.
2000-09-27 20:32:29 +00:00
@menu
2001-05-24 20:24:12 +00:00
* Device files::
* Other files::
2000-09-27 20:32:29 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Device files
2000-09-27 20:32:29 +00:00
@subsection Device files
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@cindex device files
2008-12-22 21:29:21 +00:00
Most operating systems nowadays come with the necessary device files by default,
or they have a mechanism to create them on demand.
2000-09-27 20:32:29 +00:00
2008-12-22 21:29:21 +00:00
If you use Linux and do not have udev installed,
you may need to create the following device file if it does not exist:
2000-03-26 00:33:07 +00:00
@example
2008-12-22 21:29:21 +00:00
mknod -m 600 /dev/net/tun c 10 200
2000-03-26 00:33:07 +00:00
@end example
2000-09-27 20:32:29 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Other files
2000-09-27 20:32:29 +00:00
@subsection Other files
2000-03-26 00:33:07 +00:00
@subsubheading @file{/etc/networks}
2000-04-25 10:40:08 +00:00
You may add a line to @file{/etc/networks} so that your VPN will get a
2000-11-30 23:39:55 +00:00
symbolic name. For example:
2000-03-26 00:33:07 +00:00
@example
myvpn 10.0.0.0
@end example
@subsubheading @file{/etc/services}
2001-05-24 20:24:12 +00:00
@cindex port numbers
2000-11-30 23:39:55 +00:00
You may add this line to @file{/etc/services}. The effect is that you
may supply a @samp{tinc} as a valid port number to some programs. The
2000-03-26 00:33:07 +00:00
number 655 is registered with the IANA.
@example
tinc 655/tcp TINC
tinc 655/udp TINC
2004-03-21 14:21:22 +00:00
# Ivo Timmermans <ivo@@tinc-vpn.org>
2000-03-26 00:33:07 +00:00
@end example
2000-09-27 20:32:29 +00:00
@c
@c
@c
@c
@c Configuring tinc
@c
@c
@c
@c
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration
2001-05-24 20:24:12 +00:00
@chapter Configuration
2000-03-26 00:33:07 +00:00
@menu
2001-05-24 20:24:12 +00:00
* Configuration introduction::
* Multiple networks::
* How connections work::
* Configuration files::
* Generating keypairs::
* Network interfaces::
* Example configuration::
2000-03-26 00:33:07 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration introduction
2001-05-24 20:24:12 +00:00
@section Configuration introduction
Before actually starting to configure tinc and editing files,
make sure you have read this entire section so you know what to expect.
Then, make it clear to yourself how you want to organize your VPN:
What are the nodes (computers running tinc)?
What IP addresses/subnets do they have?
What is the network mask of the entire VPN?
Do you need special firewall rules?
Do you have to set up masquerading or forwarding rules?
2003-08-02 22:01:50 +00:00
Do you want to run tinc in router mode or switch mode?
2001-05-24 20:24:12 +00:00
These questions can only be answered by yourself,
you will not find the answers in this documentation.
Make sure you have an adequate understanding of networks in general.
2003-08-09 00:53:22 +00:00
@cindex Network Administrators Guide
2001-05-24 20:24:12 +00:00
A good resource on networking is the
@uref{http://www.linuxdoc.org/LDP/nag2/, Linux Network Administrators Guide}.
If you have everything clearly pictured in your mind,
proceed in the following order:
2002-02-10 21:57:54 +00:00
First, generate the configuration files (@file{tinc.conf}, your host configuration file, @file{tinc-up} and perhaps @file{tinc-down}).
2001-05-24 20:24:12 +00:00
Then generate the keypairs.
Finally, distribute the host configuration files.
These steps are described in the subsections below.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Multiple networks
2001-05-24 20:24:12 +00:00
@section Multiple networks
@cindex multiple networks
@cindex netname
In order to allow you to run more than one tinc daemon on one computer,
for instance if your computer is part of more than one VPN,
2003-10-09 21:33:15 +00:00
you can assign a @var{netname} to your VPN.
2001-05-24 20:24:12 +00:00
It is not required if you only run one tinc daemon,
it doesn't even have to be the same on all the sites of your VPN,
but it is recommended that you choose one anyway.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
We will asume you use a netname throughout this document.
This means that you call tincd with the -n argument,
which will assign a netname to this daemon.
2000-03-26 00:33:07 +00:00
The effect of this is that the daemon will set its configuration
2003-10-09 21:33:15 +00:00
root to @file{@value{sysconfdir}/tinc/@var{netname}/}, where @var{netname} is your argument to the -n
option. You'll notice that it appears in syslog as @file{tinc.@var{netname}}.
2000-03-26 00:33:07 +00:00
However, it is not strictly necessary that you call tinc with the -n
2000-11-30 23:39:55 +00:00
option. In this case, the network name would just be empty, and it will
2003-10-09 21:33:15 +00:00
be used as such. tinc now looks for files in @file{@value{sysconfdir}/tinc/}, instead of
@file{@value{sysconfdir}/tinc/@var{netname}/}; the configuration file should be @file{@value{sysconfdir}/tinc/tinc.conf},
and the host configuration files are now expected to be in @file{@value{sysconfdir}/tinc/hosts/}.
2000-03-26 00:33:07 +00:00
But it is highly recommended that you use this feature of tinc, because
2000-11-30 23:39:55 +00:00
it will be so much clearer whom your daemon talks to. Hence, we will
2000-03-26 00:33:07 +00:00
assume that you use it.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node How connections work
2000-03-26 00:33:07 +00:00
@section How connections work
2001-05-24 20:24:12 +00:00
When tinc starts up, it parses the command-line options and then
2002-09-15 22:19:38 +00:00
reads in the configuration file tinc.conf.
If it sees one or more `ConnectTo' values pointing to other tinc daemons in that file,
it will try to connect to those other daemons.
2001-05-24 20:24:12 +00:00
Whether this succeeds or not and whether `ConnectTo' is specified or not,
tinc will listen for incoming connection from other deamons.
If you did specify a `ConnectTo' value and the other side is not responding,
tinc will keep retrying.
This means that once started, tinc will stay running until you tell it to stop,
and failures to connect to other tinc daemons will not stop your tinc daemon
for trying again later.
2002-09-15 22:19:38 +00:00
This means you don't have to intervene if there are temporary network problems.
2001-05-24 20:24:12 +00:00
@cindex client
@cindex server
There is no real distinction between a server and a client in tinc.
If you wish, you can view a tinc daemon without a `ConnectTo' value as a server,
and one which does specify such a value as a client.
2002-09-15 22:19:38 +00:00
It does not matter if two tinc daemons have a `ConnectTo' value pointing to each other however.
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Configuration files
2001-05-24 20:24:12 +00:00
@section Configuration files
2000-03-26 00:33:07 +00:00
The actual configuration of the daemon is done in the file
2003-08-09 00:53:22 +00:00
@file{@value{sysconfdir}/tinc/@var{netname}/tinc.conf} and at least one other file in the directory
@file{@value{sysconfdir}/tinc/@var{netname}/hosts/}.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
These file consists of comments (lines started with a #) or assignments
2000-03-26 00:33:07 +00:00
in the form of
@example
Variable = Value.
@end example
The variable names are case insensitive, and any spaces, tabs, newlines
2000-11-30 23:39:55 +00:00
and carriage returns are ignored. Note: it is not required that you put
2000-03-26 00:33:07 +00:00
in the `=' sign, but doing so improves readability. If you leave it
out, remember to replace it with at least one space character.
2000-12-05 08:54:22 +00:00
In this section all valid variables are listed in alphabetical order.
2001-05-25 10:06:13 +00:00
The default value is given between parentheses,
2003-08-09 00:53:22 +00:00
other comments are between square brackets.
2000-12-05 08:54:22 +00:00
2000-03-26 00:33:07 +00:00
@menu
2001-05-24 20:24:12 +00:00
* Main configuration variables::
* Host configuration variables::
2003-08-09 00:53:22 +00:00
* Scripts::
2001-05-24 20:24:12 +00:00
* How to configure::
2000-03-26 00:33:07 +00:00
@end menu
2000-12-05 08:54:22 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Main configuration variables
2000-12-05 08:54:22 +00:00
@subsection Main configuration variables
2000-03-26 00:33:07 +00:00
@table @asis
2002-02-18 16:25:19 +00:00
@cindex AddressFamily
2003-10-09 21:33:15 +00:00
@item AddressFamily = <ipv4|ipv6|any> (any)
2002-02-18 16:25:19 +00:00
This option affects the address family of listening and outgoing sockets.
2003-10-09 21:33:15 +00:00
If any is selected, then depending on the operating system
2002-03-01 13:38:02 +00:00
both IPv4 and IPv6 or just IPv6 listening sockets will be created.
2002-10-07 07:32:31 +00:00
@cindex BindToAddress
2003-10-09 21:33:15 +00:00
@item BindToAddress = <@var{address}> [experimental]
2002-10-07 07:32:31 +00:00
If your computer has more than one IPv4 or IPv6 address, tinc
will by default listen on all of them for incoming connections.
It is possible to bind only to a single address with this variable.
This option may not work on all platforms.
2002-02-10 21:57:54 +00:00
@cindex BindToInterface
2003-10-09 21:33:15 +00:00
@item BindToInterface = <@var{interface}> [experimental]
2002-02-10 21:57:54 +00:00
If you have more than one network interface in your computer, tinc will
by default listen on all of them for incoming connections. It is
possible to bind tinc to a single interface like eth0 or ppp0 with this
variable.
This option may not work on all platforms.
2001-05-24 20:24:12 +00:00
@cindex ConnectTo
2003-10-09 21:33:15 +00:00
@item ConnectTo = <@var{name}>
2002-07-16 13:18:27 +00:00
Specifies which other tinc daemon to connect to on startup.
Multiple ConnectTo variables may be specified,
in which case outgoing connections to each specified tinc daemon are made.
The names should be known to this tinc daemon
(i.e., there should be a host configuration file for the name on the ConnectTo line).
If you don't specify a host with ConnectTo,
tinc won't try to connect to other daemons at all,
and will instead just listen for incoming connections.
2000-08-18 14:45:38 +00:00
2002-02-10 21:57:54 +00:00
@cindex Device
2003-10-09 21:33:15 +00:00
@item Device = <@var{device}> (@file{/dev/tap0}, @file{/dev/net/tun} or other depending on platform)
2003-08-09 00:53:22 +00:00
The virtual network device to use.
2003-10-09 21:33:15 +00:00
Tinc will automatically detect what kind of device it is.
2003-08-09 00:53:22 +00:00
Note that you can only use one device per daemon.
Under Windows, use @var{Interface} instead of @var{Device}.
Note that you can only use one device per daemon.
See also @ref{Device files}.
2002-02-10 21:57:54 +00:00
2008-12-22 21:29:21 +00:00
@cindex DeviceType
@item DeviceType = <tun|tunnohead|tunifhead|tap> (only supported on BSD platforms)
The type of the virtual network device.
Tinc will normally automatically select the right type, and this option should not be used.
However, in case tinc does not seem to correctly interpret packets received from the virtual network device,
using this option might help.
@table @asis
@item tun
Set type to tun.
Depending on the platform, this can either be with or without an address family header (see below).
@cindex tunnohead
@item tunnohead
Set type to tun without an address family header.
Tinc will expect packets read from the virtual network device to start with an IP header.
On some platforms IPv6 packets cannot be read from or written to the device in this mode.
@cindex tunifhead
@item tunifhead
Set type to tun with an address family header.
Tinc will expect packets read from the virtual network device
to start with a four byte header containing the address family,
followed by an IP header.
This mode should support both IPv4 and IPv6 packets.
@item tap
Set type to tap.
Tinc will expect packets read from the virtual network device
to start with an Ethernet header.
@end table
2006-11-11 20:37:58 +00:00
@cindex GraphDumpFile
@item GraphDumpFile = <@var{filename}> [experimental]
If this option is present,
tinc will dump the current network graph to the file @var{filename}
every minute, unless there were no changes to the graph.
The file is in a format that can be read by graphviz tools.
If @var{filename} starts with a pipe symbol |,
then the rest of the filename is interpreted as a shell command
that is executed, the graph is then sent to stdin.
2001-05-24 20:24:12 +00:00
@cindex Hostnames
2003-10-09 21:33:15 +00:00
@item Hostnames = <yes|no> (no)
2000-12-05 08:54:22 +00:00
This option selects whether IP addresses (both real and on the VPN)
should be resolved. Since DNS lookups are blocking, it might affect
tinc's efficiency, even stopping the daemon for a few seconds everytime
it does a lookup if your DNS server is not responding.
This does not affect resolving hostnames to IP addresses from the
configuration file.
2001-05-24 20:24:12 +00:00
@cindex Interface
2003-10-09 21:33:15 +00:00
@item Interface = <@var{interface}>
2002-02-10 21:57:54 +00:00
Defines the name of the interface corresponding to the virtual network device.
2003-08-09 00:53:22 +00:00
Depending on the operating system and the type of device this may or may not actually set the name of the interface.
Under Windows, this variable is used to select which network interface will be used.
If you specified a Device, this variable is almost always already correctly set.
2000-12-05 08:54:22 +00:00
2002-02-10 21:57:54 +00:00
@cindex Mode
2003-10-09 21:33:15 +00:00
@item Mode = <router|switch|hub> (router)
2002-02-10 21:57:54 +00:00
This option selects the way packets are routed to other daemons.
@table @asis
@cindex router
@item router
In this mode Subnet
variables in the host configuration files will be used to form a routing table.
Only unicast packets of routable protocols (IPv4 and IPv6) are supported in this mode.
2003-07-30 09:22:29 +00:00
This is the default mode, and unless you really know you need another mode, don't change it.
2002-02-10 21:57:54 +00:00
@cindex switch
@item switch
In this mode the MAC addresses of the packets on the VPN will be used to
2002-03-01 14:25:10 +00:00
dynamically create a routing table just like an Ethernet switch does.
Unicast, multicast and broadcast packets of every protocol that runs over Ethernet are supported in this mode
2002-02-10 21:57:54 +00:00
at the cost of frequent broadcast ARP requests and routing table updates.
2003-07-30 09:22:29 +00:00
This mode is primarily useful if you want to bridge Ethernet segments.
2002-02-10 21:57:54 +00:00
@cindex hub
@item hub
2002-03-01 14:25:10 +00:00
This mode is almost the same as the switch mode, but instead
every packet will be broadcast to the other daemons
while no routing table is managed.
2002-02-10 21:57:54 +00:00
@end table
2000-08-18 14:45:38 +00:00
2001-05-24 20:24:12 +00:00
@cindex KeyExpire
2003-10-09 21:33:15 +00:00
@item KeyExpire = <@var{seconds}> (3600)
2001-01-17 01:40:46 +00:00
This option controls the time the encryption keys used to encrypt the data
are valid. It is common practice to change keys at regular intervals to
make it even harder for crackers, even though it is thought to be nearly
impossible to crack a single key.
2002-03-01 14:25:10 +00:00
@cindex MACExpire
2003-10-09 21:33:15 +00:00
@item MACExpire = <@var{seconds}> (600)
2002-03-01 14:25:10 +00:00
This option controls the amount of time MAC addresses are kept before they are removed.
This only has effect when Mode is set to "switch".
2001-05-24 20:24:12 +00:00
@cindex Name
2003-10-09 21:33:15 +00:00
@item Name = <@var{name}> [required]
2008-12-22 21:29:21 +00:00
This is a symbolic name for this connection.
The name should consist only of alfanumeric and underscore characters (a-z, A-Z, 0-9 and _).
2000-03-26 00:33:07 +00:00
2006-01-19 17:13:18 +00:00
@cindex PingInterval
@item PingInterval = <@var{seconds}> (60)
2000-03-26 00:33:07 +00:00
The number of seconds of inactivity that tinc will wait before sending a
2006-01-19 17:13:18 +00:00
probe to the other end.
@cindex PingTimeout
@item PingTimeout = <@var{seconds}> (5)
The number of seconds to wait for a response to pings or to allow meta
connections to block. If the other end doesn't respond within this time,
the connection is terminated, and the others will be notified of this.
2000-03-26 00:33:07 +00:00
2002-03-01 13:38:02 +00:00
@cindex PriorityInheritance
2003-10-09 21:33:15 +00:00
@item PriorityInheritance = <yes|no> (no) [experimental]
2002-03-01 13:38:02 +00:00
When this option is enabled the value of the TOS field of tunneled IPv4 packets
will be inherited by the UDP packets that are sent out.
2001-05-24 20:24:12 +00:00
@cindex PrivateKey
2003-10-09 21:33:15 +00:00
@item PrivateKey = <@var{key}> [obsolete]
2001-01-06 20:02:21 +00:00
This is the RSA private key for tinc. However, for safety reasons it is
advised to store private keys of any kind in separate files. This prevents
accidental eavesdropping if you are editting the configuration file.
2001-05-24 20:24:12 +00:00
@cindex PrivateKeyFile
2003-10-09 21:33:15 +00:00
@item PrivateKeyFile = <@var{path}> (@file{@value{sysconfdir}/tinc/@var{netname}/rsa_key.priv})
2000-12-05 08:54:22 +00:00
This is the full path name of the RSA private key file that was
2003-10-09 21:33:15 +00:00
generated by @samp{tincd --generate-keys}. It must be a full path, not a
2001-01-06 20:02:21 +00:00
relative directory.
2003-10-09 21:33:15 +00:00
Note that there must be exactly one of PrivateKey
or PrivateKeyFile
2002-02-10 21:57:54 +00:00
specified in the configuration file.
2000-03-26 00:33:07 +00:00
2009-05-28 20:51:30 +00:00
@cindex ProcessPriority
@item ProcessPriority = <low|normal|high>
When this option is used the priority of the tincd process will be adjusted.
Increasing the priority may help to reduce latency and packet loss on the VPN.
2004-11-10 21:57:04 +00:00
@cindex TunnelServer
@item TunnelServer = <yes|no> (no) [experimental]
When this option is enabled tinc will no longer forward information between other tinc daemons,
and will only allow nodes and subnets on the VPN which are present in the
@file{@value{sysconfdir}/tinc/@var{netname}/hosts/} directory.
2000-12-05 08:54:22 +00:00
@end table
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Host configuration variables
2000-12-05 08:54:22 +00:00
@subsection Host configuration variables
@table @asis
2001-05-24 20:24:12 +00:00
@cindex Address
2003-10-09 21:33:15 +00:00
@item Address = <@var{IP address}|@var{hostname}> [recommended]
2000-12-05 08:54:22 +00:00
This variable is only required if you want to connect to this host. It
must resolve to the external IP address where the host can be reached,
not the one that is internal to the VPN.
2002-02-10 21:57:54 +00:00
@cindex Cipher
2003-10-09 21:33:15 +00:00
@item Cipher = <@var{cipher}> (blowfish)
2002-02-10 21:57:54 +00:00
The symmetric cipher algorithm used to encrypt UDP packets.
Any cipher supported by OpenSSL is recognized.
2003-10-09 21:33:15 +00:00
Furthermore, specifying "none" will turn off packet encryption.
It is best to use only those ciphers which support CBC mode.
2002-02-10 21:57:54 +00:00
2002-02-11 15:59:18 +00:00
@cindex Compression
2003-10-09 21:33:15 +00:00
@item Compression = <@var{level}> (0)
2002-02-11 15:59:18 +00:00
This option sets the level of compression used for UDP packets.
2003-06-11 20:18:48 +00:00
Possible values are 0 (off), 1 (fast zlib) and any integer up to 9 (best zlib),
2003-06-12 11:08:40 +00:00
10 (fast lzo) and 11 (best lzo).
2002-02-11 15:59:18 +00:00
2002-02-10 21:57:54 +00:00
@cindex Digest
2003-10-09 21:33:15 +00:00
@item Digest = <@var{digest}> (sha1)
2002-02-10 21:57:54 +00:00
The digest algorithm used to authenticate UDP packets.
Any digest supported by OpenSSL is recognized.
Furthermore, specifying "none" will turn off packet authentication.
2001-05-24 20:24:12 +00:00
@cindex IndirectData
2003-10-09 21:33:15 +00:00
@item IndirectData = <yes|no> (no)
2000-12-05 08:54:22 +00:00
This option specifies whether other tinc daemons besides the one you
specified with ConnectTo can make a direct connection to you. This is
especially useful if you are behind a firewall and it is impossible to
make a connection from the outside to your tinc daemon. Otherwise, it
is best to leave this option out or set it to no.
2002-02-10 21:57:54 +00:00
@cindex MACLength
2003-10-09 21:33:15 +00:00
@item MACLength = <@var{bytes}> (4)
2002-02-10 21:57:54 +00:00
The length of the message authentication code used to authenticate UDP packets.
Can be anything from 0
up to the length of the digest produced by the digest algorithm.
2008-12-22 21:29:21 +00:00
@cindex PMTU
@item PMTU = <@var{mtu}> (1514)
This option controls the initial path MTU to this node.
@cindex PMTUDiscovery
@item PMTUDiscovery = <yes|no> (yes)
When this option is enabled, tinc will try to discover the path MTU to this node.
After the path MTU has been discovered, it will be enforced on the VPN.
2001-05-24 20:24:12 +00:00
@cindex Port
2003-10-09 21:33:15 +00:00
@item Port = <@var{port}> (655)
2002-09-15 22:19:38 +00:00
This is the port this tinc daemon listens on.
2003-10-09 21:33:15 +00:00
You can use decimal portnumbers or symbolic names (as listed in @file{/etc/services}).
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@cindex PublicKey
2003-10-09 21:33:15 +00:00
@item PublicKey = <@var{key}> [obsolete]
2001-01-06 20:02:21 +00:00
This is the RSA public key for this host.
2001-05-24 20:24:12 +00:00
@cindex PublicKeyFile
2003-10-09 21:33:15 +00:00
@item PublicKeyFile = <@var{path}> [obsolete]
2000-12-05 08:54:22 +00:00
This is the full path name of the RSA public key file that was generated
2003-10-09 21:33:15 +00:00
by @samp{tincd --generate-keys}. It must be a full path, not a relative
2001-01-06 20:02:21 +00:00
directory.
2001-05-24 20:24:12 +00:00
@cindex PEM format
2001-05-19 15:50:51 +00:00
From version 1.0pre4 on tinc will store the public key directly into the
host configuration file in PEM format, the above two options then are not
necessary. Either the PEM format is used, or exactly
@strong{one of the above two options} must be specified
2001-01-06 20:02:21 +00:00
in each host configuration file, if you want to be able to establish a
connection with that host.
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@cindex Subnet
2009-03-05 12:34:13 +00:00
@item Subnet = <@var{address}[/@var{prefixlength}[#@var{weight}]]>
2002-02-10 21:57:54 +00:00
The subnet which this tinc daemon will serve.
2003-10-09 21:33:15 +00:00
Tinc tries to look up which other daemon it should send a packet to by searching the appropiate subnet.
2002-02-10 21:57:54 +00:00
If the packet matches a subnet,
it will be sent to the daemon who has this subnet in his host configuration file.
Multiple subnet lines can be specified for each daemon.
Subnets can either be single MAC, IPv4 or IPv6 addresses,
in which case a subnet consisting of only that single address is assumed,
2002-04-09 11:43:29 +00:00
or they can be a IPv4 or IPv6 network address with a prefixlength.
2002-03-27 15:26:29 +00:00
Shorthand notations are not supported.
2002-02-10 21:57:54 +00:00
For example, IPv4 subnets must be in a form like 192.168.1.0/24,
where 192.168.1.0 is the network address and 24 is the number of bits set in the netmask.
Note that subnets like 192.168.1.1/24 are invalid!
2002-03-25 15:01:32 +00:00
Read a networking HOWTO/FAQ/guide if you don't understand this.
IPv6 subnets are notated like fec0:0:0:1:0:0:0:0/64.
MAC addresses are notated like 0:1a:2b:3c:4d:5e.
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@cindex CIDR notation
2004-11-10 21:57:04 +00:00
Prefixlength is the number of bits set to 1 in the netmask part; for
2000-12-05 08:54:22 +00:00
example: netmask 255.255.255.0 would become /24, 255.255.252.0 becomes
2001-01-06 20:02:21 +00:00
/22. This conforms to standard CIDR notation as described in
@uref{ftp://ftp.isi.edu/in-notes/rfc1519.txt, RFC1519}
2000-12-05 08:54:22 +00:00
2009-03-05 12:34:13 +00:00
A Subnet can be given a weight to indicate its priority over identical Subnets
owned by different nodes. The default weight is 10. Lower values indicate
higher priority. Packets will be sent to the node with the highest priority,
unless that node is not reachable, in which case the node with the next highest
priority will be tried, and so on.
2001-05-24 20:24:12 +00:00
@cindex TCPonly
2008-12-22 21:29:21 +00:00
@item TCPonly = <yes|no> (no)
2000-12-05 08:54:22 +00:00
If this variable is set to yes, then the packets are tunnelled over a
TCP connection instead of a UDP connection. This is especially useful
for those who want to run a tinc daemon from behind a masquerading
2002-03-27 15:26:29 +00:00
firewall, or if UDP packet routing is disabled somehow.
2001-05-25 10:06:13 +00:00
Setting this options also implicitly sets IndirectData.
2000-12-05 08:54:22 +00:00
@end table
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Scripts
2003-08-09 00:53:22 +00:00
@subsection Scripts
@cindex scripts
Apart from reading the server and host configuration files,
tinc can also run scripts at certain moments.
2003-10-09 21:33:15 +00:00
Under Windows (not Cygwin), the scripts should have the extension .bat.
2003-08-09 00:53:22 +00:00
@table @file
@cindex tinc-up
@item @value{sysconfdir}/tinc/@var{netname}/tinc-up
This is the most important script.
If it is present it will be executed right after the tinc daemon has been
started and has connected to the virtual network device.
It should be used to set up the corresponding network interface,
but can also be used to start other things.
Under Windows you can use the Network Connections control panel instead of creating this script.
@cindex tinc-down
@item @value{sysconfdir}/tinc/@var{netname}/tinc-down
This script is started right before the tinc daemon quits.
@item @value{sysconfdir}/tinc/@var{netname}/hosts/@var{host}-up
This script is started when the tinc daemon with name @var{host} becomes reachable.
@item @value{sysconfdir}/tinc/@var{netname}/hosts/@var{host}-down
This script is started when the tinc daemon with name @var{host} becomes unreachable.
2005-05-04 16:53:11 +00:00
2006-06-12 21:45:39 +00:00
@item @value{sysconfdir}/tinc/@var{netname}/host-up
This script is started when any host becomes reachable.
@item @value{sysconfdir}/tinc/@var{netname}/host-down
This script is started when any host becomes unreachable.
2005-05-04 16:53:11 +00:00
@item @value{sysconfdir}/tinc/@var{netname}/subnet-up
This script is started when a Subnet becomes reachable.
The Subnet and the node it belongs to are passed in environment variables.
@item @value{sysconfdir}/tinc/@var{netname}/subnet-down
This script is started when a Subnet becomes unreachable.
2003-08-09 00:53:22 +00:00
@end table
@cindex environment variables
The scripts are started without command line arguments,
but can make use of certain environment variables.
Under UNIX like operating systems the names of environment variables must be preceded by a $ in scripts.
Under Windows, in @file{.bat} files, they have to be put between % signs.
@table @env
@cindex NETNAME
@item NETNAME
If a netname was specified, this environment variable contains it.
@cindex NAME
@item NAME
Contains the name of this tinc daemon.
@cindex DEVICE
@item DEVICE
Contains the name of the virtual network device that tinc uses.
@cindex INTERFACE
@item INTERFACE
Contains the name of the virtual network interface that tinc uses.
This should be used for commands like ifconfig.
@cindex NODE
@item NODE
When a host becomes (un)reachable, this is set to its name.
2005-05-04 16:53:11 +00:00
If a subnet becomes (un)reachable, this is set to the owner of that subnet.
2003-08-09 00:53:22 +00:00
@cindex REMOTEADDRESS
@item REMOTEADDRESS
When a host becomes (un)reachable, this is set to its real address.
@cindex REMOTEPORT
@item REMOTEPORT
When a host becomes (un)reachable,
this is set to the port number it uses for communication with other tinc daemons.
2005-05-04 16:53:11 +00:00
@cindex SUBNET
@item SUBNET
When a subnet becomes (un)reachable, this is set to the subnet.
2003-08-09 00:53:22 +00:00
@end table
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node How to configure
2000-12-05 08:54:22 +00:00
@subsection How to configure
2001-05-24 20:24:12 +00:00
@subsubheading Step 1. Creating the main configuration file
2000-12-05 08:54:22 +00:00
2003-08-09 00:53:22 +00:00
The main configuration file will be called @file{@value{sysconfdir}/tinc/@var{netname}/tinc.conf}.
2001-05-24 20:24:12 +00:00
Adapt the following example to create a basic configuration file:
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@example
2003-08-09 00:53:22 +00:00
Name = @var{yourname}
Device = @file{/dev/tap0}
2001-05-24 20:24:12 +00:00
@end example
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
Then, if you know to which other tinc daemon(s) yours is going to connect,
add `ConnectTo' values.
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@subsubheading Step 2. Creating your host configuration file
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
If you added a line containing `Name = yourname' in the main configuarion file,
2003-08-09 00:53:22 +00:00
you will need to create a host configuration file @file{@value{sysconfdir}/tinc/@var{netname}/hosts/yourname}.
2001-05-24 20:24:12 +00:00
Adapt the following example to create a host configuration file:
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@example
2003-08-09 00:53:22 +00:00
Address = your.real.hostname.org
Subnet = 192.168.1.0/24
2001-05-24 20:24:12 +00:00
@end example
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
You can also use an IP address instead of a hostname.
The `Subnet' specifies the address range that is local for @emph{your part of the VPN only}.
If you have multiple address ranges you can specify more than one `Subnet'.
You might also need to add a `Port' if you want your tinc daemon to run on a different port number than the default (655).
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Generating keypairs
2001-05-24 20:24:12 +00:00
@section Generating keypairs
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@cindex key generation
Now that you have already created the main configuration file and your host configuration file,
you can easily create a public/private keypair by entering the following command:
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
@example
2003-08-09 00:53:22 +00:00
tincd -n @var{netname} -K
2001-05-24 20:24:12 +00:00
@end example
2000-12-05 08:54:22 +00:00
2003-10-09 21:33:15 +00:00
Tinc will generate a public and a private key and ask you where to put them.
2001-05-24 20:24:12 +00:00
Just press enter to accept the defaults.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Network interfaces
2001-05-24 20:24:12 +00:00
@section Network interfaces
2000-12-05 08:54:22 +00:00
2001-05-24 20:24:12 +00:00
Before tinc can start transmitting data over the tunnel, it must
2002-02-10 21:57:54 +00:00
set up the virtual network interface.
2001-05-24 20:24:12 +00:00
First, decide which IP addresses you want to have associated with these
devices, and what network mask they must have.
2003-10-09 21:33:15 +00:00
Tinc will open a virtual network device (@file{/dev/tun}, @file{/dev/tap0} or similar),
which will also create a network interface called something like @samp{tun0}, @samp{tap0}.
If you are using the Linux tun/tap driver, the network interface will by default have the same name as the @var{netname}.
Under Windows you can change the name of the network interface from the Network Connections control panel.
2001-05-24 20:24:12 +00:00
@cindex tinc-up
2002-02-10 21:57:54 +00:00
You can configure the network interface by putting ordinary ifconfig, route, and other commands
2003-10-09 21:33:15 +00:00
to a script named @file{@value{sysconfdir}/tinc/@var{netname}/tinc-up}.
When tinc starts, this script will be executed. When tinc exits, it will execute the script named
2003-08-09 00:53:22 +00:00
@file{@value{sysconfdir}/tinc/@var{netname}/tinc-down}, but normally you don't need to create that script.
2001-05-24 20:24:12 +00:00
2002-02-10 21:57:54 +00:00
An example @file{tinc-up} script:
2001-05-24 20:24:12 +00:00
@example
#!/bin/sh
2002-02-10 21:57:54 +00:00
ifconfig $INTERFACE 192.168.1.1 netmask 255.255.0.0
2001-05-24 20:24:12 +00:00
@end example
2003-06-11 20:18:48 +00:00
This script gives the interface an IP address and a netmask.
2001-05-24 20:24:12 +00:00
The kernel will also automatically add a route to this interface, so normally you don't need
to add route commands to the @file{tinc-up} script.
The kernel will also bring the interface up after this command.
@cindex netmask
The netmask is the mask of the @emph{entire} VPN network, not just your
own subnet.
2003-10-09 21:33:15 +00:00
The exact syntax of the ifconfig and route commands differs from platform to platform.
You can look up the commands for setting addresses and adding routes in @ref{Platform specific information},
but it is best to consult the manpages of those utilities on your platform.
2000-08-18 14:45:38 +00:00
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Example configuration
2001-05-24 20:24:12 +00:00
@section Example configuration
2000-03-26 00:33:07 +00:00
2000-09-27 20:32:29 +00:00
2000-12-05 08:54:22 +00:00
@cindex example
2001-05-19 15:50:51 +00:00
Imagine the following situation. Branch A of our example `company' wants to connect
2001-05-24 20:24:12 +00:00
three branch offices in B, C and D using the Internet. All four offices
have a 24/7 connection to the Internet.
2000-03-26 00:33:07 +00:00
2000-11-30 23:39:55 +00:00
A is going to serve as the center of the network. B and C will connect
to A, and D will connect to C. Each office will be assigned their own IP
2000-03-26 00:33:07 +00:00
network, 10.x.0.0.
@example
A: net 10.1.0.0 mask 255.255.0.0 gateway 10.1.54.1 internet IP 1.2.3.4
B: net 10.2.0.0 mask 255.255.0.0 gateway 10.2.1.12 internet IP 2.3.4.5
C: net 10.3.0.0 mask 255.255.0.0 gateway 10.3.69.254 internet IP 3.4.5.6
D: net 10.4.0.0 mask 255.255.0.0 gateway 10.4.3.32 internet IP 4.5.6.7
@end example
2003-10-09 21:33:15 +00:00
Here, ``gateway'' is the VPN IP address of the machine that is running the
tincd, and ``internet IP'' is the IP address of the firewall, which does not
need to run tincd, but it must do a port forwarding of TCP and UDP on port
2000-04-25 01:45:34 +00:00
655 (unless otherwise configured).
2000-03-26 00:33:07 +00:00
In this example, it is assumed that eth0 is the interface that points to
2000-12-05 08:54:22 +00:00
the inner (physical) LAN of the office, although this could also be the
2001-05-24 20:24:12 +00:00
same as the interface that leads to the Internet. The configuration of
2000-12-05 08:54:22 +00:00
the real interface is also shown as a comment, to give you an idea of
2001-05-19 15:50:51 +00:00
how these example host is set up. All branches use the netname `company'
for this particular VPN.
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@subsubheading For Branch A
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@emph{BranchA} would be configured like this:
2003-08-08 14:07:12 +00:00
In @file{@value{sysconfdir}/tinc/company/tinc-up}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
# Real interface of internal network:
2003-10-09 21:33:15 +00:00
# ifconfig eth0 10.1.54.1 netmask 255.255.0.0
2001-05-19 15:50:51 +00:00
2003-06-11 20:18:48 +00:00
ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0
2000-03-26 00:33:07 +00:00
@end example
2003-08-08 14:07:12 +00:00
and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
Name = BranchA
2002-02-10 21:57:54 +00:00
Device = /dev/tap0
2000-03-26 00:33:07 +00:00
@end example
2003-10-09 21:33:15 +00:00
On all hosts, @file{@value{sysconfdir}/tinc/company/hosts/BranchA} contains:
2000-12-05 08:54:22 +00:00
@example
Subnet = 10.1.0.0/16
Address = 1.2.3.4
2001-05-19 15:50:51 +00:00
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
2000-12-05 08:54:22 +00:00
@end example
2003-06-11 20:18:48 +00:00
Note that the IP addresses of eth0 and tap0 are the same.
This is quite possible, if you make sure that the netmasks of the interfaces are different.
It is in fact recommended to give give both real internal network interfaces and tap interfaces the same IP address,
since that will make things a lot easier to remember and set up.
2000-12-05 08:54:22 +00:00
2001-05-19 15:50:51 +00:00
@subsubheading For Branch B
2003-08-08 14:07:12 +00:00
In @file{@value{sysconfdir}/tinc/company/tinc-up}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
# Real interface of internal network:
2003-10-09 21:33:15 +00:00
# ifconfig eth0 10.2.43.8 netmask 255.255.0.0
2001-05-19 15:50:51 +00:00
2003-06-11 20:18:48 +00:00
ifconfig $INTERFACE 10.2.1.12 netmask 255.0.0.0
2000-03-26 00:33:07 +00:00
@end example
2003-08-08 14:07:12 +00:00
and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
Name = BranchB
ConnectTo = BranchA
2000-03-26 00:33:07 +00:00
@end example
Note here that the internal address (on eth0) doesn't have to be the
2000-11-30 23:39:55 +00:00
same as on the tap0 device. Also, ConnectTo is given so that no-one can
2000-03-26 00:33:07 +00:00
connect to this node.
2003-08-08 14:07:12 +00:00
On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchB}:
2000-12-05 08:54:22 +00:00
@example
Subnet = 10.2.0.0/16
Address = 2.3.4.5
2001-05-19 15:50:51 +00:00
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
2000-12-05 08:54:22 +00:00
@end example
2001-05-19 15:50:51 +00:00
@subsubheading For Branch C
2003-08-08 14:07:12 +00:00
In @file{@value{sysconfdir}/tinc/company/tinc-up}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
# Real interface of internal network:
2003-10-09 21:33:15 +00:00
# ifconfig eth0 10.3.69.254 netmask 255.255.0.0
2001-05-19 15:50:51 +00:00
2003-06-11 20:18:48 +00:00
ifconfig $INTERFACE 10.3.69.254 netmask 255.0.0.0
2000-03-26 00:33:07 +00:00
@end example
2003-08-08 14:07:12 +00:00
and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
Name = BranchC
ConnectTo = BranchA
2002-02-10 21:57:54 +00:00
Device = /dev/tap1
2000-03-26 00:33:07 +00:00
@end example
C already has another daemon that runs on port 655, so they have to
2001-05-19 15:50:51 +00:00
reserve another port for tinc. It knows the portnumber it has to listen on
from it's own host configuration file.
2000-12-05 08:54:22 +00:00
2003-08-08 14:07:12 +00:00
On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchC}:
2000-12-05 08:54:22 +00:00
@example
2001-05-19 15:50:51 +00:00
Address = 3.4.5.6
2000-12-05 08:54:22 +00:00
Subnet = 10.3.0.0/16
Port = 2000
2001-05-19 15:50:51 +00:00
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
2000-12-05 08:54:22 +00:00
@end example
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@subsubheading For Branch D
2003-08-08 14:07:12 +00:00
In @file{@value{sysconfdir}/tinc/company/tinc-up}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
# Real interface of internal network:
2003-10-09 21:33:15 +00:00
# ifconfig eth0 10.4.3.32 netmask 255.255.0.0
2001-05-19 15:50:51 +00:00
2003-06-11 20:18:48 +00:00
ifconfig $INTERFACE 10.4.3.32 netmask 255.0.0.0
2000-03-26 00:33:07 +00:00
@end example
2003-08-08 14:07:12 +00:00
and in @file{@value{sysconfdir}/tinc/company/tinc.conf}:
2000-03-26 00:33:07 +00:00
@example
2001-05-19 15:50:51 +00:00
Name = BranchD
ConnectTo = BranchC
2002-09-15 22:19:38 +00:00
Device = /dev/net/tun
2000-03-26 00:33:07 +00:00
@end example
D will be connecting to C, which has a tincd running for this network on
2001-05-19 15:50:51 +00:00
port 2000. It knows the port number from the host configuration file.
2002-02-10 21:57:54 +00:00
Also note that since D uses the tun/tap driver, the network interface
2001-05-24 20:24:12 +00:00
will not be called `tun' or `tap0' or something like that, but will
have the same name as netname.
2000-03-26 00:33:07 +00:00
2003-08-08 14:07:12 +00:00
On all hosts, in @file{@value{sysconfdir}/tinc/company/hosts/BranchD}:
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@example
Subnet = 10.4.0.0/16
Address = 4.5.6.7
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
@end example
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@subsubheading Key files
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
A, B, C and D all have generated a public/private keypair with the following command:
2000-03-26 00:33:07 +00:00
2001-05-19 15:50:51 +00:00
@example
tincd -n company -K
@end example
2000-03-26 00:33:07 +00:00
2003-08-08 14:07:12 +00:00
The private key is stored in @file{@value{sysconfdir}/tinc/company/rsa_key.priv},
the public key is put into the host configuration file in the @file{@value{sysconfdir}/tinc/company/hosts/} directory.
2001-05-19 15:50:51 +00:00
During key generation, tinc automatically guesses the right filenames based on the -n option and
the Name directive in the @file{tinc.conf} file (if it is available).
2000-03-26 00:33:07 +00:00
@subsubheading Starting
2001-05-19 15:50:51 +00:00
After each branch has finished configuration and they have distributed
the host configuration files amongst them, they can start their tinc daemons.
They don't necessarily have to wait for the other branches to have started
their daemons, tinc will try connecting until they are available.
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Running tinc
2000-03-26 00:33:07 +00:00
@chapter Running tinc
2001-05-24 20:24:12 +00:00
If everything else is done, you can start tinc by typing the following command:
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@example
2003-08-09 00:53:22 +00:00
tincd -n @var{netname}
2001-05-24 20:24:12 +00:00
@end example
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@cindex daemon
2003-10-09 21:33:15 +00:00
Tinc will detach from the terminal and continue to run in the background like a good daemon.
2001-05-24 20:24:12 +00:00
If there are any problems however you can try to increase the debug level
and look in the syslog to find out what the problems are.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@menu
* Runtime options::
2004-11-10 21:57:04 +00:00
* Signals::
* Debug levels::
2003-10-09 21:33:15 +00:00
* Solving problems::
2001-05-24 20:24:12 +00:00
* Error messages::
2003-10-11 14:42:30 +00:00
* Sending bug reports::
2001-05-24 20:24:12 +00:00
@end menu
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Runtime options
2000-03-26 00:33:07 +00:00
@section Runtime options
Besides the settings in the configuration file, tinc also accepts some
command line options.
2000-12-05 08:54:22 +00:00
@cindex command line
@cindex runtime options
@cindex options
2000-03-26 00:33:07 +00:00
@c from the manpage
2003-08-09 00:53:22 +00:00
@table @option
2003-10-09 21:33:15 +00:00
@item -c, --config=@var{path}
Read configuration options from the directory @var{path}. The default is
2003-08-09 00:53:22 +00:00
@file{@value{sysconfdir}/tinc/@var{netname}/}.
2000-03-26 00:33:07 +00:00
2003-07-30 09:22:29 +00:00
@item -D, --no-detach
Don't fork and detach.
This will also disable the automatic restart mechanism for fatal errors.
2001-05-24 20:24:12 +00:00
@cindex debug level
2003-10-09 21:33:15 +00:00
@item -d, --debug=@var{level}
Set debug level to @var{level}. The higher the debug level, the more gets
2000-11-30 23:39:55 +00:00
logged. Everything goes via syslog.
2000-03-26 00:33:07 +00:00
2003-10-09 21:33:15 +00:00
@item -k, --kill[=@var{signal}]
Attempt to kill a running tincd (optionally with the specified @var{signal} instead of SIGTERM) and exit.
2002-02-10 21:57:54 +00:00
Use it in conjunction with the -n option to make sure you kill the right tinc daemon.
2003-08-02 21:55:12 +00:00
Under native Windows the optional argument is ignored,
the service will always be stopped and removed.
2002-02-10 21:57:54 +00:00
2003-10-09 21:33:15 +00:00
@item -n, --net=@var{netname}
Use configuration for net @var{netname}. @xref{Multiple networks}.
2002-02-10 21:57:54 +00:00
2003-10-09 21:33:15 +00:00
@item -K, --generate-keys[=@var{bits}]
Generate public/private keypair of @var{bits} length. If @var{bits} is not specified,
2003-07-30 09:22:29 +00:00
1024 is the default. tinc will ask where you want to store the files,
but will default to the configuration directory (you can use the -c or -n option
in combination with -K). After that, tinc will quit.
2002-02-10 21:57:54 +00:00
2002-09-15 22:19:38 +00:00
@item -L, --mlock
Lock tinc into main memory.
This will prevent sensitive data like shared private keys to be written to the system swap files/partitions.
2003-10-09 21:33:15 +00:00
@item --logfile[=@var{file}]
2003-07-30 09:22:29 +00:00
Write log entries to a file instead of to the system logging facility.
2003-10-09 21:33:15 +00:00
If @var{file} is omitted, the default is @file{@value{localstatedir}/log/tinc.@var{netname}.log}.
2003-07-30 09:22:29 +00:00
2003-10-09 21:33:15 +00:00
@item --pidfile=@var{file}
Write PID to @var{file} instead of @file{@value{localstatedir}/run/tinc.@var{netname}.pid}.
2003-07-30 09:22:29 +00:00
@item --bypass-security
Disables encryption and authentication.
Only useful for debugging.
2009-05-18 12:25:41 +00:00
@item -R, --chroot
Change process root directory to the directory where the config file is
located (@file{@value{sysconfdir}/tinc/@var{netname}/} as determined by
-n/--net option or as given by -c/--config option), for added security.
The chroot is performed after all the initialization is done, after
writing pid files and opening network sockets.
Note that this option alone does not do any good without -U/--user, below.
Note also that tinc can't run scripts anymore (such as tinc-down or host-up),
unless it's setup to be runnable inside chroot environment.
@item -U, --user=@var{user}
Switch to the given @var{user} after initialization, at the same time as
chroot is performed (see --chroot above). With this option tinc drops
privileges, for added security.
2003-07-30 09:22:29 +00:00
@item --help
Display a short reminder of these runtime options and terminate.
2000-03-26 00:33:07 +00:00
@item --version
Output version information and exit.
@end table
2004-11-10 21:57:04 +00:00
@c ==================================================================
@node Signals
@section Signals
@cindex signals
You can also send the following signals to a running tincd process:
@c from the manpage
@table @samp
@item ALRM
Forces tinc to try to connect to all uplinks immediately.
Usually tinc attempts to do this itself,
but increases the time it waits between the attempts each time it failed,
and if tinc didn't succeed to connect to an uplink the first time after it started,
it defaults to the maximum time of 15 minutes.
@item HUP
Partially rereads configuration files.
Connections to hosts whose host config file are removed are closed.
New outgoing connections specified in @file{tinc.conf} will be made.
@item INT
Temporarily increases debug level to 5.
Send this signal again to revert to the original level.
@item USR1
Dumps the connection list to syslog.
@item USR2
Dumps virtual network device statistics, all known nodes, edges and subnets to syslog.
@item WINCH
Purges all information remembered about unreachable nodes.
@end table
@c ==================================================================
@node Debug levels
@section Debug levels
@cindex debug levels
The tinc daemon can send a lot of messages to the syslog.
The higher the debug level, the more messages it will log.
Each level inherits all messages of the previous level:
@c from the manpage
@table @samp
@item 0
This will log a message indicating tinc has started along with a version number.
It will also log any serious error.
@item 1
This will log all connections that are made with other tinc daemons.
@item 2
This will log status and error messages from scripts and other tinc daemons.
@item 3
This will log all requests that are exchanged with other tinc daemons. These include
authentication, key exchange and connection list updates.
@item 4
This will log a copy of everything received on the meta socket.
@item 5
This will log all network traffic over the virtual private network.
@end table
2003-10-09 21:33:15 +00:00
@c ==================================================================
@node Solving problems
@section Solving problems
If tinc starts without problems, but if the VPN doesn't work, you will have to find the cause of the problem.
The first thing to do is to start tinc with a high debug level in the foreground,
so you can directly see everything tinc logs:
@example
tincd -n @var{netname} -d5 -D
@end example
If tinc does not log any error messages, then you might want to check the following things:
@itemize
@item @file{tinc-up} script
Does this script contain the right commands?
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.
@item Subnet
Does the Subnet (or Subnets) in the host configuration file of this host match the portion of the VPN that belongs to this host?
@item Firewalls and NATs
Do you have a firewall or a NAT device (a masquerading firewall or perhaps an ADSL router that performs masquerading)?
If so, check that it allows TCP and UDP traffic on port 655.
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.
You can add @samp{TCPOnly = yes} to your host config file to force tinc to only use a single TCP connection,
this works through most firewalls and NATs.
@end itemize
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Error messages
2000-12-05 08:54:22 +00:00
@section Error messages
2003-10-09 21:33:15 +00:00
What follows is a list of the most common error messages you might find in the logs.
Some of them will only be visible if the debug level is high enough.
2000-12-05 08:54:22 +00:00
2003-10-09 21:33:15 +00:00
@table @samp
2000-12-05 08:54:22 +00:00
@item Could not open /dev/tap0: No such device
2001-05-24 20:24:12 +00:00
@itemize
@item You forgot to `modprobe netlink_dev' or `modprobe ethertap'.
@item You forgot to compile `Netlink device emulation' in the kernel.
@end itemize
2000-12-05 08:54:22 +00:00
2002-09-15 22:19:38 +00:00
@item Can't write to /dev/net/tun: No such device
2001-05-24 20:24:12 +00:00
@itemize
@item You forgot to `modprobe tun'.
@item You forgot to compile `Universal TUN/TAP driver' in the kernel.
2003-10-09 21:33:15 +00:00
@item The tun device is located somewhere else in @file{/dev/}.
@end itemize
@item Network address and prefix length do not match!
@itemize
@item The Subnet field must contain a @emph{network} address, trailing bits should be 0.
@item If you only want to use one IP address, set the netmask to /32.
@end itemize
@item Error reading RSA key file `rsa_key.priv': No such file or directory
@itemize
@item You forgot to create a public/private keypair.
@item Specify the complete pathname to the private key file with the @samp{PrivateKeyFile} option.
@end itemize
@item Warning: insecure file permissions for RSA private key file `rsa_key.priv'!
@itemize
@item The private key file is readable by users other than root.
Use chmod to correct the file permissions.
@end itemize
@item Creating metasocket failed: Address family not supported
@itemize
@item By default tinc tries to create both IPv4 and IPv6 sockets.
On some platforms this might not be implemented.
If the logs show @samp{Ready} later on, then at least one metasocket was created,
and you can ignore this message.
You can add @samp{AddressFamily = ipv4} to @file{tinc.conf} to prevent this from happening.
@end itemize
@item Cannot route packet: unknown IPv4 destination 1.2.3.4
@itemize
@item You try to send traffic to a host on the VPN for which no Subnet is known.
@item If it is a broadcast address (ending in .255), it probably is a samba server or a Windows host sending broadcast packets.
You can ignore it.
@end itemize
@item Cannot route packet: ARP request for unknown address 1.2.3.4
@itemize
@item You try to send traffic to a host on the VPN for which no Subnet is known.
2001-05-24 20:24:12 +00:00
@end itemize
2000-12-05 08:54:22 +00:00
@item Packet with destination 1.2.3.4 is looping back to us!
2001-05-24 20:24:12 +00:00
@itemize
2001-01-06 20:02:21 +00:00
@item Something is not configured right. Packets are being sent out to the
2002-02-10 21:57:54 +00:00
virtual network device, but according to the Subnet directives in your host configuration
2001-01-06 20:02:21 +00:00
file, those packets should go to your own host. Most common mistake is that
2002-04-09 11:43:29 +00:00
you have a Subnet line in your host configuration file with a prefix length which is
just as large as the prefix of the virtual network interface. The latter should in almost all
2001-01-06 20:02:21 +00:00
cases be larger. Rethink your configuration.
Note that you will only see this message if you specified a debug
2000-12-05 08:54:22 +00:00
level of 5 or higher!
2003-10-09 21:33:15 +00:00
@item Chances are that a @samp{Subnet = ...} line in the host configuration file of this tinc daemon is wrong.
2001-05-24 20:24:12 +00:00
Change it to a subnet that is accepted locally by another interface,
or if that is not the case, try changing the prefix length into /32.
@end itemize
2003-10-09 21:33:15 +00:00
@item Node foo (1.2.3.4) is not reachable
2001-05-24 20:24:12 +00:00
@itemize
2003-10-09 21:33:15 +00:00
@item Node foo does not have a connection anymore, its tinc daemon is not running or its connection to the Internet is broken.
2001-05-24 20:24:12 +00:00
@end itemize
2000-12-05 08:54:22 +00:00
2003-10-09 21:33:15 +00:00
@item Received UDP packet from unknown source 1.2.3.4 (port 12345)
2001-05-24 20:24:12 +00:00
@itemize
2003-10-09 21:33:15 +00:00
@item If you see this only sporadically, it is harmless and caused by a node sending packets using an old key.
@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.
You can add @samp{TCPOnly = yes} to host configuration files to force all VPN traffic to go over a TCP connection.
2001-05-24 20:24:12 +00:00
@end itemize
2000-12-05 08:54:22 +00:00
2003-10-09 21:33:15 +00:00
@item Got bad/bogus/unauthorized REQUEST from foo (1.2.3.4 port 12345)
2001-05-24 20:24:12 +00:00
@itemize
2003-10-09 21:33:15 +00:00
@item Node foo does not have the right public/private keypair.
Generate new keypairs and distribute them again.
@item An attacker tries to gain access to your VPN.
@item A network error caused corruption of metadata sent from foo.
2001-05-24 20:24:12 +00:00
@end itemize
2000-12-05 08:54:22 +00:00
@end table
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Sending bug reports
@section Sending bug reports
If you really can't find the cause of a problem, or if you suspect tinc is not working right,
you can send us a bugreport, see @ref{Contact information}.
Be sure to include the following information in your bugreport:
@itemize
@item A clear description of what you are trying to achieve and what the problem is.
@item What platform (operating system, version, hardware architecture) and which version of tinc you use.
@item If compiling tinc fails, a copy of @file{config.log} and the error messages you get.
@item Otherwise, a copy of @file{tinc.conf}, @file{tinc-up} and all files in the @file{hosts/} directory.
@item The output of the commands @samp{ifconfig -a} and @samp{route -n} (or @samp{netstat -rn} if that doesn't work).
@item The output of any command that fails to work as it should (like ping or traceroute).
@end itemize
@c ==================================================================
@node Technical information
2000-12-05 08:54:22 +00:00
@chapter Technical information
2001-01-17 01:40:46 +00:00
2000-03-26 00:33:07 +00:00
@menu
2001-05-25 12:45:37 +00:00
* The connection::
* The meta-protocol::
2001-05-24 20:24:12 +00:00
* Security::
2000-03-26 00:33:07 +00:00
@end menu
2000-12-05 08:54:22 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node The connection
2001-05-25 12:45:37 +00:00
@section The connection
2000-03-26 00:33:07 +00:00
2001-05-25 12:45:37 +00:00
@cindex connection
2003-10-09 21:33:15 +00:00
Tinc is a daemon that takes VPN data and transmit that to another host
2000-03-26 00:33:07 +00:00
computer over the existing Internet infrastructure.
@menu
2001-05-25 12:45:37 +00:00
* The UDP tunnel::
* The meta-connection::
2000-03-26 00:33:07 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node The UDP tunnel
2001-05-25 12:45:37 +00:00
@subsection The UDP tunnel
2000-03-26 00:33:07 +00:00
2002-02-10 21:57:54 +00:00
@cindex virtual network device
2000-03-26 00:33:07 +00:00
@cindex frame type
The data itself is read from a character device file, the so-called
2002-02-10 21:57:54 +00:00
@emph{virtual network device}. This device is associated with a network
2000-11-30 23:39:55 +00:00
interface. Any data sent to this interface can be read from the device,
2003-06-11 20:18:48 +00:00
and any data written to the device gets sent from the interface.
There are two possible types of virtual network devices:
`tun' style, which are point-to-point devices which can only handle IPv4 and/or IPv6 packets,
and `tap' style, which are Ethernet devices and handle complete Ethernet frames.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
So when tinc reads an Ethernet frame from the device, it determines its
2002-02-10 21:57:54 +00:00
type. When tinc is in it's default routing mode, it can handle IPv4 and IPv6
2003-06-11 20:18:48 +00:00
packets. Depending on the Subnet lines, it will send the packets off to their destination IP address.
2002-02-10 21:57:54 +00:00
In the `switch' and `hub' mode, tinc will use broadcasts and MAC address discovery
to deduce the destination of the packets.
Since the latter modes only depend on the link layer information,
any protocol that runs over Ethernet is supported (for instance IPX and Appletalk).
2003-06-11 20:18:48 +00:00
However, only `tap' style devices provide this information.
2000-03-26 00:33:07 +00:00
2002-09-15 22:19:38 +00:00
After the destination has been determined,
the packet will be compressed (optionally),
a sequence number will be added to the packet,
the packet will then be encrypted
and a message authentication code will be appended.
2000-03-26 00:33:07 +00:00
@cindex encapsulating
2001-05-24 20:24:12 +00:00
@cindex UDP
2002-02-10 21:57:54 +00:00
When that is done, time has come to actually transport the
2000-11-30 23:39:55 +00:00
packet to the destination computer. We do this by sending the packet
over an UDP connection to the destination host. This is called
2000-03-26 00:33:07 +00:00
@emph{encapsulating}, the VPN packet (though now encrypted) is
encapsulated in another IP datagram.
When the destination receives this packet, the same thing happens, only
2002-02-10 21:57:54 +00:00
in reverse. So it checks the message authentication code, decrypts the contents of the UDP datagram,
checks the sequence number
and writes the decrypted information to its own virtual network device.
2000-03-26 00:33:07 +00:00
2003-06-11 20:18:48 +00:00
If the virtual network device is a `tun' device (a point-to-point tunnel),
there is no problem for the kernel to accept a packet.
However, if it is a `tap' device (this is the only available type on FreeBSD),
the destination MAC address must match that of the virtual network interface.
If tinc is in it's default routing mode, ARP does not work, so the correct destination MAC
can not be known by the sending host.
2003-10-09 21:33:15 +00:00
Tinc solves this by letting the receiving end detect the MAC address of its own virtual network interface
2002-09-15 22:19:38 +00:00
and overwriting the destination MAC address of the received packet.
In switch or hub modes ARP does work so the sender already knows the correct destination MAC address.
In those modes every interface should have a unique MAC address, so make sure they are not the same.
2003-06-11 20:18:48 +00:00
Because switch and hub modes rely on MAC addresses to function correctly,
these modes cannot be used on the following operating systems which don't have a `tap' style virtual network device:
OpenBSD, NetBSD, Darwin and Solaris.
2001-01-06 20:02:21 +00:00
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node The meta-connection
2000-03-26 00:33:07 +00:00
@subsection The meta-connection
2002-09-15 22:19:38 +00:00
Having only a UDP connection available is not enough. Though suitable
2000-03-26 00:33:07 +00:00
for transmitting data, we want to be able to reliably send other
2001-05-24 20:24:12 +00:00
information, such as routing and session key information to somebody.
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@cindex TCP
2000-03-26 00:33:07 +00:00
TCP is a better alternative, because it already contains protection
against information being lost, unlike UDP.
2000-11-30 23:39:55 +00:00
So we establish two connections. One for the encrypted VPN data, and one
for other information, the meta-data. Hence, we call the second
connection the meta-connection. We can now be sure that the
2000-03-26 00:33:07 +00:00
meta-information doesn't get lost on the way to another computer.
@cindex data-protocol
@cindex meta-protocol
Like with any communication, we must have a protocol, so that everybody
2000-12-05 08:54:22 +00:00
knows what everything stands for, and how she should react. Because we
2000-11-30 23:39:55 +00:00
have two connections, we also have two protocols. The protocol used for
2000-03-26 00:33:07 +00:00
the UDP data is the ``data-protocol,'' the other one is the
``meta-protocol.''
2000-05-14 12:22:42 +00:00
The reason we don't use TCP for both protocols is that UDP is much
2000-11-30 23:39:55 +00:00
better for encapsulation, even while it is less reliable. The real
2000-05-14 12:22:42 +00:00
problem is that when TCP would be used to encapsulate a TCP stream
that's on the private network, for every packet sent there would be
2001-05-24 20:24:12 +00:00
three ACKs sent instead of just one. Furthermore, if there would be
2000-05-14 12:22:42 +00:00
a timeout, both TCP streams would sense the timeout, and both would
2001-05-24 20:24:12 +00:00
start re-sending packets.
2000-03-26 00:33:07 +00:00
2001-05-25 12:45:37 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node The meta-protocol
2001-05-25 12:45:37 +00:00
@section The meta-protocol
The meta protocol is used to tie all tinc daemons together, and
exchange information about which tinc daemon serves which virtual
subnet.
The meta protocol consists of requests that can be sent to the other
side. Each request has a unique number and several parameters. All
requests are represented in the standard ASCII character set. It is
possible to use tools such as telnet or netcat to connect to a tinc
2002-09-15 22:19:38 +00:00
daemon started with the --bypass-security option
and to read and write requests by hand, provided that one
2001-05-25 12:45:37 +00:00
understands the numeric codes sent.
The authentication scheme is described in @ref{Authentication protocol}. After a
2002-02-10 21:57:54 +00:00
successful authentication, the server and the client will exchange all the
2001-05-25 12:45:37 +00:00
information about other tinc daemons and subnets they know of, so that both
sides (and all the other tinc daemons behind them) have their information
synchronised.
2002-02-10 21:57:54 +00:00
@cindex ADD_EDGE
2001-05-25 12:45:37 +00:00
@cindex ADD_SUBNET
@example
2004-11-10 21:57:04 +00:00
message
------------------------------------------------------------------
ADD_EDGE node1 node2 21.32.43.54 655 222 0
| | | | | +-> options
| | | | +----> weight
| | | +--------> UDP port of node2
| | +----------------> real address of node2
| +-------------------------> name of destination node
+-------------------------------> name of source node
ADD_SUBNET node 192.168.1.0/24
| | +--> prefixlength
| +--------> network address
+------------------> owner of this subnet
------------------------------------------------------------------
2001-05-25 12:45:37 +00:00
@end example
2002-09-15 22:19:38 +00:00
The ADD_EDGE messages are to inform other tinc daemons that a connection between
two nodes exist. The address of the destination node is available so that
VPN packets can be sent directly to that node.
The ADD_SUBNET messages inform other tinc daemons that certain subnets belong
to certain nodes. tinc will use it to determine to which node a VPN packet has
to be sent.
2002-02-10 21:57:54 +00:00
@cindex DEL_EDGE
2002-09-15 22:19:38 +00:00
@cindex DEL_SUBNET
@example
message
------------------------------------------------------------------
DEL_EDGE node1 node2
2004-11-10 21:57:04 +00:00
| +----> name of destination node
2002-09-15 22:19:38 +00:00
+----------> name of source node
DEL_SUBNET node 192.168.1.0/24
| | +--> prefixlength
| +--------> network address
+------------------> owner of this subnet
------------------------------------------------------------------
@end example
2002-02-10 21:57:54 +00:00
In case a connection between two daemons is closed or broken, DEL_EDGE messages
are sent to inform the other daemons of that fact. Each daemon will calculate a
new route to the the daemons, or mark them unreachable if there isn't any.
2001-05-25 12:45:37 +00:00
2002-09-15 22:19:38 +00:00
@cindex REQ_KEY
@cindex ANS_KEY
@cindex KEY_CHANGED
@example
message
------------------------------------------------------------------
REQ_KEY origin destination
| +--> name of the tinc daemon it wants the key from
+----------> name of the daemon that wants the key
ANS_KEY origin destination 4ae0b0a82d6e0078 91 64 4
| | \______________/ | | +--> MAC length
| | | | +-----> digest algorithm
| | | +--------> cipher algorithm
| | +--> 128 bits key
| +--> name of the daemon that wants the key
+----------> name of the daemon that uses this key
KEY_CHANGED origin
+--> daemon that has changed it's packet key
2004-11-10 21:57:04 +00:00
------------------------------------------------------------------
2002-09-15 22:19:38 +00:00
@end example
2001-05-25 12:45:37 +00:00
The keys used to encrypt VPN packets are not sent out directly. This is
because it would generate a lot of traffic on VPNs with many daemons, and
chances are that not every tinc daemon will ever send a packet to every
other daemon. Instead, if a daemon needs a key it sends a request for it
via the meta connection of the nearest hop in the direction of the
2002-09-15 22:19:38 +00:00
destination.
2001-05-25 12:45:37 +00:00
2002-09-15 22:19:38 +00:00
@cindex PING
@cindex PONG
2001-05-25 12:45:37 +00:00
@example
daemon message
2004-11-10 21:57:04 +00:00
------------------------------------------------------------------
2002-09-15 22:19:38 +00:00
origin PING
dest. PONG
2004-11-10 21:57:04 +00:00
------------------------------------------------------------------
2001-05-25 12:45:37 +00:00
@end example
There is also a mechanism to check if hosts are still alive. Since network
failures or a crash can cause a daemon to be killed without properly
shutting down the TCP connection, this is necessary to keep an up to date
connection list. PINGs are sent at regular intervals, except when there
is also some other traffic. A little bit of salt (random data) is added
with each PING and PONG message, to make sure that long sequences of PING/PONG
messages without any other traffic won't result in known plaintext.
2003-10-09 21:33:15 +00:00
This basically covers what is sent over the meta connection by tinc.
2001-05-25 12:45:37 +00:00
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Security
@section Security
2000-03-26 00:33:07 +00:00
2001-05-24 20:24:12 +00:00
@cindex TINC
2000-03-26 00:33:07 +00:00
@cindex Cabal
2003-10-09 21:33:15 +00:00
Tinc got its name from ``TINC,'' short for @emph{There Is No Cabal}; the
2001-05-24 20:24:12 +00:00
alleged Cabal was/is an organisation that was said to keep an eye on the
2000-11-30 23:39:55 +00:00
entire Internet. As this is exactly what you @emph{don't} want, we named
2000-03-26 00:33:07 +00:00
the tinc project after TINC.
@cindex SVPN
But in order to be ``immune'' to eavesdropping, you'll have to encrypt
2000-11-30 23:39:55 +00:00
your data. Because tinc is a @emph{Secure} VPN (SVPN) daemon, it does
2000-03-26 00:33:07 +00:00
exactly that: encrypt.
2003-10-09 21:33:15 +00:00
Tinc by default uses blowfish encryption with 128 bit keys in CBC mode, 32 bit
2002-03-25 15:12:09 +00:00
sequence numbers and 4 byte long message authentication codes to make sure
eavesdroppers cannot get and cannot change any information at all from the
packets they can intercept. The encryption algorithm and message authentication
algorithm can be changed in the configuration. The length of the message
authentication codes is also adjustable. The length of the key for the
2002-03-26 13:19:56 +00:00
encryption algorithm is always the default length used by OpenSSL.
2000-03-26 00:33:07 +00:00
2001-05-25 12:45:37 +00:00
@menu
* Authentication protocol::
* Encryption of network packets::
2003-10-09 21:33:15 +00:00
* Security issues::
2001-05-25 12:45:37 +00:00
@end menu
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Authentication protocol
2001-05-25 12:45:37 +00:00
@subsection Authentication protocol
2001-05-24 20:24:12 +00:00
@cindex authentication
2001-05-25 12:45:37 +00:00
A new scheme for authentication in tinc has been devised, which offers some
improvements over the protocol used in 1.0pre2 and 1.0pre3. Explanation is
below.
2002-02-10 21:57:54 +00:00
@cindex ID
@cindex META_KEY
@cindex CHALLENGE
@cindex CHAL_REPLY
@cindex ACK
2001-05-25 12:45:37 +00:00
@example
daemon message
--------------------------------------------------------------------------
client <attempts connection>
server <accepts connection>
2002-02-10 21:57:54 +00:00
client ID client 12
| +---> version
+-------> name of tinc daemon
2001-05-25 12:45:37 +00:00
2002-02-10 21:57:54 +00:00
server ID server 12
| +---> version
+-------> name of tinc daemon
2001-05-25 12:45:37 +00:00
client META_KEY 5f0823a93e35b69e...7086ec7866ce582b
\_________________________________/
+-> RSAKEYLEN bits totally random string S1,
encrypted with server's public RSA key
server META_KEY 6ab9c1640388f8f0...45d1a07f8a672630
\_________________________________/
+-> RSAKEYLEN bits totally random string S2,
encrypted with client's public RSA key
From now on:
2002-02-10 21:57:54 +00:00
- the client will symmetrically encrypt outgoing traffic using S1
- the server will symmetrically encrypt outgoing traffic using S2
2001-05-25 12:45:37 +00:00
client CHALLENGE da02add1817c1920989ba6ae2a49cecbda0
\_________________________________/
+-> CHALLEN bits totally random string H1
server CHALLENGE 57fb4b2ccd70d6bb35a64c142f47e61d57f
\_________________________________/
+-> CHALLEN bits totally random string H2
client CHAL_REPLY 816a86
+-> 160 bits SHA1 of H2
server CHAL_REPLY 928ffe
+-> 160 bits SHA1 of H1
2002-02-10 21:57:54 +00:00
After the correct challenge replies are received, both ends have proved
their identity. Further information is exchanged.
2002-09-15 22:19:38 +00:00
client ACK 655 123 0
| | +-> options
| +----> estimated weight
+--------> listening port of client
server ACK 655 321 0
| | +-> options
| +----> estimated weight
+--------> listening port of server
2001-05-25 12:45:37 +00:00
--------------------------------------------------------------------------
@end example
This new scheme has several improvements, both in efficiency and security.
First of all, the server sends exactly the same kind of messages over the wire
as the client. The previous versions of tinc first authenticated the client,
and then the server. This scheme even allows both sides to send their messages
simultaneously, there is no need to wait for the other to send something first.
This means that any calculations that need to be done upon sending or receiving
a message can also be done in parallel. This is especially important when doing
RSA encryption/decryption. Given that these calculations are the main part of
the CPU time spent for the authentication, speed is improved by a factor 2.
Second, only one RSA encrypted message is sent instead of two. This reduces the
amount of information attackers can see (and thus use for a cryptographic
attack). It also improves speed by a factor two, making the total speedup a
factor 4.
Third, and most important:
The symmetric cipher keys are exchanged first, the challenge is done
afterwards. In the previous authentication scheme, because a man-in-the-middle
could pass the challenge/chal_reply phase (by just copying the messages between
the two real tinc daemons), but no information was exchanged that was really
needed to read the rest of the messages, the challenge/chal_reply phase was of
no real use. The man-in-the-middle was only stopped by the fact that only after
the ACK messages were encrypted with the symmetric cipher. Potentially, it
could even send it's own symmetric key to the server (if it knew the server's
public key) and read some of the metadata the server would send it (it was
impossible for the mitm to read actual network packets though). The new scheme
however prevents this.
This new scheme makes sure that first of all, symmetric keys are exchanged. The
rest of the messages are then encrypted with the symmetric cipher. Then, each
side can only read received messages if they have their private key. The
challenge is there to let the other side know that the private key is really
known, because a challenge reply can only be sent back if the challenge is
decrypted correctly, and that can only be done with knowledge of the private
key.
2003-08-02 22:01:50 +00:00
Fourth: the first thing that is sent via the symmetric cipher encrypted
2001-05-25 12:45:37 +00:00
connection is a totally random string, so that there is no known plaintext (for
an attacker) in the beginning of the encrypted stream.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Encryption of network packets
2003-10-11 14:42:30 +00:00
@subsection Encryption of network packets
2001-05-25 12:45:37 +00:00
@cindex encryption
A data packet can only be sent if the encryption key is known to both
parties, and the connection is activated. If the encryption key is not
known, a request is sent to the destination using the meta connection
2002-02-10 21:57:54 +00:00
to retrieve it. The packet is stored in a queue while waiting for the
2001-05-25 12:45:37 +00:00
key to arrive.
@cindex UDP
The UDP packet containing the network packet from the VPN has the following layout:
@example
2002-02-10 21:57:54 +00:00
... | IP header | UDP header | seqno | VPN packet | MAC | UDP trailer
\___________________/\_____/
| |
V +---> digest algorithm
2001-05-25 12:45:37 +00:00
Encrypted with symmetric cipher
@end example
2002-09-15 22:19:38 +00:00
So, the entire VPN packet is encrypted using a symmetric cipher, including a 32 bits
sequence number that is added in front of the actual VPN packet, to act as a unique
2002-02-10 21:57:54 +00:00
IV for each packet and to prevent replay attacks. A message authentication code
is added to the UDP packet to prevent alteration of packets. By default the
first 4 bytes of the digest are used for this, but this can be changed using
the MACLength configuration variable.
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Security issues
2003-10-11 14:42:30 +00:00
@subsection Security issues
2003-10-09 21:33:15 +00:00
In August 2000, we discovered the existence of a security hole in all versions
of tinc up to and including 1.0pre2. This had to do with the way we exchanged
keys. Since then, we have been working on a new authentication scheme to make
tinc as secure as possible. The current version uses the OpenSSL library and
uses strong authentication with RSA keys.
On the 29th of December 2001, Jerome Etienne posted a security analysis of tinc
1.0pre4. Due to a lack of sequence numbers and a message authentication code
for each packet, an attacker could possibly disrupt certain network services or
launch a denial of service attack by replaying intercepted packets. The current
version adds sequence numbers and message authentication codes to prevent such
attacks.
On the 15th of September 2003, Peter Gutmann posted a security analysis of tinc
1.0.1. He argues that the 32 bit sequence number used by tinc is not a good IV,
that tinc's default length of 4 bytes for the MAC is too short, and he doesn't
like tinc's use of RSA during authentication. We do not know of a security hole
in this version of tinc, but tinc's security is not as strong as TLS or IPsec.
We will address these issues in tinc 2.0.
Cryptography is a hard thing to get right. We cannot make any
guarantees. Time, review and feedback are the only things that can
prove the security of any cryptographic product. If you wish to review
tinc or give us feedback, you are stronly encouraged to do so.
@c ==================================================================
@node Platform specific information
@chapter Platform specific information
@menu
* Interface configuration::
* Routes::
@end menu
@c ==================================================================
@node Interface configuration
@section Interface configuration
When configuring an interface, one normally assigns it an address and a
netmask. The address uniquely identifies the host on the network attached to
the interface. The netmask, combined with the address, forms a subnet. It is
used to add a route to the routing table instructing the kernel to send all
packets which fall into that subnet to that interface. Because all packets for
the entire VPN should go to the virtual network interface used by tinc, the
netmask should be such that it encompasses the entire VPN.
For IPv4 addresses:
@multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
@item Linux
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item Linux iproute2
@tab @code{ip addr add} @var{address}@code{/}@var{prefixlength} @code{dev} @var{interface}
@item FreeBSD
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item OpenBSD
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item NetBSD
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item Solaris
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item Darwin (MacOS/X)
@tab @code{ifconfig} @var{interface} @var{address} @code{netmask} @var{netmask}
@item Windows
@tab @code{netsh interface ip set address} @var{interface} @code{static} @var{address} @var{netmask}
@end multitable
For IPv6 addresses:
@multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
@item Linux
@tab @code{ifconfig} @var{interface} @code{add} @var{address}@code{/}@var{prefixlength}
@item FreeBSD
@tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
@item OpenBSD
@tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
@item NetBSD
@tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
@item Solaris
2004-11-10 21:57:04 +00:00
@tab @code{ifconfig} @var{interface} @code{inet6 plumb up}
@item
@tab @code{ifconfig} @var{interface} @code{inet6 addif} @var{address} @var{address}
2003-10-09 21:33:15 +00:00
@item Darwin (MacOS/X)
@tab @code{ifconfig} @var{interface} @code{inet6} @var{address} @code{prefixlen} @var{prefixlength}
@item Windows
@tab @code{netsh interface ipv6 add address} @var{interface} @code{static} @var{address}/@var{prefixlength}
@end multitable
@c ==================================================================
@node Routes
@section Routes
In some cases it might be necessary to add more routes to the virtual network
interface. There are two ways to indicate which interface a packet should go
to, one is to use the name of the interface itself, another way is to specify
the (local) address that is assigned to that interface (@var{local_address}). The
former way is unambiguous and therefore preferable, but not all platforms
support this.
Adding routes to IPv4 subnets:
@multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
@item Linux
@tab @code{route add -net} @var{network_address} @code{netmask} @var{netmask} @var{interface}
@item Linux iproute2
@tab @code{ip route add} @var{network_address}@code{/}@var{prefixlength} @code{dev} @var{interface}
@item FreeBSD
@tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
@item OpenBSD
@tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
@item NetBSD
@tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
@item Solaris
2004-11-10 21:57:04 +00:00
@tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address} @code{-interface}
2003-10-09 21:33:15 +00:00
@item Darwin (MacOS/X)
@tab @code{route add} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
@item Windows
2004-11-10 21:57:04 +00:00
@tab @code{netsh routing ip add persistentroute} @var{network_address} @var{netmask} @var{interface} @var{local_address}
2003-10-09 21:33:15 +00:00
@end multitable
Adding routes to IPv6 subnets:
@multitable {Darwin (MacOS/X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
@item Linux
@tab @code{route add -A inet6} @var{network_address}@code{/}@var{prefixlength} @var{interface}
@item Linux iproute2
@tab @code{ip route add} @var{network_address}@code{/}@var{prefixlength} @code{dev} @var{interface}
2004-11-10 21:57:04 +00:00
@item FreeBSD
@tab @code{route add -inet6} @var{network_address}@code{/}@var{prefixlength} @var{local_address}
2003-10-09 21:33:15 +00:00
@item OpenBSD
2004-11-10 21:57:04 +00:00
@tab @code{route add -inet6} @var{network_address} @var{local_address} @code{-prefixlen} @var{prefixlength}
2003-10-09 21:33:15 +00:00
@item NetBSD
2004-11-10 21:57:04 +00:00
@tab @code{route add -inet6} @var{network_address} @var{local_address} @code{-prefixlen} @var{prefixlength}
2003-10-09 21:33:15 +00:00
@item Solaris
2004-11-10 21:57:04 +00:00
@tab @code{route add -inet6} @var{network_address}@code{/}@var{prefixlength} @var{local_address} @code{-interface}
2003-10-09 21:33:15 +00:00
@item Darwin (MacOS/X)
2004-11-10 21:57:04 +00:00
@tab ?
2003-10-09 21:33:15 +00:00
@item Windows
@tab @code{netsh interface ipv6 add route} @var{network address}/@var{prefixlength} @var{interface}
@end multitable
@c ==================================================================
@node About us
2000-03-26 00:33:07 +00:00
@chapter About us
@menu
2003-10-11 14:42:30 +00:00
* Contact information::
2001-05-24 20:24:12 +00:00
* Authors::
2000-03-26 00:33:07 +00:00
@end menu
@c ==================================================================
2003-10-11 14:42:30 +00:00
@node Contact information
2000-03-26 00:33:07 +00:00
@section Contact information
2001-05-24 20:24:12 +00:00
@cindex website
2004-03-21 14:21:22 +00:00
Tinc's website is at @url{http://www.tinc-vpn.org/},
2000-03-26 00:33:07 +00:00
this server is located in the Netherlands.
2001-05-24 20:24:12 +00:00
@cindex IRC
2003-07-30 09:22:29 +00:00
We have an IRC channel on the FreeNode and OFTC IRC networks. Connect to
2002-09-15 22:19:38 +00:00
@uref{http://www.freenode.net/, irc.freenode.net}
2003-07-30 09:22:29 +00:00
or
@uref{http://www.oftc.net/, irc.oftc.net}
2000-03-26 00:33:07 +00:00
and join channel #tinc.
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Authors
2000-03-26 00:33:07 +00:00
@section Authors
@table @asis
2009-09-24 21:42:30 +00:00
@item Ivo Timmermans (zarq)
2004-03-21 14:21:22 +00:00
@item Guus Sliepen (guus) (@email{guus@@tinc-vpn.org})
2000-03-26 00:33:07 +00:00
@end table
2000-12-05 08:54:22 +00:00
We have received a lot of valuable input from users. With their help,
tinc has become the flexible and robust tool that it is today. We have
composed a list of contributions, in the file called @file{THANKS} in
the source distribution.
2000-03-26 00:33:07 +00:00
@c ==================================================================
2003-10-09 21:33:15 +00:00
@node Concept Index
2000-03-26 00:33:07 +00:00
@unnumbered Concept Index
@c ==================================================================
@printindex cp
@c ==================================================================
@contents
@bye