--- tinc-1.0.9.orig/doc/tinc/tinc_0.html +++ tinc-1.0.9/doc/tinc/tinc_0.html @@ -0,0 +1,249 @@ + + + + + +tinc Manual: 1. Introduction + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

1. Introduction

+ +

Tinc is a Virtual Private Network (VPN) daemon that uses tunneling and +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. +The encrypted tunnels allows VPN sites to share information with each other +over the Internet without exposing any information to others. +

This document is the manual for tinc. Included are chapters on how to +configure your computer to use tinc, as well as the configuration +process of tinc itself. +

+ + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

1.1 Virtual Private Networks

+ + +

A Virtual Private Network or VPN is a network that can only be accessed +by a few elected computers that participate. This goal is achievable in +more than just one way. +

+ +

Private networks can consist of a single stand-alone Ethernet LAN. Or +even two computers hooked up using a null-modem cable. In these cases, +it is +obvious that the network is private, no one can access it from the +outside. But if your computers are linked to the Internet, the network +is not private anymore, unless one uses firewalls to block all private +traffic. But then, there is no way to send private data to trusted +computers on the other end of the Internet. +

This problem can be solved by using virtual networks. Virtual +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 +the Internet. Mostly, virtual networks appear like a singe LAN, even though +they can span the entire world. But virtual networks can't be secured +by using firewalls, because the traffic that flows through it has to go +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. +

When one introduces encryption, we can form a true VPN. Other people may +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 +through the VPN. This is what tinc was made for. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

1.2 tinc

+ + +

I really don't quite remember what got us started, but it must have been +Guus' idea. He wrote a simple implementation (about 50 lines of C) that +used the ethertap device that Linux knows of since somewhere +about kernel 2.1.60. It didn't work immediately and he improved it a +bit. At this stage, the project was still simply called "vpnd". +

Since then, a lot has changed—to say the least. +

+ +

Tinc now supports encryption, it consists of a single daemon (tincd) for +both the receiving and sending end, it has become largely +runtime-configurable—in short, it has become a full-fledged +professional package. +

+ +

Tinc also allows more than two sites to connect to eachother and form a single VPN. +Traditionally VPNs are created by making tunnels, which only have two endpoints. +Larger VPNs with more sites are created by adding more tunnels. +Tinc takes another approach: only endpoints are specified, +the software itself will take care of creating the tunnels. +This allows for easier configuration and improved scalability. +

A lot can—and will be—changed. We have a number of things that we would like to +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 +it stands, and then add more advanced features. +

Meanwhile, we're always open-minded towards new ideas. And we're +available too. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

1.3 Supported platforms

+ + +

Tinc has been verified to work under Linux, FreeBSD, OpenBSD, NetBSD, MacOS/X (Darwin), Solaris, and Windows (both natively and in a Cygwin environment), +with various hardware architectures. These are some of the platforms +that are supported by the universal tun/tap device driver or other virtual network device drivers. +Without such a driver, tinc will most +likely compile and run, but it will not be able to send or receive data +packets. +

For an up to date list of supported platforms, please check the list on +our website: +http://www.tinc-vpn.org/platforms. +

+ +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_1.html +++ tinc-1.0.9/doc/tinc/tinc_1.html @@ -0,0 +1,536 @@ + + + + + +tinc Manual: 2. Preparations + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2. Preparations

+ +

This chapter contains information on how to prepare your system to +support tinc. +

+ + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1 Configuring the kernel

+ + + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.1 Configuration of Linux kernels

+ +

For tinc to work, you need a kernel that supports the Universal tun/tap device. +Most distributions come with kernels that already support this. +Here are the options you have to turn on when configuring a new kernel: +

Code maturity level options
+[*] Prompt for development and/or incomplete code/drivers
+Network device support
+<M> Universal tun/tap device driver support
+

+ +

It's not necessary to compile this driver as a module, even if you are going to +run more than one instance of tinc. +

If you decide to build the tun/tap driver as a kernel module, add these lines +to ‘/etc/modules.conf’: +

alias char-major-10-200 tun
+

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.2 Configuration of FreeBSD kernels

+ +

For FreeBSD version 4.1 and higher, tun and tap drivers are included in the default kernel configuration. +Using tap devices is recommended. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.3 Configuration of OpenBSD kernels

+ +

For OpenBSD version 2.9 and higher, +the tun driver is included in the default kernel configuration. +There is also a kernel patch from http://diehard.n-r-g.com/stuff/openbsd/ +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. +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.4 Configuration of NetBSD kernels

+ +

For NetBSD version 1.5.2 and higher, +the tun driver is included in the default kernel configuration. +

Tunneling IPv6 may not work on NetBSD's tun device. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.5 Configuration of Solaris kernels

+ +

For Solaris 8 (SunOS 5.8) and higher, +the tun driver may or may not be included in the default kernel configuration. +If it isn't, the source can be downloaded from http://vtun.sourceforge.net/tun/. +For x86 and sparc64 architectures, precompiled versions can be found at http://www.monkey.org/~dugsong/fragroute/. +If the ‘net/if_tun.h’ header file is missing, install it from the source package. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.6 Configuration of Darwin (MacOS/X) kernels

+ +

Tinc on Darwin relies on a tunnel driver for its data acquisition from the kernel. +Tinc supports either the driver from http://www-user.rhrk.uni-kl.de/~nissler/tuntap/, +which supports both tun and tap style devices, +and also the driver from from 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: +

kmodload tunnel
+

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.1.7 Configuration of Windows

+ +

You will need to install the latest TAP-Win32 driver from OpenVPN. +You can download it from 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. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.2 Libraries

+ +

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 +having them installed, configure will give you an error message, and stop. +

+ + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.2.1 OpenSSL

+ +

For all cryptography-related functions, tinc uses the functions provided +by the OpenSSL library. +

If this library is not installed, you wil get an error when configuring +tinc for build. Support for running tinc without having OpenSSL +installed 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 OpenSSL manually, you can get the source code +from 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). +

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. +

--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)
+

+ + + +

License

+ +

The complete source code of tinc is covered by the GNU GPL version 2. +Since the license under which OpenSSL is distributed is not directly +compatible with the terms of the GNU GPL +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: +

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. +

+ +

Since the LZO library used by tinc is also covered by the GPL, +we also present the following exemption: +

Hereby I grant a special exception to the tinc VPN project +(http://www.tinc-vpn.org/) to link the LZO library with the OpenSSL library +(http://www.openssl.org). +
+
Markus F.X.J. Oberhumer +

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.2.2 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 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 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). +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

2.2.3 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 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 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). +

+ + +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_2.html +++ tinc-1.0.9/doc/tinc/tinc_2.html @@ -0,0 +1,344 @@ + + + + + +tinc Manual: 3. Installation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3. Installation

+ +

If you use Debian, you may want to install one of the +precompiled packages for your system. These packages are equipped with +system startup scripts and sample configurations. +

If you cannot use one of the precompiled packages, or you want to compile tinc +for yourself, you can use the source. The source is distributed under +the GNU General Public License (GPL). Download the source from the +download page, which has +the checksums of these files listed; you may wish to check these with +md5sum before continuing. +

Tinc comes in a convenient autoconf/automake package, which you can just +treat the same as any other package. Which is just untar it, type +`./configure' and then `make'. +More detailed instructions are in the file ‘INSTALL’, which is +included in the source distribution. +

+ + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.1 Building and installing tinc

+ +

Detailed instructions on configuring the source, building tinc and installing tinc +can be found in the file called ‘INSTALL’. +

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. +

+ + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.1.1 Darwin (MacOS/X) build environment

+ +

In order to build tinc on Darwin, you need to install the MacOS/X Developer Tools +from http://developer.apple.com/tools/macosxtools.html and +a recent version of Fink from http://fink.sourceforge.net/. +

After installation use fink to download and install the following packages: +autoconf25, automake, dlcompat, m4, openssl, zlib and lzo. +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.1.2 Cygwin (Windows) build environment

+ +

If Cygwin hasn't already been installed, install it directly from +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. +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.1.3 MinGW (Windows) build environment

+ +

You will need to install the MinGW environment from http://www.mingw.org. +

When tinc is compiled using MinGW it runs natively under Windows, +it is not necessary to keep MinGW installed. +

When detaching, tinc will install itself as a service, +which will be restarted automatically after reboots. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.2 System files

+ +

Before you can run tinc, you must make sure you have all the needed +files on your system. +

+ + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.2.1 Device files

+ +

Most operating systems nowadays come with the necessary device files by default, +or they have a mechanism to create them on demand. +

If you use Linux and do not have udev installed, +you may need to create the following device file if it does not exist: +

mknod -m 600 /dev/net/tun c 10 200
+

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

3.2.2 Other files

+ + +

‘`/etc/networks`’

+ +

You may add a line to ‘/etc/networks’ so that your VPN will get a +symbolic name. For example: +

myvpn 10.0.0.0
+

+ + +

‘`/etc/services`’

+ + +

You may add this line to ‘/etc/services’. The effect is that you +may supply a ‘tinc’ as a valid port number to some programs. The +number 655 is registered with the IANA. +

tinc            655/tcp    TINC
+tinc            655/udp    TINC
+#                          Ivo Timmermans <ivo@tinc-vpn.org>
+

+ + + + +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_3.html +++ tinc-1.0.9/doc/tinc/tinc_3.html @@ -0,0 +1,1137 @@ + + + + + +tinc Manual: 4. Configuration + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4. Configuration

+ + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.1 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? +Do you want to run tinc in router mode or switch mode? +These questions can only be answered by yourself, +you will not find the answers in this documentation. +Make sure you have an adequate understanding of networks in general. +A good resource on networking is the +Linux Network Administrators Guide. +

