tinc/debian
Guus Sliepen c14863878e Release 1.0.36-2 for unstable 2020-11-22 10:40:54 +01:00
..
patches Import Debian changes 1.0.34-1 2019-08-26 13:44:48 +02:00
source Import Debian changes 1.0.13-1 2019-08-26 13:44:40 +02:00
upstream Import Debian changes 1.0.24-1 2019-08-26 13:44:45 +02:00
NEWS Import Debian changes 1.0.27-1 2019-08-26 13:44:46 +02:00
README.Debian Import Debian changes 1.0.27-1 2019-08-26 13:44:46 +02:00
changelog Release 1.0.36-2 for unstable 2020-11-22 10:40:54 +01:00
control Disable support for livdeplug. 2020-11-22 10:40:00 +01:00
copyright Import Debian changes 1.0.9-1 2019-08-26 13:44:38 +02:00
doc-base.tinc Import Debian changes 1.0.22-1~bpo70+1 2019-08-26 13:44:44 +02:00
info Import Debian changes 1.0pre7-2 2019-08-26 13:44:36 +02:00
postinst Import Debian changes 1.0.32-1 2019-08-26 13:44:48 +02:00
postrm Import Debian changes 1.0.13-1 2019-08-26 13:44:40 +02:00
preinst Import Debian changes 1.0.27-1 2019-08-26 13:44:46 +02:00
rules Disable support for livdeplug. 2020-11-22 10:40:00 +01:00
tinc.default Import Debian changes 1.0.24-1 2019-08-26 13:44:45 +02:00
tinc.dirs Import Debian changes 1.0.3-4 2019-08-26 13:44:36 +02:00
tinc.docs Import Debian changes 1.0.3-4 2019-08-26 13:44:36 +02:00
tinc.files Import Debian changes 1.0.3-4 2019-08-26 13:44:36 +02:00
tinc.if-post-down Import Debian changes 1.0.32-1 2019-08-26 13:44:48 +02:00
tinc.if-pre-up Import Debian changes 1.0.33-1 2019-08-26 13:44:48 +02:00
tinc.if-up Import Debian changes 1.0.23-2 2019-08-26 13:44:45 +02:00
tinc.init Import Debian changes 1.0.32-1 2019-08-26 13:44:48 +02:00
watch Import Debian changes 1.0.24-1 2019-08-26 13:44:45 +02:00

README.Debian

tinc for Debian
---------------

The manual for tinc is also available as info pages, type `info tinc'
to read it.

There are several ways in which tinc may be automatically started at boot:

Systemd
-------

Since 1.0.27-1, the tinc package comes with native systemd service files.
To enable and start a net, call:

systemctl enable tinc@<netname>
systemctl start tinc@<netname>

This will cause a tincd to be started which uses the configuration from
/etc/tinc/<netname>, and also makes sure that it will be started next time your
system boots.

Apart from controlling individual instances, you can also start/stop/reload all
enabled instances simultaneously by omitting @<netname>, for example:

systemctl reload tinc

Note that when you have systemd installed on your system, the file
/etc/tinc/nets.boot will not be used anymore to automatically start tinc
daemons. If the variable EXTRA is defined in /etc/default/tinc, it will be
passed on to tinc. The variable LIMITS is however not used.

The service files that come with this package start tinc unconditionally.
However, tinc does support socket activation. If you wish to write a socket
unit for tinc, use the ListenStream option to specify on which port(s) and
address(es) tinc should listen.

SysVinit
--------

The system startup script for tinc, /etc/init.d/tinc, uses the file
/etc/tinc/nets.boot to find out which networks have to be started. Use one
netname per line. Lines starting with a # are ignored.

/etc/network/interfaces
-----------------------

You can create a stanza in /etc/network/interfaces, and add a line with
"tinc-net <netname>". This will cause a tincd to be started which uses the
configuration from /etc/tinc/<netname>. You can use an inet static (with
address and netmask options) or inet dhcp stanza, in which case the ifup will
configure the VPN interface and you do not need to have a tinc-up script.

The following options are also recognized and map directly to the corresponding
command line options for tincd:

tinc-config <directory>
tinc-debug <level>
tinc-mlock yes
tinc-logfile <filename>
tinc-pidfile <filename>
tinc-chroot yes
tinc-user <username>

An example stanza:

iface vpn inet static
	address 192.168.2.42
	netmask 255.255.0.0
	tinc-net myvpn
	tinc-debug 1
	tinc-mlock yes
	tinc-user nobody
	tinc-pidfile /tmp/tinc.pid

This will start a tinc daemon that reads its configuration from
/etc/tinc/myvpn, logs at debug level 1, locks itself in RAM, runs as user
nobody, and creates a network interface called "vpn". Ifup then sets the
address and netmask on that interface.

 -- Guus Sliepen <guus@debian.org>, Sun, 10 April 2016, 01:38:08 +0200