If you have everything clearly pictured in your mind, +proceed in the following order: +First, generate the configuration files (‘tinc.conf’, your host configuration file, ‘tinc-up’ and perhaps ‘tinc-down’). +Then generate the keypairs. +Finally, distribute the host configuration files. +These steps are described in the subsections below. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.2 Multiple networks

+ + +

In order to allow you to run more than one tinc daemon on one computer, +for instance if your computer is part of more than one VPN, +you can assign a netname to your VPN. +It is not required if you only run one tinc daemon, +it doesn't even have to be the same on all the sites of your VPN, +but it is recommended that you choose one anyway. +

We will asume you use a netname throughout this document. +This means that you call tincd with the -n argument, +which will assign a netname to this daemon. +

The effect of this is that the daemon will set its configuration +root to ‘/etc/tinc/netname/’, where netname is your argument to the -n +option. You'll notice that it appears in syslog as ‘tinc.netname’. +

However, it is not strictly necessary that you call tinc with the -n +option. In this case, the network name would just be empty, and it will +be used as such. tinc now looks for files in ‘/etc/tinc/’, instead of +‘/etc/tinc/netname/’; the configuration file should be ‘/etc/tinc/tinc.conf’, +and the host configuration files are now expected to be in ‘/etc/tinc/hosts/’. +

But it is highly recommended that you use this feature of tinc, because +it will be so much clearer whom your daemon talks to. Hence, we will +assume that you use it. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.3 How connections work

+ +

When tinc starts up, it parses the command-line options and then +reads in the configuration file tinc.conf. +If it sees one or more `ConnectTo' values pointing to other tinc daemons in that file, +it will try to connect to those other daemons. +Whether this succeeds or not and whether `ConnectTo' is specified or not, +tinc will listen for incoming connection from other deamons. +If you did specify a `ConnectTo' value and the other side is not responding, +tinc will keep retrying. +This means that once started, tinc will stay running until you tell it to stop, +and failures to connect to other tinc daemons will not stop your tinc daemon +for trying again later. +This means you don't have to intervene if there are temporary network problems. +

+ + +

There is no real distinction between a server and a client in tinc. +If you wish, you can view a tinc daemon without a `ConnectTo' value as a server, +and one which does specify such a value as a client. +It does not matter if two tinc daemons have a `ConnectTo' value pointing to each other however. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.4 Configuration files

+ +

The actual configuration of the daemon is done in the file +‘/etc/tinc/netname/tinc.conf’ and at least one other file in the directory +‘/etc/tinc/netname/hosts/’. +

These file consists of comments (lines started with a #) or assignments +in the form of +

Variable = Value.
+

+ +

The variable names are case insensitive, and any spaces, tabs, newlines +and carriage returns are ignored. Note: it is not required that you put +in the `=' sign, but doing so improves readability. If you leave it +out, remember to replace it with at least one space character. +

In this section all valid variables are listed in alphabetical order. +The default value is given between parentheses, +other comments are between square brackets. +

+ + + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.4.1 Main configuration variables

+ +

AddressFamily = <ipv4|ipv6|any> (any)

This option affects the address family of listening and outgoing sockets. +If any is selected, then depending on the operating system +both IPv4 and IPv6 or just IPv6 listening sockets will be created. +

+ +

BindToAddress = <address> [experimental]

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. +

+ +

BindToInterface = <interface> [experimental]

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. +

+ +

ConnectTo = <name>

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. +

+ +

Device = <device> (‘/dev/tap0’, ‘/dev/net/tun’ or other depending on platform)

The virtual network device to use. +Tinc will automatically detect what kind of device it is. +Note that you can only use one device per daemon. +Under Windows, use Interface instead of Device. +Note that you can only use one device per daemon. +See also Device files. +

+ +

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. +

tun: Set type to tun. +Depending on the platform, this can either be with or without an address family header (see below). +
+ +
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. +
+ +
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. +
+
tap: Set type to tap. +Tinc will expect packets read from the virtual network device +to start with an Ethernet header. +

+ + +

GraphDumpFile = <filename> [experimental]

If this option is present, +tinc will dump the current network graph to the file filename +every minute, unless there were no changes to the graph. +The file is in a format that can be read by graphviz tools. +If filename starts with a pipe symbol |, +then the rest of the filename is interpreted as a shell command +that is executed, the graph is then sent to stdin. +

+ +

Hostnames = <yes|no> (no)

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. +

+ +

Interface = <interface>

Defines the name of the interface corresponding to the virtual network device. +Depending on the operating system and the type of device this may or may not actually set the name of the interface. +Under Windows, this variable is used to select which network interface will be used. +If you specified a Device, this variable is almost always already correctly set. +

+ +

Mode = <router|switch|hub> (router)

This option selects the way packets are routed to other daemons. +

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. +

This is the default mode, and unless you really know you need another mode, don't change it. +

+ +

switch

In this mode the MAC addresses of the packets on the VPN will be used to +dynamically create a routing table just like an Ethernet switch does. +Unicast, multicast and broadcast packets of every protocol that runs over Ethernet are supported in this mode +at the cost of frequent broadcast ARP requests and routing table updates. +

This mode is primarily useful if you want to bridge Ethernet segments. +

+ +

hub

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. +

+ + +

KeyExpire = <seconds> (3600)

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. +

+ +

MACExpire = <seconds> (600)

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". +

+ +

Name = <name> [required]

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 _). +

+ +

PingInterval = <seconds> (60)

The number of seconds of inactivity that tinc will wait before sending a +probe to the other end. +

+ +

PingTimeout = <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. +

+ +

PriorityInheritance = <yes|no> (no) [experimental]

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. +

+ +

PrivateKey = <key> [obsolete]

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. +

+ +

PrivateKeyFile = <path> (‘/etc/tinc/netname/rsa_key.priv’)

This is the full path name of the RSA private key file that was +generated by ‘tincd --generate-keys’. It must be a full path, not a +relative directory. +

Note that there must be exactly one of PrivateKey +or PrivateKeyFile +specified in the configuration file. +

+ +

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 +‘/etc/tinc/netname/hosts/’ directory. +

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.4.2 Host configuration variables

+ +

Address = <IP address|hostname> [recommended]

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. +

+ +

Cipher = <cipher> (blowfish)

The symmetric cipher algorithm used to encrypt UDP packets. +Any cipher supported by OpenSSL is recognized. +Furthermore, specifying "none" will turn off packet encryption. +It is best to use only those ciphers which support CBC mode. +

+ +

Compression = <level> (0)

This option sets the level of compression used for UDP packets. +Possible values are 0 (off), 1 (fast zlib) and any integer up to 9 (best zlib), +10 (fast lzo) and 11 (best lzo). +

+ +

Digest = <digest> (sha1)

The digest algorithm used to authenticate UDP packets. +Any digest supported by OpenSSL is recognized. +Furthermore, specifying "none" will turn off packet authentication. +

+ +

IndirectData = <yes|no> (no)

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. +

+ +

MACLength = <bytes> (4)

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. +

+ +

PMTU = <mtu> (1514)

This option controls the initial path MTU to this node. +

+ +

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. +

+ +

Port = <port> (655)

This is the port this tinc daemon listens on. +You can use decimal portnumbers or symbolic names (as listed in ‘/etc/services’). +

+ +

PublicKey = <key> [obsolete]

This is the RSA public key for this host. +

+ +

PublicKeyFile = <path> [obsolete]

This is the full path name of the RSA public key file that was generated +by ‘tincd --generate-keys’. It must be a full path, not a relative +directory. +

+ +

From version 1.0pre4 on tinc will store the public key directly into the +host configuration file in PEM format, the above two options then are not +necessary. Either the PEM format is used, or exactly +one of the above two options must be specified +in each host configuration file, if you want to be able to establish a +connection with that host. +

+ +

Subnet = <address[/prefixlength]>

The subnet which this tinc daemon will serve. +Tinc tries to look up which other daemon it should send a packet to by searching the appropiate subnet. +If the packet matches a subnet, +it will be sent to the daemon who has this subnet in his host configuration file. +Multiple subnet lines can be specified for each daemon. +

Subnets can either be single MAC, IPv4 or IPv6 addresses, +in which case a subnet consisting of only that single address is assumed, +or they can be a IPv4 or IPv6 network address with a prefixlength. +Shorthand notations are not supported. +For example, IPv4 subnets must be in a form like 192.168.1.0/24, +where 192.168.1.0 is the network address and 24 is the number of bits set in the netmask. +Note that subnets like 192.168.1.1/24 are invalid! +Read a networking HOWTO/FAQ/guide if you don't understand this. +IPv6 subnets are notated like fec0:0:0:1:0:0:0:0/64. +MAC addresses are notated like 0:1a:2b:3c:4d:5e. +

+ +

Prefixlength is the number of bits set to 1 in the netmask part; for +example: netmask 255.255.255.0 would become /24, 255.255.252.0 becomes +/22. This conforms to standard CIDR notation as described in +RFC1519 +

TCPonly = <yes|no> (no)

If this variable is set to yes, then the packets are tunnelled over a +TCP connection instead of a UDP connection. This is especially useful +for those who want to run a tinc daemon from behind a masquerading +firewall, or if UDP packet routing is disabled somehow. +Setting this options also implicitly sets IndirectData. +

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.4.3 Scripts

+ + +

Apart from reading the server and host configuration files, +tinc can also run scripts at certain moments. +Under Windows (not Cygwin), the scripts should have the extension .bat. +

+
‘/etc/tinc/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. +
+ +
‘/etc/tinc/netname/tinc-down’: This script is started right before the tinc daemon quits. +
+
‘/etc/tinc/netname/hosts/host-up’: This script is started when the tinc daemon with name host becomes reachable. +
+
‘/etc/tinc/netname/hosts/host-down’: This script is started when the tinc daemon with name host becomes unreachable. +
+
‘/etc/tinc/netname/host-up’: This script is started when any host becomes reachable. +
+
‘/etc/tinc/netname/host-down’: This script is started when any host becomes unreachable. +
+
‘/etc/tinc/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. +
+
‘/etc/tinc/netname/subnet-down’: This script is started when a Subnet becomes unreachable. +

+ + +

The scripts are started without command line arguments, +but can make use of certain environment variables. +Under UNIX like operating systems the names of environment variables must be preceded by a $ in scripts. +Under Windows, in ‘.bat’ files, they have to be put between % signs. +

+
NETNAME: If a netname was specified, this environment variable contains it. +
+ +
NAME: Contains the name of this tinc daemon. +
+ +
DEVICE: Contains the name of the virtual network device that tinc uses. +
+ +
INTERFACE: Contains the name of the virtual network interface that tinc uses. +This should be used for commands like ifconfig. +
+ +
NODE: When a host becomes (un)reachable, this is set to its name. +If a subnet becomes (un)reachable, this is set to the owner of that subnet. +
+ +
REMOTEADDRESS: When a host becomes (un)reachable, this is set to its real address. +
+ +
REMOTEPORT: When a host becomes (un)reachable, +this is set to the port number it uses for communication with other tinc daemons. +
+
SUBNET: When a subnet becomes (un)reachable, this is set to the subnet. +
+

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.4.4 How to configure

+ + +

Step 1. Creating the main configuration file

+ +

The main configuration file will be called ‘/etc/tinc/netname/tinc.conf’. +Adapt the following example to create a basic configuration file: +

Name = yourname
+Device = ‘/dev/tap0’
+

+ +

Then, if you know to which other tinc daemon(s) yours is going to connect, +add `ConnectTo' values. +

+ +

Step 2. Creating your host configuration file

+ +

If you added a line containing `Name = yourname' in the main configuarion file, +you will need to create a host configuration file ‘/etc/tinc/netname/hosts/yourname’. +Adapt the following example to create a host configuration file: +

Address = your.real.hostname.org
+Subnet = 192.168.1.0/24
+

+ +

You can also use an IP address instead of a hostname. +The `Subnet' specifies the address range that is local for your part of the VPN only. +If you have multiple address ranges you can specify more than one `Subnet'. +You might also need to add a `Port' if you want your tinc daemon to run on a different port number than the default (655). +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.5 Generating keypairs

+ + +

Now that you have already created the main configuration file and your host configuration file, +you can easily create a public/private keypair by entering the following command: +

tincd -n netname -K
+

+ +

Tinc will generate a public and a private key and ask you where to put them. +Just press enter to accept the defaults. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.6 Network interfaces

+ +

Before tinc can start transmitting data over the tunnel, it must +set up the virtual network interface. +

First, decide which IP addresses you want to have associated with these +devices, and what network mask they must have. +

Tinc will open a virtual network device (‘/dev/tun’, ‘/dev/tap0’ or similar), +which will also create a network interface called something like ‘tun0’, ‘tap0’. +If you are using the Linux tun/tap driver, the network interface will by default have the same name as the netname. +Under Windows you can change the name of the network interface from the Network Connections control panel. +

+ +

You can configure the network interface by putting ordinary ifconfig, route, and other commands +to a script named ‘/etc/tinc/netname/tinc-up’. +When tinc starts, this script will be executed. When tinc exits, it will execute the script named +‘/etc/tinc/netname/tinc-down’, but normally you don't need to create that script. +

An example ‘tinc-up’ script: +

#!/bin/sh
+ifconfig $INTERFACE 192.168.1.1 netmask 255.255.0.0
+

+ +

This script gives the interface an IP address and a netmask. +The kernel will also automatically add a route to this interface, so normally you don't need +to add route commands to the ‘tinc-up’ script. +The kernel will also bring the interface up after this command. +The netmask is the mask of the entire VPN network, not just your +own subnet. +

The exact syntax of the ifconfig and route commands differs from platform to platform. +You can look up the commands for setting addresses and adding routes in Platform specific information, +but it is best to consult the manpages of those utilities on your platform. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

4.7 Example configuration

+ + + +

Imagine the following situation. Branch A of our example `company' wants to connect +three branch offices in B, C and D using the Internet. All four offices +have a 24/7 connection to the Internet. +

A is going to serve as the center of the network. B and C will connect +to A, and D will connect to C. Each office will be assigned their own IP +network, 10.x.0.0. +

A: net 10.1.0.0 mask 255.255.0.0 gateway 10.1.54.1 internet IP 1.2.3.4
+B: net 10.2.0.0 mask 255.255.0.0 gateway 10.2.1.12 internet IP 2.3.4.5
+C: net 10.3.0.0 mask 255.255.0.0 gateway 10.3.69.254 internet IP 3.4.5.6
+D: net 10.4.0.0 mask 255.255.0.0 gateway 10.4.3.32 internet IP 4.5.6.7
+

+ +

Here, “gateway” is the VPN IP address of the machine that is running the +tincd, and “internet IP” is the IP address of the firewall, which does not +need to run tincd, but it must do a port forwarding of TCP and UDP on port +655 (unless otherwise configured). +

In this example, it is assumed that eth0 is the interface that points to +the inner (physical) LAN of the office, although this could also be the +same as the interface that leads to the Internet. The configuration of +the real interface is also shown as a comment, to give you an idea of +how these example host is set up. All branches use the netname `company' +for this particular VPN. +

+ +

For Branch A

+ +

BranchA would be configured like this: +

In ‘/etc/tinc/company/tinc-up’: +

# Real interface of internal network:
+# ifconfig eth0 10.1.54.1 netmask 255.255.0.0
+
+ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0
+

+ +

and in ‘/etc/tinc/company/tinc.conf’: +

Name = BranchA
+Device = /dev/tap0
+

+ +

On all hosts, ‘/etc/tinc/company/hosts/BranchA’ contains: +

Subnet = 10.1.0.0/16
+Address = 1.2.3.4
+
+-----BEGIN RSA PUBLIC KEY-----
+...
+-----END RSA PUBLIC KEY-----
+

+ +

Note that the IP addresses of eth0 and tap0 are the same. +This is quite possible, if you make sure that the netmasks of the interfaces are different. +It is in fact recommended to give 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. +

+ + +

For Branch B

+ +

In ‘/etc/tinc/company/tinc-up’: +

# Real interface of internal network:
+# ifconfig eth0 10.2.43.8 netmask 255.255.0.0
+
+ifconfig $INTERFACE 10.2.1.12 netmask 255.0.0.0
+

+ +

and in ‘/etc/tinc/company/tinc.conf’: +

Name = BranchB
+ConnectTo = BranchA
+

+ +

Note here that the internal address (on eth0) doesn't have to be the +same as on the tap0 device. Also, ConnectTo is given so that no-one can +connect to this node. +

On all hosts, in ‘/etc/tinc/company/hosts/BranchB’: +

Subnet = 10.2.0.0/16
+Address = 2.3.4.5
+
+-----BEGIN RSA PUBLIC KEY-----
+...
+-----END RSA PUBLIC KEY-----
+

+ + + +

For Branch C

+ +

In ‘/etc/tinc/company/tinc-up’: +

# Real interface of internal network:
+# ifconfig eth0 10.3.69.254 netmask 255.255.0.0
+
+ifconfig $INTERFACE 10.3.69.254 netmask 255.0.0.0
+

+ +

and in ‘/etc/tinc/company/tinc.conf’: +

Name = BranchC
+ConnectTo = BranchA
+Device = /dev/tap1
+

+ +

C already has another daemon that runs on port 655, so they have to +reserve another port for tinc. It knows the portnumber it has to listen on +from it's own host configuration file. +

On all hosts, in ‘/etc/tinc/company/hosts/BranchC’: +

Address = 3.4.5.6
+Subnet = 10.3.0.0/16
+Port = 2000
+
+-----BEGIN RSA PUBLIC KEY-----
+...
+-----END RSA PUBLIC KEY-----
+

+ + + +

For Branch D

+ +

In ‘/etc/tinc/company/tinc-up’: +

# Real interface of internal network:
+# ifconfig eth0 10.4.3.32 netmask 255.255.0.0
+
+ifconfig $INTERFACE 10.4.3.32 netmask 255.0.0.0
+

+ +

and in ‘/etc/tinc/company/tinc.conf’: +

Name = BranchD
+ConnectTo = BranchC
+Device = /dev/net/tun
+

+ +

D will be connecting to C, which has a tincd running for this network on +port 2000. It knows the port number from the host configuration file. +Also note that since D uses the tun/tap driver, the network interface +will not be called `tun' or `tap0' or something like that, but will +have the same name as netname. +

On all hosts, in ‘/etc/tinc/company/hosts/BranchD’: +

Subnet = 10.4.0.0/16
+Address = 4.5.6.7
+
+-----BEGIN RSA PUBLIC KEY-----
+...
+-----END RSA PUBLIC KEY-----
+

+ + +

Key files

+ +

A, B, C and D all have generated a public/private keypair with the following command: +

tincd -n company -K
+

+ +

The private key is stored in ‘/etc/tinc/company/rsa_key.priv’, +the public key is put into the host configuration file in the ‘/etc/tinc/company/hosts/’ directory. +During key generation, tinc automatically guesses the right filenames based on the -n option and +the Name directive in the ‘tinc.conf’ file (if it is available). +

+ +

Starting

+ +

After each branch has finished configuration and they have distributed +the host configuration files amongst them, they can start their tinc daemons. +They don't necessarily have to wait for the other branches to have started +their daemons, tinc will try connecting until they are available. +

+ +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_4.html +++ tinc-1.0.9/doc/tinc/tinc_4.html @@ -0,0 +1,533 @@ + + + + + +tinc Manual: 5. Running tinc + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5. Running tinc

+ +

If everything else is done, you can start tinc by typing the following command: +

tincd -n netname
+

+ + +

Tinc will detach from the terminal and continue to run in the background like a good daemon. +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. +

+ + + + + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.1 Runtime options

+ +

Besides the settings in the configuration file, tinc also accepts some +command line options. +

+ + + +

‘-c, --config=path’: Read configuration options from the directory path. The default is +‘/etc/tinc/netname/’. +
+
‘-D, --no-detach’: Don't fork and detach. +This will also disable the automatic restart mechanism for fatal errors. +
+
‘-d, --debug=level’: Set debug level to level. The higher the debug level, the more gets +logged. Everything goes via syslog. +
+
‘-k, --kill[=signal]’: Attempt to kill a running tincd (optionally with the specified signal instead of SIGTERM) and exit. +Use it in conjunction with the -n option to make sure you kill the right tinc daemon. +Under native Windows the optional argument is ignored, +the service will always be stopped and removed. +
+
‘-n, --net=netname’: Use configuration for net netname. See section Multiple networks. +
+
‘-K, --generate-keys[=bits]’: Generate public/private keypair of bits length. If bits is not specified, +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. +
+
‘-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. +
+
‘--logfile[=file]’: Write log entries to a file instead of to the system logging facility. +If file is omitted, the default is ‘/var/log/tinc.netname.log’. +
+
‘--pidfile=file’: Write PID to file instead of ‘/var/run/tinc.netname.pid’. +
+
‘--bypass-security’: Disables encryption and authentication. +Only useful for debugging. +
+
‘--help’: Display a short reminder of these runtime options and terminate. +
+
‘--version’: Output version information and exit. +
+

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.2 Signals

+ +

You can also send the following signals to a running tincd process: +

‘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. +
+
‘HUP’: Partially rereads configuration files. +Connections to hosts whose host config file are removed are closed. +New outgoing connections specified in ‘tinc.conf’ will be made. +
+
‘INT’: Temporarily increases debug level to 5. +Send this signal again to revert to the original level. +
+
‘USR1’: Dumps the connection list to syslog. +
+
‘USR2’: Dumps virtual network device statistics, all known nodes, edges and subnets to syslog. +
+
‘WINCH’: Purges all information remembered about unreachable nodes. +
+

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.3 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: +

‘0’: This will log a message indicating tinc has started along with a version number. +It will also log any serious error. +
+
‘1’: This will log all connections that are made with other tinc daemons. +
+
‘2’: This will log status and error messages from scripts and other tinc daemons. +
+
‘3’: This will log all requests that are exchanged with other tinc daemons. These include +authentication, key exchange and connection list updates. +
+
‘4’: This will log a copy of everything received on the meta socket. +
+
‘5’: This will log all network traffic over the virtual private network. +
+

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.4 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: +

tincd -n netname -d5 -D
+

+ +

If tinc does not log any error messages, then you might want to check the following things: +

‘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. + +
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? + +
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 ‘TCPOnly = yes’ to your host config file to force tinc to only use a single TCP connection, +this works through most firewalls and NATs. + +

+ + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.5 Error messages

+ +

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. +

‘Could not open /dev/tap0: No such device’

You forgot to `modprobe netlink_dev' or `modprobe ethertap'. +
You forgot to compile `Netlink device emulation' in the kernel. +

+ +

‘Can't write to /dev/net/tun: No such device’

You forgot to `modprobe tun'. +
You forgot to compile `Universal TUN/TAP driver' in the kernel. +
The tun device is located somewhere else in ‘/dev/’. +

+ +

‘Network address and prefix length do not match!’

The Subnet field must contain a network address, trailing bits should be 0. +
If you only want to use one IP address, set the netmask to /32. +

+ +

‘Error reading RSA key file `rsa_key.priv': No such file or directory’

You forgot to create a public/private keypair. +
Specify the complete pathname to the private key file with the ‘PrivateKeyFile’ option. +

+ +

‘Warning: insecure file permissions for RSA private key file `rsa_key.priv'!’

The private key file is readable by users other than root. +Use chmod to correct the file permissions. +

+ +

‘Creating metasocket failed: Address family not supported’

By default tinc tries to create both IPv4 and IPv6 sockets. +On some platforms this might not be implemented. +If the logs show ‘Ready’ later on, then at least one metasocket was created, +and you can ignore this message. +You can add ‘AddressFamily = ipv4’ to ‘tinc.conf’ to prevent this from happening. +

+ +

‘Cannot route packet: unknown IPv4 destination 1.2.3.4’

You try to send traffic to a host on the VPN for which no Subnet is known. +
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. +

+ +

‘Cannot route packet: ARP request for unknown address 1.2.3.4’

You try to send traffic to a host on the VPN for which no Subnet is known. +

+ +

‘Packet with destination 1.2.3.4 is looping back to us!’

Something is not configured right. Packets are being sent out to the +virtual network device, but according to the Subnet directives in your host configuration +file, those packets should go to your own host. Most common mistake is that +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 +cases be larger. Rethink your configuration. +Note that you will only see this message if you specified a debug +level of 5 or higher! +
Chances are that a ‘Subnet = ...’ line in the host configuration file of this tinc daemon is wrong. +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. +

+ +

‘Node foo (1.2.3.4) is not reachable’

Node foo does not have a connection anymore, its tinc daemon is not running or its connection to the Internet is broken. +

+ +

‘Received UDP packet from unknown source 1.2.3.4 (port 12345)’

If you see this only sporadically, it is harmless and caused by a node sending packets using an old key. +
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 ‘TCPOnly = yes’ to host configuration files to force all VPN traffic to go over a TCP connection. +

+ +

‘Got bad/bogus/unauthorized REQUEST from foo (1.2.3.4 port 12345)’

Node foo does not have the right public/private keypair. +Generate new keypairs and distribute them again. +
An attacker tries to gain access to your VPN. +
A network error caused corruption of metadata sent from foo. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

5.6 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 Contact information. +Be sure to include the following information in your bugreport: +

A clear description of what you are trying to achieve and what the problem is. +
What platform (operating system, version, hardware architecture) and which version of tinc you use. +
If compiling tinc fails, a copy of ‘config.log’ and the error messages you get. +
Otherwise, a copy of ‘tinc.conf’, ‘tinc-up’ and all files in the ‘hosts/’ directory. +
The output of the commands ‘ifconfig -a’ and ‘route -n’ (or ‘netstat -rn’ if that doesn't work). +
The output of any command that fails to work as it should (like ping or traceroute). +

+ +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_5.html +++ tinc-1.0.9/doc/tinc/tinc_5.html @@ -0,0 +1,655 @@ + + + + + +tinc Manual: 6. Technical information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6. Technical information

+ + + + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.1 The connection

+ +

Tinc is a daemon that takes VPN data and transmit that to another host +computer over the existing Internet infrastructure. +

+ + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.1.1 The UDP tunnel

+ + +

The data itself is read from a character device file, the so-called +virtual network device. This device is associated with a network +interface. Any data sent to this interface can be read from the device, +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. +

So when tinc reads an Ethernet frame from the device, it determines its +type. When tinc is in it's default routing mode, it can handle IPv4 and IPv6 +packets. Depending on the Subnet lines, it will send the packets off to their destination IP address. +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). +However, only `tap' style devices provide this information. +

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. +

+ + +

When that is done, time has come to actually transport the +packet to the destination computer. We do this by sending the packet +over an UDP connection to the destination host. This is called +encapsulating, the VPN packet (though now encrypted) is +encapsulated in another IP datagram. +

When the destination receives this packet, the same thing happens, only +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. +

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. +Tinc solves this by letting the receiving end detect the MAC address of its own virtual network interface +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. +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. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.1.2 The meta-connection

+ +

Having only a UDP connection available is not enough. Though suitable +for transmitting data, we want to be able to reliably send other +information, such as routing and session key information to somebody. +

+ +

TCP is a better alternative, because it already contains protection +against information being lost, unlike UDP. +

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 +meta-information doesn't get lost on the way to another computer. +

+ + +

Like with any communication, we must have a protocol, so that everybody +knows what everything stands for, and how she should react. Because we +have two connections, we also have two protocols. The protocol used for +the UDP data is the “data-protocol,” the other one is the +“meta-protocol.” +

The reason we don't use TCP for both protocols is that UDP is much +better for encapsulation, even while it is less reliable. The real +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 +three ACKs sent instead of just one. Furthermore, if there would be +a timeout, both TCP streams would sense the timeout, and both would +start re-sending packets. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.2 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 +daemon started with the –bypass-security option +and to read and write requests by hand, provided that one +understands the numeric codes sent. +

The authentication scheme is described in Authentication protocol. After a +successful authentication, the server and the client will exchange all the +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. +

+ + +

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
+------------------------------------------------------------------
+

+ +

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. +

+ + +

message
+------------------------------------------------------------------
+DEL_EDGE node1 node2
+           |     +----> name of destination node
+           +----------> name of source node
+
+DEL_SUBNET node 192.168.1.0/24
+             |         |     +--> prefixlength
+             |         +--------> network address
+             +------------------> owner of this subnet
+------------------------------------------------------------------
+

+ +

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. +

+ + + +

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
+------------------------------------------------------------------
+

+ +

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 +destination. +

+ +

daemon	message
+------------------------------------------------------------------
+origin	PING
+dest.	PONG
+------------------------------------------------------------------
+

+ +

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. +

This basically covers what is sent over the meta connection by tinc. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.3 Security

+ + +

Tinc got its name from “TINC,” short for There Is No Cabal; the +alleged Cabal was/is an organisation that was said to keep an eye on the +entire Internet. As this is exactly what you don't want, we named +the tinc project after TINC. +

But in order to be “immune” to eavesdropping, you'll have to encrypt +your data. Because tinc is a Secure VPN (SVPN) daemon, it does +exactly that: encrypt. +Tinc by default uses blowfish encryption with 128 bit keys in CBC mode, 32 bit +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 +encryption algorithm is always the default length used by OpenSSL. +

+ + + + + + + +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.3.1 Authentication protocol

+ + +

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. +

+ + + + +

daemon  message
+--------------------------------------------------------------------------
+client  <attempts connection>
+
+server  <accepts connection>
+
+client  ID client 12
+              |   +---> version
+              +-------> name of tinc daemon
+
+server  ID server 12
+              |   +---> version
+              +-------> name of tinc daemon
+
+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:
+ - the client will symmetrically encrypt outgoing traffic using S1
+ - the server will symmetrically encrypt outgoing traffic using S2
+
+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
+
+After the correct challenge replies are received, both ends have proved
+their identity. Further information is exchanged.
+
+client  ACK 655 123 0
+             |   |  +-> options
+	         |   +----> estimated weight
+	         +--------> listening port of client
+
+server  ACK 655 321 0
+             |   |  +-> options
+	         |   +----> estimated weight
+	         +--------> listening port of server
+--------------------------------------------------------------------------
+

+ +

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. +

Fourth: the first thing that is sent via the symmetric cipher encrypted +connection is a totally random string, so that there is no known plaintext (for +an attacker) in the beginning of the encrypted stream. +

+ +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.3.2 Encryption of network packets

+ + +

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 +to retrieve it. The packet is stored in a queue while waiting for the +key to arrive. +

The UDP packet containing the network packet from the VPN has the following layout: +

... | IP header | UDP header | seqno | VPN packet | MAC | UDP trailer
+                             \___________________/\_____/
+                                       |             |
+                                       V             +---> digest algorithm
+                         Encrypted with symmetric cipher
+

+ +

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 +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. +

+ + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

6.3.3 Security issues

+ +

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. +

+ +

+ + + + + + + + + + + + +

[ << ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

+ + This document was generated by Guus Sliepen on December, 26 2008 using texi2html 1.78. + +
+ +

+ + --- tinc-1.0.9.orig/doc/tinc/tinc_6.html +++ tinc-1.0.9/doc/tinc/tinc_6.html @@ -0,0 +1,82 @@ + + + + + +tinc Manual: 7. Platform specific information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

7. Platform specific information

+ + + + + + +

+ + + + + + + + + + +

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

/dev/null 2>/dev/null +fi +# End automatically added section + +#DEBHELPER# --- tinc-1.0.9.orig/debian/postinst +++ tinc-1.0.9/debian/postinst @@ -0,0 +1,90 @@ +#! /bin/sh +# postinst script for tinc +# +# $Id: postinst,v 1.6 2000/05/21 23:01:28 zarq Exp $ +# +# see: dh_installdeb(1) + +TCONF="/etc/tinc" +NETSFILE="$TCONF/nets.boot" +RET="false" + +set -e + +# summary of how this script can be called: +# * `configure' +# * `abort-upgrade' +# * `abort-remove' `in-favour' +# +# * `abort-deconfigure' `in-favour' +# `removing' +# +# for details, see /usr/doc/packaging-manual/ +# +# quoting from the policy: +# Any necessary prompting should almost always be confined to the +# post-installation script, and should be protected with a conditional +# so that unnecessary prompting doesn't happen if a package's +# installation fails and the `postinst' is called with `abort-upgrade', +# `abort-remove' or `abort-deconfigure'. + +# Automatically added by dh_installinit, edited for use with debconf +if [ -x "/etc/init.d/tinc" ]; then + update-rc.d tinc defaults >/dev/null + + if [ "$1" = "configure" ] ; then + if dpkg --compare-versions "$2" lt "1.0pre5-4" ; then + RET="true" + else + if [ -e /usr/share/debconf/confmodule ] ; then + . /usr/share/debconf/confmodule + db_get tinc/restart_on_upgrade + db_stop + else + RET="true" + fi + fi + fi +fi +# End automatically added section + + +case "$1" in + configure) + if [ ! -e /dev/.devfsd ] ; then if [ ! -e /dev/.devfs ] ; then + if [ ! -e /dev/net/tun ] ; then if [ ! -e /dev/tun ] ; then + echo "Creating tun device..." + cd /dev && ./MAKEDEV net/tun 2>/dev/null || ./MAKEDEV tun 2>/dev/null || echo "Failed to create tun device." + fi; fi + fi; fi + + if [ ! -e $NETSFILE ] ; then + echo "## This file contains all names of the networks to be started on system startup." > $NETSFILE + fi + + if [ "$RET" = "true" ] ; then + invoke-rc.d tinc start + else + echo "I have not stopped or restarted the tinc daemon. You should do this" + echo "yourself whenever you're ready; type \`\`invoke-rc.d tinc restart''." + fi + ;; + + abort-upgrade|abort-remove|abort-deconfigure) + + ;; + + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 0 + ;; +esac + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 + + --- tinc-1.0.9.orig/debian/init.d +++ tinc-1.0.9/debian/init.d @@ -0,0 +1,85 @@ +#! /bin/sh +# +### BEGIN INIT INFO +# Provides: tinc +# Required-Start: $network +# Required-Stop: $network +# Should-Start: $syslog $named +# Should-Stop: $syslog +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 +# Short-Description: Start tinc daemons +# Description: Create a file $NETSFILE (/etc/tinc/nets.boot), +# and put all the names of the networks in there. +# These names must be valid directory names under +# $TCONF (/etc/tinc). Lines starting with a # will be +# ignored in this file. +### END INIT INFO +# +# Based on Lubomir Bulej's Redhat init script. + +DAEMON="/usr/sbin/tincd" +NAME="tinc" +DESC="tinc daemons" +TCONF="/etc/tinc" +NETSFILE="$TCONF/nets.boot" +NETS="" + +test -f $DAEMON || exit 0 + +[ -r /etc/default/tinc ] && . /etc/default/tinc + +find_nets () { + if [ ! -f $NETSFILE ] ; then + echo "Please create $NETSFILE." + exit 0 + fi + NETS="`egrep '^[ ]*[a-zA-Z0-9_-]+[ ]*$' $NETSFILE`" +} + +case "$1" in + start) + find_nets + echo -n "Starting $DESC:" + for n in $NETS ; do + echo -n " $n" + $DAEMON -n $n $EXTRA + done + echo "." + ;; + stop) + find_nets + echo -n "Stopping $DESC:" + for n in $NETS ; do + echo -n " $n" + $DAEMON -n $n $EXTRA -k + done + echo "." + ;; + reload|force-reload) + find_nets + echo -n "Reloading $DESC configuration:" + for n in $NETS ; do + echo -n " $n" + $DAEMON -n $n $EXTRA -kHUP + done + echo "." + ;; + restart) + find_nets + echo -n "Restarting $DESC:" + for n in $NETS ; do + echo -n " $n" + $DAEMON -n $n $EXTRA -k + sleep 1 + $DAEMON -n $n $EXTRA + done + echo "." + ;; + *) + echo "Usage: /etc/init.d/$NAME {start|stop|reload|restart|force-reload}" + exit 1 + ;; +esac + +exit 0 --- tinc-1.0.9.orig/debian/doc-base.tinc +++ tinc-1.0.9/debian/doc-base.tinc @@ -0,0 +1,10 @@ +Document: tinc +Title: tinc Manual +Author: Ivo Timmermans, Guus Sliepen +Abstract: This manual describes how to set up a Virtual Private + Network with tinc. +Section: System/Security + +Format: HTML +Files: /usr/share/doc/tinc/tinc*.html +Index: /usr/share/doc/tinc/tinc_toc.html --- tinc-1.0.9.orig/debian/changelog +++ tinc-1.0.9/debian/changelog @@ -0,0 +1,400 @@ +tinc (1.0.9-1) unstable; urgency=low + + * New upstream release. + - Binds IPv6 sockets only to IPv6. Closes: #440150 + * Update copyright file. Closes: #482566 + + -- Guus Sliepen Fri, 26 Dec 2008 13:25:05 +0100 + +tinc (1.0.8-2) unstable; urgency=low + + * Include Portugese debconf translation. Closes: #434191 + + -- Guus Sliepen Tue, 14 Aug 2007 13:50:27 +0200 + +tinc (1.0.8-1) unstable; urgency=low + + * New upstream release. Closes: #173987 + * Include german debconf translation. Closes: #412351 + * Build-Depend on texinfo. Closes: #424209 + + -- Guus Sliepen Wed, 16 May 2007 17:59:16 +0200 + +tinc (1.0.7-1) unstable; urgency=low + + * New upstream release. + + -- Guus Sliepen Fri, 5 Jan 2007 15:55:42 +0100 + +tinc (1.0.6-1) unstable; urgency=low + + * New upstream release. + + -- Guus Sliepen Mon, 18 Dec 2006 15:41:03 +0100 + +tinc (1.0.5-1) unstable; urgency=low + + * New upstream release. Closes: #391610 + * Add an LSB section to the init script. + + -- Guus Sliepen Tue, 14 Nov 2006 16:32:20 +0100 + +tinc (1.0.4-4) unstable; urgency=low + + * Include swedish debconf translation. Closes: #332963 + * Remove nets.boot on purge. Closes: #333303 + + -- Guus Sliepen Mon, 17 Oct 2005 12:34:32 +0200 + +tinc (1.0.4-3) unstable; urgency=low + + * Depend on debconf | debconf-2.0. + * Include vietnamese debconf translation. Closes: #322305 + * Include japanese debconf translation. Closes: #319591 + + -- Guus Sliepen Thu, 29 Sep 2005 11:15:34 +0200 + +tinc (1.0.4-2) unstable; urgency=low + + * Compensate for change in texinfo's output directory. Closes: #318562 + * Include Czech translation of the debconf questions. Closes: #312982 + + -- Guus Sliepen Sat, 16 Jul 2005 11:42:04 +0200 + +tinc (1.0.4-1) unstable; urgency=low + + * New upstream release. Closes: #294819 + * Update french translation of debconf template. Closes: #293371, #296148 + * Allow dashes in nets.boot. Closes: #296281 + + -- Guus Sliepen Wed, 4 May 2005 21:56:22 +0200 + +tinc (1.0.3-4) unstable; urgency=low + + * Call debconf early in postinst so it won't get confused by output + from other commands in the postinst script. Closes: #292920 + * If MAKEDEV doesn't know about net/tun, fall back to tun. + + -- Guus Sliepen Mon, 31 Jan 2005 13:27:16 +0100 + +tinc (1.0.3-3) unstable; urgency=low + + * Fix clean rule in debian/rules. + + -- Guus Sliepen Thu, 27 Jan 2005 23:16:59 +0000 + +tinc (1.0.3-2) unstable; urgency=low + + * Don't check for /dev/tap* in postinst if we don't create them anyway. + * MAKEDEV expects net/tun instead of tun. + * Don't ask if /dev/net/tun should be created, just do it. + Closes: #259489, #292450 + * Move $EXTRA from init.d/tinc to /etc/default/tinc. Closes: #281366 + + -- Guus Sliepen Thu, 27 Jan 2005 14:10:02 +0100 + +tinc (1.0.3-1) unstable; urgency=low + + * New upstream release. + * Adopting the package from Ivo. + * Use invoke-rc.d, and tell user to do so as well. Closes: #223276 + * Let force-reload do the same thing as reload. Closes: #230180 + + -- Guus Sliepen Fri, 1 Oct 2004 21:04:14 +0200 + +tinc (1.0.2-2) unstable; urgency=low + + * debian/control: Oops, really make that automake1.7. + + -- Ivo Timmermans Sat, 8 Nov 2003 21:53:04 +0100 + +tinc (1.0.2-1) unstable; urgency=low + + * New upstream release: + * Fix broken replies to CHAL_RESP. (Closes: #217646) + * debian/control: Updated automake build dependency to automake1.7. + (Closes: #219360) + + -- Ivo Timmermans Sat, 8 Nov 2003 19:56:04 +0100 + +tinc (1.0.1-2) unstable; urgency=low + + * debian/dirs: Removed, moved contents to tinc.dirs. + (Closes: #208591) + * debian/docs: Renamed to tinc.docs. + * debian/rules: Install the contents of doc/sample-config.tar.gz in + /usr/share/doc/tinc/examples instead of /etc/tinc. + * debian/Makefile*: Removed. + + -- Ivo Timmermans Wed, 10 Sep 2003 12:19:32 +0200 + +tinc (1.0.1-1) unstable; urgency=low + + * New upstream release. + * debian/patches/001_openbsd_device.c.patch: Removed. + + -- Ivo Timmermans Thu, 14 Aug 2003 17:03:28 +0200 + +tinc (1.0release-1) unstable; urgency=low + + * New upstream version. (Closes: #204639) + * Fixes switching back to normal logging mode when killing with + SIGINT twice. (Closes: #175633) + * Uses one SSL context struct for each connection, speeding up + encrypting/decrypting data; don't throw away out of sequence + packets. (Closes: #188874) + * Fixes handling of broadcast messages. (Closes: #175632) + * debian/rules: Use cdbs. + * debian/control: Build-Depend on cdbs, liblzo-dev. + * debian/patches/001_openbsd_device.c.patch: Sync openbsd/device.c to + latest CVS version. + + -- Ivo Timmermans Sun, 10 Aug 2003 16:13:29 +0200 + +tinc (1.0pre8-6) unstable; urgency=low + + * debian/po/fr.po: Added French debconf translation. (Closes: #201803) + + -- Ivo Timmermans Fri, 18 Jul 2003 10:03:20 +0200 + +tinc (1.0pre8-5) unstable; urgency=low + + * debian/*: Change to po-debconf, thanks to From: Michel Grentzinger + for the patch: + - change debhelper dependency to 4.1.16 (according to man + po-debconf), + - manually add nl translation in old tinc.templates (master), + - run debconf-gettextize debian/tinc.templates, + - move old templates files (debian/tinc.templates.*), + - change construction "If you say no" to "If you refuse", + * debian/rules: Call po2debconf. + * debian/rules: Don't copy COPYING.README to the package. + * debian/control: Update Standards-Version. + * debian/conffiles: Removed. + * debian/postinst: No longer use mknod directly, use MAKEDEV. + + -- Ivo Timmermans Tue, 15 Jul 2003 20:13:47 +0200 + +tinc (1.0pre8-4) unstable; urgency=low + + * src/net.h, src/net_packet.c, src/net_setup.c: Apply fix from CVS + for OpenSSL-related memory leaks. (Closes: #189432) + + -- Ivo Timmermans Mon, 5 May 2003 15:00:29 +0200 + +tinc (1.0pre8-3) unstable; urgency=low + + * m4/openssl.m4: Updated to CVS version. (Closes: #184400) + + -- Ivo Timmermans Thu, 13 Mar 2003 17:24:42 +0100 + +tinc (1.0pre8-2) unstable; urgency=low + + * debian/postinst: Create /dev/net/tun if it doesn't exist. + * debian/tinc.modules: Add alias for /dev/net/tun. + * debian/rules: Install tinc.modules. + * These things together: (Closes: #151967, #153156) + + -- Ivo Timmermans Wed, 13 Nov 2002 22:45:38 +0100 + +tinc (1.0pre8-1) unstable; urgency=low + + * New upstream version. + * debian/rules: + - DEB_BUILD_OPTIONS support. + - Enable --enable-tracing by default. + + -- Ivo Timmermans Tue, 17 Sep 2002 13:50:44 +0200 + +tinc (1.0pre7-3) unstable; urgency=low + + * Properly install _all_ info pages. (Closes: #144718) + + -- Ivo Timmermans Wed, 29 May 2002 14:01:21 +0200 + +tinc (1.0pre7-2) unstable; urgency=low + + * Dutch translation wasn't being installed. + + -- Ivo Timmermans Thu, 11 Apr 2002 09:26:14 +0200 + +tinc (1.0pre7-1) unstable; urgency=medium + + * New upstream release. + + -- Ivo Timmermans Tue, 9 Apr 2002 16:04:46 +0200 + +tinc (1.0pre6-3) unstable; urgency=medium + + * Synched with upstream CVS. + * Added build dependency on zlib1g-dev. (Closes: #141705) + + -- Ivo Timmermans Mon, 8 Apr 2002 21:19:31 +0200 + +tinc (1.0pre6-2) unstable; urgency=low + + * The Section was non-US again, so changed it back to main/net. + + -- Ivo Timmermans Thu, 28 Mar 2002 07:26:10 +0100 + +tinc (1.0pre6-1) unstable; urgency=low + + * New upstream release. + * Fixed text in debian/copyright + + -- Ivo Timmermans Wed, 27 Mar 2002 23:10:07 +0100 + +tinc (1.0pre5-4) unstable; urgency=low + + * Added a debconf question for restarting on upgrade. + * Added reload option to init.d, start with EXTRA='-d' default. + * Moved from non-US to main. + * Install example configuration files. + * The HTML documentation wasn't installed; fixed. + + -- Ivo Timmermans Tue, 26 Mar 2002 20:14:19 +0100 + +tinc (1.0pre5-3) unstable; urgency=low + + * Config variables are now treated case sentitivly again. + * Added a forgotten xstrdup. + + -- Ivo Timmermans Fri, 15 Feb 2002 12:35:17 +0100 + +tinc (1.0pre5-2) unstable; urgency=low + + * MaxTimeout accidentally wasn't configurable. (Closes: #119653) + + -- Ivo Timmermans Wed, 13 Feb 2002 13:36:54 +0100 + +tinc (1.0pre5-1) unstable; urgency=low + + * New upstream version. (Closes: #119653) + * Init script redone in sh. + + -- Ivo Timmermans Sun, 10 Feb 2002 16:39:53 +0100 + +tinc (1.0pre4-1.cvs010621.6) unstable; urgency=low + + * Somehow po-Makefile.in.in.diff got lost, readded. (Closes: #119157) + + -- Ivo Timmermans Thu, 15 Nov 2001 17:00:03 +0100 + +tinc (1.0pre4-1.cvs010621.5) unstable; urgency=low + + * Fix a typo in postinst that let it MAKEDEV even on devfs. + (Closes: #116034) + + -- Ivo Timmermans Thu, 18 Oct 2001 09:35:16 +0200 + +tinc (1.0pre4-1.cvs010621.4) unstable; urgency=low + + * Ask before creating the device files. (Closes: #111099) + * Add a section to the info file. + + -- Ivo Timmermans Fri, 12 Oct 2001 20:47:09 +0200 + +tinc (1.0pre4-1.cvs010621.3) unstable; urgency=low + + * Build and install html documentation. (Closes: #106843) + * Remove build-time dependency on libc6-dev. + + -- Ivo Timmermans Mon, 30 Jul 2001 22:03:52 +0200 + +tinc (1.0pre4-1.cvs010621.2) unstable; urgency=low + + * Changed location of the pidfile. (Closes: #102798) + + -- Ivo Timmermans Sun, 1 Jul 2001 01:57:43 +0200 + +tinc (1.0pre4-1.cvs010621.1) unstable; urgency=low + + * New upstream version. (Closes: #98730) + * Rebuilding automatically inserted new config.{sub|guess}. + (Closes: #98165) + * Updated Standards-Version. + * Don't include a sample configuration file. + + -- Ivo Timmermans Thu, 21 Jun 2001 14:08:49 +0200 + +tinc (1.0pre3-5) unstable; urgency=low + + * Fixed an error in the init script that prevented tinc from + starting correctly. + + -- Ivo Timmermans Thu, 8 Feb 2001 02:45:09 +0100 + +tinc (1.0pre3-4) unstable; urgency=low + + * Change build-depends for OpenSSL to libssl096-dev + (Closes: #84197, #84873). + + -- Ivo Timmermans Sun, 4 Feb 2001 22:43:22 +0100 + +tinc (1.0pre3-3) unstable; urgency=low + + * Set architecture to any (really this time!) (Closes: #80451). + * Section set to non-US + + -- Ivo Timmermans Tue, 23 Jan 2001 22:52:53 +0100 + +tinc (1.0pre3-2) unstable; urgency=low + + * Set architecture to any (Closes: #80451). + * Added tinc.modules with some useful module aliases. + + -- Ivo Timmermans Sat, 13 Jan 2001 16:10:57 +0100 + +tinc (1.0pre3-1) unstable; urgency=low + + * New upstream version (1.0pre3) (Closes: #71274). + * Better Depends and Build-Depends lines. + * Dropped dependencies on libgmp, added libssl. + * doc-base.tinc: New file. + * Deleted the file shlibs, as there on longer is a libblowfish. + * Patch po/Makefile.in.in from po-Makefile.in.in.diff if necessary. + * Use dh_perl to get accurate perl dependencies. + + -- Ivo Timmermans Thu, 9 Nov 2000 21:58:40 +0100 + +tinc (1.0pre2-1.1) unstable; urgency=low + + * NMU at Ivo's request as his application is being processed, and his + sponsor is based in the US. + + -- J.H.M. Dassen (Ray) Wed, 28 Jun 2000 21:52:30 +0200 + +tinc (1.0pre2-1) unstable; urgency=low + + * postinst creates a file /etc/tinc/nets.boot, containing all networks + to be started upon system startup; + * init.d script starts all networks from that list. + * postinst script creates tap devices. + + -- Ivo Timmermans Tue, 16 May 2000 00:06:25 +0200 + +tinc (1.0pre1-0.4) unstable; urgency=low + + * postinst script. + + -- Ivo Timmermans Mon, 15 May 2000 19:22:05 +0200 + +tinc (1.0pre1-0.3) unstable; urgency=low + + * system startup script. + + -- Ivo Timmermans Sun, 14 May 2000 22:58:02 +0200 + +tinc (1.0pre1-0.2) unstable; urgency=low + + * Included the blowfish license. + + -- Ivo Timmermans Fri, 21 Apr 2000 17:07:50 +0200 + +tinc (1.0pre1-0.1) unstable; urgency=low + + * Initial Release. + + -- Ivo Timmermans Fri, 21 Apr 2000 17:07:50 +0200 + + --- tinc-1.0.9.orig/debian/control +++ tinc-1.0.9/debian/control @@ -0,0 +1,16 @@ +Source: tinc +Section: net +Priority: optional +Maintainer: Guus Sliepen +Standards-Version: 3.8.0 +Build-Depends: libssl-dev, debhelper (>= 4.1.16), gettext, texi2html, texinfo, zlib1g-dev, cdbs, liblzo2-dev +Homepage: http://www.tinc-vpn.org/ + +Package: tinc +Architecture: any +Depends: debconf | debconf-2.0, ${shlibs:Depends}, ${misc:Depends} +Description: Virtual Private Network daemon + tinc is a daemon with which you can create a virtual private network + (VPN). One daemon can handle multiple connections, so you can + create an entire (moderately sized) VPN with only one daemon per + participating computer. --- tinc-1.0.9.orig/debian/copyright +++ tinc-1.0.9/debian/copyright @@ -0,0 +1,34 @@ +This package was debianized by Ivo Timmermans on +Fri, 21 Apr 2000 17:07:50 +0200. + +It was downloaded from http://www.tinc-vpn.org/ + +Upstream Authors: + Guus Sliepen + Ivo Timmermans + +Copyright (C) 1998-2005 Ivo Timmermans + 1998-2008 Guus Sliepen + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + +On Debian GNU/Linux systems, the complete text of the GNU General Public +License version 2 can be found in /usr/share/common-licenses/GPL-2. + +The following applies to tinc: + +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. + +The following applies to the LZO library: + +Hereby I grant a special exception to the tinc VPN project +(http://tinc.nl.linux.org/) to link the LZO library with the OpenSSL library +(http://www.openssl.org). + +Markus F.X.J. Oberhumer --- tinc-1.0.9.orig/debian/prerm +++ tinc-1.0.9/debian/prerm @@ -0,0 +1,20 @@ +#!/bin/sh + +set -e + +# Automatically added by dh_installinit, edited for use with debconf +if [ -x "/etc/init.d/tinc" ]; then + if [ -e /usr/share/debconf/confmodule ] ; then + . /usr/share/debconf/confmodule + db_get tinc/restart_on_upgrade + if [ "$RET" = "true" ] ; then + invoke-rc.d tinc stop + fi + db_stop + else + invoke-rc.d tinc stop + fi +fi +# End automatically added section + +#DEBHELPER# --- tinc-1.0.9.orig/debian/po/nl.po +++ tinc-1.0.9/debian/po/nl.po @@ -0,0 +1,63 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: tinc_1.0.4-1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-05-04 21:40+0200\n" +"Last-Translator: Guus Sliepen \n" +"Language-Team: Dutch \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "Start tinc opnieuw na iedere upgrade?" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"Je kunt kiezen of ik de tinc daemon opnieuw moet starten iedere keer als je " +"een nieuwe versie van het pakket installeert." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"Soms wil je dit niet doen, bij voorbeeld als je de upgrade uitvoert over een " +"tunnel die met tinc is gemaakt. Het stoppen van tinc resulteert dan " +"waarschijnlijk is een dode verbinding, en tinc wordt dan misschien niet " +"opnieuw gestart." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Als je weigert, moet je zelf tinc opnieuw starten na een upgrade, door" +"`invoke-rc.d tinc restart' in te tiepen wanneer het goed uitkomt." --- tinc-1.0.9.orig/debian/po/POTFILES.in +++ tinc-1.0.9/debian/po/POTFILES.in @@ -0,0 +1 @@ +[type: gettext/rfc822deb] tinc.templates --- tinc-1.0.9.orig/debian/po/templates.pot +++ tinc-1.0.9/debian/po/templates.pot @@ -0,0 +1,56 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=CHARSET\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" --- tinc-1.0.9.orig/debian/po/fr.po +++ tinc-1.0.9/debian/po/fr.po @@ -0,0 +1,62 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: tinc_1.0.3-4\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-02-18 12:42+0100\n" +"Last-Translator: Michel Grentzinger \n" +"Language-Team: French \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-15\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "Faut-il red�marrer tinc � chaque mise � jour�?" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"Vous pouvez choisir de red�marrer le d�mon tinc � chaque fois que vous " +"installez une nouvelle version de ce paquet." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"Dans certains cas, vous devrez �viter de le faire, par exemple si vous " +"mettez � jour � travers un tunnel cr�� avec tinc. Arr�ter le d�mon " +"laisserait sans doute une connexion inactive et tinc ne pourrait pas �tre " +"red�marr�." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Si vous refusez cette option, vous devrez red�marrer tinc vous-m�me en cas " +"de mise � jour, avec la commande�: ��invoke-rc.d tinc restart��, au moment " +"o� cela vous conviendra." --- tinc-1.0.9.orig/debian/po/cs.po +++ tinc-1.0.9/debian/po/cs.po @@ -0,0 +1,63 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: tinc 1.0.4-1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-06-10 22:44+0200\n" +"Last-Translator: Martin Sin \n" +"Language-Team: Czech \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-2\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "Restartovat tinc p�i ka�d� aktualizaci?" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"M��ete zvolit, zda restartovat tinc daemona poka�d�, kdy� je instalov�na " +"nov� verze tohoto bal��ku." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"N�kdy tuto mo�nost nepot�ebujete, nap��klad pokud prov�d�te aktualizaci " +"p�es tunel, kter� je vytvo�en pomoc� tinc. Zastaven� tohoto daemona " +"v�m pravd�podobn� zanech� \"mrtv� p�ipojen�\" a nav�c se tinc nemus� znovu " +"spustit." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Pokud zam�tnete, mus�te po aktualizaci restartovat tinc ru�n�, zad�n�m " +"p��kazu `invoke-rc.d tinc restart' kdykoliv se v�m to hod�." --- tinc-1.0.9.orig/debian/po/vi.po +++ tinc-1.0.9/debian/po/vi.po @@ -0,0 +1,48 @@ +# Vietnamese translation for tinc. +# Copyright © 2005 Free Software Foundation, Inc. +# Clytie Siddall , 2005. +# +msgid "" +msgstr "" +"Project-Id-Version: tinc 1.0.4-2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-08-10 17:13+0930\n" +"Last-Translator: Clytie Siddall \n" +"Language-Team: Vietnamese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0\n" +"X-Generator: LocFactoryEditor 1.2.2\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "Khởi chạy lại trình tinc mỗi lần nâng cấp không?" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "Tại đây bạn có thể chọn tự động khởi chạy lại trình nền (dæmon) tinc mỗi lần bạn cài đặt phiên bản mới của gói này hay không." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "Đôi khi bạn không muốn làm như thế, lấy thí dụ nếu bạn đang nâng cấp qua đường hầm mà tinc tạo. Trong trường hợp này, ngừng trình nền rất có thể sẽ ngắt kết nối, và có lẽ tinc sẽ không khởi chạy lại." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "Nếu bạn từ chối thì bạn cần phải tự khởi chạy lại trình tinc mỗi lần nâng cấp, bằng cách gõ lệnh « invoke-rc.d tinc restart » (gọi-rc.d tinc khởi chạy lại) khi thích hợp." --- tinc-1.0.9.orig/debian/po/ja.po +++ tinc-1.0.9/debian/po/ja.po @@ -0,0 +1,49 @@ +msgid "" +msgstr "" +"Project-Id-Version: tinc 1.0.4-1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-06-14 21:09+0900\n" +"Last-Translator: Atsushi Shimono \n" +"Language-Team: Japanese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=EUC-JP\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "��åץ��졼�ɤΤ��Ӥ� tinc ��Ƶ�ư��ޤ��" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"��Υѥå��ο��С��򥤥󥹥ȡ��뤹�뤿�Ӥˡ�tinc �ǡ��" +"�Ƶ�ư��뤫�ɤ��Ǥ��ޤ��" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"tinc �Υȥ�ͥ��ͳ��ƥ��åץ��졼�ɤ�ԤäƤ��Ȥ��ʤɡ��Ԥ�" +"��ʤ��Ȥ��Ȼפ��ޤ��ǡ��ߤ�뤳�Ȥ��³��졢tinc " +"��Ƶ�ư��ʤ��ʤ�ޤ��" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"��򤷤ʤ��硢��åץ��졼�ɤ�Ԥä��ݡ��Թ礬�ɤ��Ȥ�� " +"'invoke-rc.d tinc restart' ��¹Ԥ�� tinc ��ʬ�ǺƵ�ư��ɬ�פ��ޤ��" --- tinc-1.0.9.orig/debian/po/sv.po +++ tinc-1.0.9/debian/po/sv.po @@ -0,0 +1,62 @@ +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# Developers do not need to manually edit POT or PO files. +# , fuzzy +# +# +msgid "" +msgstr "" +"Project-Id-Version: tinc 1.0.4-3\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2004-11-11 20:06+0000\n" +"PO-Revision-Date: 2005-10-10 22:06+0200\n" +"Last-Translator: Daniel Nylander \n" +"Language-Team: Swedish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=iso-8859-1\n" +"Content-Transfer-Encoding: 8bit" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "Restart tinc on each upgrade?" +msgstr "Starta om tinc vid varje uppgradering?" + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"Du kan v�lja om du vill att jag startar om tinc-daemonen varje g�ng du installerar en " +"ny version av detta paket." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"Ibland vill du kanske inte g�ra detta, till exempel om du g�r en uppgradering " +"via en tunnel som �r skapad med tinc. Stoppa daemonen skulle antagligen koppla ner " +"f�rbindelsen och tinc kan inte startas igen." + +#. Type: boolean +#. Description +#: ../tinc.templates:4 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Om du v�grar m�ste du starta om tinc sj�lv om du uppgraderat, genom att skriva " +"'invoke-rc.d tinc restart' n�r det passar dig." + --- tinc-1.0.9.orig/debian/po/de.po +++ tinc-1.0.9/debian/po/de.po @@ -0,0 +1,55 @@ +# Translation of tinc debconf templates to German +# Copyright (C) Helge Kreutzmann , 2007. +# This file is distributed under the same license as the tinc package. +# +msgid "" +msgstr "" +"Project-Id-Version: tinc 1.0.7-1\n" +"Report-Msgid-Bugs-To: tinc@packages.debian.org\n" +"POT-Creation-Date: 2007-01-13 20:22+0100\n" +"PO-Revision-Date: 2007-02-25 16:43+0100\n" +"Last-Translator: Helge Kreutzmann \n" +"Language-Team: German \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-15\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "Restart tinc on each upgrade?" +msgstr "Tinc bei jedem Upgrade neu starten?" + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"Sie k�nnen dies ausw�hlen, falls Sie m�chten, dass jedes mal, wenn Sie eine " +"neue Version installieren, Tinc neu gestartet werden soll." + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"In manchen Situationen ist dies nicht gewollt, zum Beispiel falls Sie das " +"Upgrade �ber einen Tunnel durchf�hren, der mit Tinc erstellt wurde. W�rde " +"dann der Daemon beendet, w�re die Kommunikation tot und Tinc k�nnte sich " +"nicht neu starten." + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Falls Sie hier ablehnen, m�ssen Sie Tinc selbst neu starten, wenn Sie ein " +"Upgrade durchgef�hrt haben, indem Sie �invoke-rc.d tinc restart� eingeben, " +"wenn es Ihnen passt." --- tinc-1.0.9.orig/debian/po/pt.po +++ tinc-1.0.9/debian/po/pt.po @@ -0,0 +1,56 @@ +# translation of tinc debconf to Portuguese +# Copyright (C) 2007 Américo Monteiro +# This file is distributed under the same license as the tinc package. +# +# Américo Monteiro , 2007. +msgid "" +msgstr "" +"Project-Id-Version: tinc_1.0.8-1_templates\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-05-25 04:46+0200\n" +"PO-Revision-Date: 2007-07-21 16:38+0100\n" +"Last-Translator: Américo Monteiro \n" +"Language-Team: Portuguese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "Restart tinc on each upgrade?" +msgstr "Reiniciar o tinc em cada actualização?" + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"You may choose if you want me to restart the tinc daemon every time you " +"install a new version of this package." +msgstr "" +"Você pode escolher se quer eu reinicie o serviço tinc toda a vez que instalar " +"uma nova versão deste pacote." + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"Sometimes you don't want to do this, for example if you are doing the " +"upgrade over a tunnel that is created with tinc. Stopping the daemon would " +"probably leave you with a dead connection, and tinc may not be started again." +msgstr "" +"Por vezes você não querer que isto aconteça, por exemplo, se estiver a fazer " +"a actualização por um túnel que é criado pelo tinc. Parando o serviço iria provavelmente " +"deixá-lo com uma ligação morta, e o tinc poderia não arrancar de novo." + +#. Type: boolean +#. Description +#: ../tinc.templates:1001 +msgid "" +"If you refuse, you have to restart tinc yourself if you upgraded, by typing " +"`invoke-rc.d tinc restart' whenever it suits you." +msgstr "" +"Se recusar, terá que ser você a reiniciar o tinc se o actualizar, escrevendo " +"'invoke-rc.d tinc restart' ou outro comando que lhe sirva." +

1.1 Virtual Private Networks		+
1.2 tinc		About tinc +
1.3 Supported platforms		+

1. Introduction

1.1 Virtual Private Networks

1.2 tinc

1.3 Supported platforms

2. Preparations

2.1 Configuring the kernel

2.1.1 Configuration of Linux kernels

2.1.2 Configuration of FreeBSD kernels

2.1.3 Configuration of OpenBSD kernels

2.1.4 Configuration of NetBSD kernels

2.1.5 Configuration of Solaris kernels

2.1.6 Configuration of Darwin (MacOS/X) kernels

2.1.7 Configuration of Windows

2.2 Libraries

2.2.1 OpenSSL

License

2.2.2 zlib

2.2.3 lzo

3. Installation

3.1 Building and installing tinc

3.1.1 Darwin (MacOS/X) build environment

3.1.2 Cygwin (Windows) build environment

3.1.3 MinGW (Windows) build environment

3.2 System files

3.2.1 Device files

3.2.2 Other files

‘/etc/networks’

‘/etc/services’

4. Configuration

4.1 Configuration introduction

4.2 Multiple networks

4.3 How connections work

4.4 Configuration files

4.4.1 Main configuration variables

4.4.2 Host configuration variables

4.4.3 Scripts

4.4.4 How to configure

Step 1. Creating the main configuration file

Step 2. Creating your host configuration file

4.5 Generating keypairs

4.6 Network interfaces

4.7 Example configuration

For Branch A

For Branch B

For Branch C

For Branch D

Key files

Starting

5. Running tinc

5.1 Runtime options

5.2 Signals

5.3 Debug levels

5.4 Solving problems

5.5 Error messages

5.6 Sending bug reports

6. Technical information

6.1 The connection

6.1.1 The UDP tunnel

6.1.2 The meta-connection

6.2 The meta-protocol

6.3 Security

6.3.1 Authentication protocol

6.3.2 Encryption of network packets

6.3.3 Security issues

7. Platform specific information

‘`/etc/networks`’

‘`/etc/services`’