ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/doc/vped.conf.5
(Generate patch)

Comparing gvpe/doc/vped.conf.5 (file contents):
Revision 1.1 by pcg, Sat Mar 1 15:53:02 2003 UTC vs.
Revision 1.6 by pcg, Fri Mar 28 18:19:14 2003 UTC

1.Dd 2002-04-09 1.\" Automatically generated by Pod::Man v1.36, Pod::Parser v1.13
2.Dt TINC.CONF 5 2.\"
3.\" Manual page created by: 3.\" Standard preamble:
4.\" Ivo Timmermans <ivo@o2w.nl> 4.\" ========================================================================
5.\" Guus Sliepen <guus@sliepen.eu.org> 5.de Sh \" Subsection heading
6.Sh NAME 6.br
7.Nm tinc.conf 7.if t .Sp
8.Nd tinc daemon configuration 8.ne 5
9.PP
10\fB\\$1\fR
11.PP
12..
13.de Sp \" Vertical space (when we can't use .PP)
14.if t .sp .5v
15.if n .sp
16..
17.de Vb \" Begin verbatim text
18.ft CW
19.nf
20.ne \\$1
21..
22.de Ve \" End verbatim text
23.ft R
24.fi
25..
26.\" Set up some character translations and predefined strings. \*(-- will
27.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
28.\" double quote, and \*(R" will give a right double quote. | will give a
29.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
30.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
31.\" expand to `' in nroff, nothing in troff, for use with C<>.
32.tr \(*W-|\(bv\*(Tr
33.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
34.ie n \{\
35. ds -- \(*W-
36. ds PI pi
37. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
38. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
39. ds L" ""
40. ds R" ""
41. ds C`
42. ds C'
43'br\}
44.el\{\
45. ds -- \|\(em\|
46. ds PI \(*p
47. ds L" ``
48. ds R" ''
49'br\}
50.\"
51.\" If the F register is turned on, we'll generate index entries on stderr for
52.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
53.\" entries marked with X<> in POD. Of course, you'll have to process the
54.\" output yourself in some meaningful fashion.
55.if \nF \{\
56. de IX
57. tm Index:\\$1\t\\n%\t"\\$2"
58..
59. nr % 0
60. rr F
61.\}
62.\"
63.\" For nroff, turn off justification. Always turn off hyphenation; it makes
64.\" way too many mistakes in technical documents.
65.hy 0
66.if n .na
67.\"
68.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
69.\" Fear. Run. Save yourself. No user-serviceable parts.
70. \" fudge factors for nroff and troff
71.if n \{\
72. ds #H 0
73. ds #V .8m
74. ds #F .3m
75. ds #[ \f1
76. ds #] \fP
77.\}
78.if t \{\
79. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
80. ds #V .6m
81. ds #F 0
82. ds #[ \&
83. ds #] \&
84.\}
85. \" simple accents for nroff and troff
86.if n \{\
87. ds ' \&
88. ds ` \&
89. ds ^ \&
90. ds , \&
91. ds ~ ~
92. ds /
93.\}
94.if t \{\
95. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
96. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
97. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
98. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
99. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
100. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
101.\}
102. \" troff and (daisy-wheel) nroff accents
103.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
104.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
105.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
106.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
107.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
108.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
109.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
110.ds ae a\h'-(\w'a'u*4/10)'e
111.ds Ae A\h'-(\w'A'u*4/10)'E
112. \" corrections for vroff
113.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
114.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
115. \" for low resolution devices (crt and lpr)
116.if \n(.H>23 .if \n(.V>19 \
117\{\
118. ds : e
119. ds 8 ss
120. ds o a
121. ds d- d\h'-1'\(ga
122. ds D- D\h'-1'\(hy
123. ds th \o'bp'
124. ds Th \o'LP'
125. ds ae ae
126. ds Ae AE
127.\}
128.rm #[ #] #H #V #F C
129.\" ========================================================================
130.\"
131.IX Title "VPED.CONF 5"
132.TH VPED.CONF 5 "2003-03-28" "0.1" "Virtual Private Ethernet"
133.SH "NAME"
134vped.conf \- vpe daemon configuration file
135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS"
137.Vb 3
138\& udp-port = 407
139\& mtu = 1492
140\& ifname = vpn0
141.Ve
142.PP
143.Vb 2
144\& node = branch1
145\& hostname = 1.2.3.4
146.Ve
147.PP
148.Vb 3
149\& node = branch2
150\& hostname = www.example.net
151\& udp-port = 500 # this host uses a different udp-port
152.Ve
153.PP
154.Vb 2
155\& node = branch3
156\& connect = ondemand
157.Ve
9.Sh DESCRIPTION 158.SH "DESCRIPTION"
10The files in the 159.IX Header "DESCRIPTION"
11.Pa /etc/tinc/ 160The vpe config file consists of a series of lines that contain \f(CW\*(C`variable
12directory contain runtime and security information for the tinc daemon. 161= value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and
13.Sh NETWORKS 162extend to the end of the line. They can be used on their own lines, or
14It is perfectly ok for you to run more than one tinc daemon. 163after any directives. Spaces are allowed before or after the \f(CW\*(C`=\*(C'\fR sign or
15However, in its default form, 164after values, but not within the variable names or values themselves.
16you will soon notice that you can't use two different configuration files without the 165.PP
17.Fl c 166The only exception to the above is the \*(L"on\*(R" directive that can prefix any
18option. 167\&\f(CW\*(C`name = value\*(C'\fR setting and will only \*(L"execute\*(R" it on the named node, or
19.Pp 168(if the nodename starts with \*(L"!\*(R") on all nodes except the named one.
20We have thought of another way of dealing with this: network names. 169.PP
21This means that you call 170.Vb 3
22.Nm 171\& name = value
23with the 172\& on branch1 loglevel = noise
24.Fl n 173\& on !branch2 connect = ondemand
25option, which will assign a name to this daemon. 174.Ve
26.Pp 175.PP
27The effect of this is that the daemon will set its configuration root to 176All settings are executed \*(L"in order\*(R", that is, later settings of the same
28.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa / , 177variable overwrite earlier ones.
29where 178.SH "ANATOMY OF A CONFIG FILE"
30.Ar NETNAME 179.IX Header "ANATOMY OF A CONFIG FILE"
31is your argument to the 180Usually, a config file starts with global settings (like the udp port to
32.Fl n 181listen on), followed by node-specific sections that begin with a \f(CW\*(C`node =
33option. 182nickname\*(C'\fR line.
34You'll notice that messages appear in syslog as coming from 183.PP
35.Nm tincd. Ns Ar NETNAME . 184Every node that is part of the network must have a section that starts
36.Pp 185with \f(CW\*(C`node = nickname\*(C'\fR. The number and order of the nodes is important
37However, it is not strictly necessary that you call tinc with the 186and must be the same on all hosts. It is not uncommon for node sections to
38.Fl n 187be completely empty \- if the default values are right.
39option. 188.PP
40In this case, the network name would just be empty, 189Node-specific settings can be used at any time. If used before the first
41and it will be used as such. 190node section they will set the default values for all following nodes.
42.Nm tinc 191.SH "CONFIG VARIABLES"
43now looks for files in 192.IX Header "CONFIG VARIABLES"
44.Pa /etc/tinc/ , 193.Sh "\s-1GLOBAL\s0 \s-1SETTINGS\s0"
45instead of 194.IX Subsection "GLOBAL SETTINGS"
46.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa / ; 195Global settings will affect the behaviour of the running vped daemon, that
47the configuration file should be 196is, they are in some sense node-specific (config files can set different
48.Pa /etc/tinc/tinc.conf , 197values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of
49and the host configuration files are now expected to be in 198the vped daemon and all connections it creates.
50.Pa /etc/tinc/hosts/ . 199.IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4
51.Pp 200.IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical"
52But it is highly recommended that you use this feature of 201Set the logging level. Connection established messages are logged at level
53.Nm tinc , 202\&\f(CW\*(C`info\*(C'\fR, notable errors are logged with \f(CW\*(C`error\*(C'\fR. Default is \f(CW\*(C`info\*(C'\fR.
54because it will be so much clearer whom your daemon talks to. 203.IP "node = nickname" 4
55Hence, we will assume that you use it. 204.IX Item "node = nickname"
56.Sh NAMES 205Not really a config setting but introduces a node section. The nickname is
57Each tinc daemon should have a name that is unique in the network which it will be part of. 206used to select the right configuration section and must be passed as an
58The name will be used by other tinc daemons for identification. 207argument to the vped daemon.
59The name has to be declared in the 208.IP "private-key = relative-path-to-key" 4
60.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /tinc.conf 209.IX Item "private-key = relative-path-to-key"
61file. 210Sets the path (relative to the config directory) to the private key
62.Pp 211(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must
63To make things easy, 212be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could
64choose something that will give unique and easy to remember names to your tinc daemon(s). 213use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where
65You could try things like hostnames, owner surnames or location names. 214\&\f(CW\*(C`vpectrl\*(C'\fR puts them.
66.Sh PUBLIC/PRIVATE KEYS 215.Sp
67You should use 216Since only the private key file of the current node is used and the
68.Ic tincd -K 217private key file should be kept secret per-host to avoid spoofings, it is
69to generate public/private keypairs. 218not recommended to use this feature.
70It will generate two keys. 219.IP "ifpersist = yes|true|on | no|false|off" 4
71The private key should be stored in a separate file 220.IX Item "ifpersist = yes|true|on | no|false|off"
72.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /rsa_key.priv 221Should the tun/tap device be made persistent, that is, should the device
73\-\- where 222stay up even when vped exits? Some versions of the tunnel device have
74.Ar NETNAME 223problems sending packets when vped is restarted in persistent mode, so
75stands for the network (see 224if the connections can be established but you cannot send packets from
76.Sx NETWORKS ) 225the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the
77above. 226device.
78The public key should be stored in the host configuration file 227.IP "ifname = devname" 4
79.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /hosts/ Ns Va NAME 228.IX Item "ifname = devname"
80\-\- where 229Sets the tun interface name to the given name. The default is OS-specific
81.Va NAME 230and most probably something like \f(CW\*(C`tun0\*(C'\fR.
82stands for the name of the local tinc daemon (see 231.IP "rekey = seconds" 4
83.Sx NAMES ) . 232.IX Item "rekey = seconds"
84.Sh SERVER CONFIGURATION 233Sets the rekeying interval in seconds (default: \f(CW3600\fR). Connections are
85The server configuration of the daemon is done in the file 234reestablished every \f(CW\*(C`rekey\*(C'\fR seconds.
86.Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /tinc.conf . 235.IP "keepalive = seconds" 4
87This file consists of comments (lines started with a 236.IX Item "keepalive = seconds"
88.Li # ) 237Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this
89or assignments in the form of: 238many seconds of inactivity the daemon will start to send keepalive probe
90.Pp 239every 5 seconds until it receives a reply from the other end. If no reply
91.Va Variable Li = Ar Value . 240is received within 30 seconds, the peer is considered unreachable and the
92.Pp 241connection is closed.
93The variable names are case insensitive, and any spaces, tabs, 242.IP "mtu = bytes" 4
94newlines and carriage returns are ignored. 243.IX Item "mtu = bytes"
95Note: it is not required that you put in the 244Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically
96.Li = 245the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate
97sign, but doing so improves readability. 246maximum overhead (e.g. udp header size, encryption blocksize...) and pass
98If you leave it out, remember to replace it with at least one space character. 247this information to the \f(CW\*(C`if\-up\*(C'\fR script.
99.Pp 248.Sp
100Here are all valid variables, listed in alphabetical order. 249Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp).
101The default value is given between parentheses. 250.Sp
102.Bl -tag -width indent 251This value must be the minimum of the mtu values of all hosts.
103.It Va AddressFamily Li = ipv4 | ipv6 | any Po ipv4 Pc Bq experimental 252.IP "ip-proto = numerical-ip-protocol" 4
104This option affects the address family of listening and outgoing sockets. 253.IX Item "ip-proto = numerical-ip-protocol"
105If 254Sets the protocol number to be used for the rawip protocol. This is a
106.Qq any 255global option because all hosts must use the same protocol, and since
107is selected, then depending on the operating system both IPv4 and IPv6 or just 256there are no port numbers, you cannot easily run more than one vped
108IPv6 listening sockets will be created. 257instance using the same protocol, nor can you share the protocol with
109.It Va BindToInterface Li = Ar interface Bq experimental 258other programs.
110If your computer has more than one network interface, 259.Sp
111.Nm tinc 260The default is 47 (\s-1GRE\s0), which has a good chance of tunneling through
112will by default listen on all of them for incoming connections. 261firewalls (but note that the rawip protocol is not \s-1GRE\s0 compatible). Other
113It is possible to bind only to a single interface with this variable. 262common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 (\s-1IPIP\s0 tunnels) or 98
114.Pp 263(\s-1ENCAP\s0, rfc1241)
115This option may not work on all platforms. 264.IP "enable-udp = yes|true|on | no|false|off" 4
116.It Va ConnectTo Li = Ar name 265.IX Item "enable-udp = yes|true|on | no|false|off"
117Specifies which other tinc daemon to connect to on startup. 266Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port
118Multiple 267(default: \f(CW\*(C`yes\*(C'\fR). This is a good general choice since \s-1UDP\s0 tunnels well
119.Va ConnectTo 268through many firewalls.
120variables may be specified, 269.IP "enable-rawip = yes|true|on | no|false|off" 4
121in which case outgoing connections to each specified tinc daemon are made. 270.IX Item "enable-rawip = yes|true|on | no|false|off"
122The names should be known to this tinc daemon 271Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol
123(i.e., there should be a host configuration file for the name on the 272(default: \f(CW\*(C`no\*(C'\fR). This is the best choice, since the overhead per packet
124.Va ConnectTo 273is only 38 bytes, as opposed to \s-1UDP\s0's 58 (or \s-1TCP\s0's 60+).
125line). 274.IP "if-up = relative-or-absolute-path" 4
126.Pp 275.IX Item "if-up = relative-or-absolute-path"
127If you don't specify a host with 276Sets the path of a script that should be called immediately after the
128.Va ConnectTo , 277network interface is initialized (but not neccessarily up). The following
129.Nm tinc 278environment variables are passed to it (the values are just examples):
130won't try to connect to other daemons at all, 279.RS 4
131and will instead just listen for incoming connections. 280.IP "CONFBASE=/etc/vpe" 4
132.It Va Device Li = Ar device Po /dev/tap0 or /dev/net/tun Pc 281.IX Item "CONFBASE=/etc/vpe"
133The virtual network device to use. 282The configuration base directory.
134.Nm tinc 283.IP "IFNAME=vpn0" 4
135will automatically detect what kind of device it is. 284.IX Item "IFNAME=vpn0"
136Note that you can only use one device per daemon. 285The interface to initialize.
137The info pages of the tinc package contain more information 286.IP "MTU=1436" 4
138about configuring the virtual network device. 287.IX Item "MTU=1436"
139.It Va Hostnames Li = yes | no Pq no 288The \s-1MTU\s0 to set the interface to. You can use lower values (if done
140This option selects whether IP addresses (both real and on the VPN) should 289consistently on all hosts), but this is usually ineffective.
141be resolved. Since DNS lookups are blocking, it might affect tinc's 290.IP "MAC=fe:fd:80:00:00:01" 4
142efficiency, even stopping the daemon for a few seconds every time it does 291.IX Item "MAC=fe:fd:80:00:00:01"
143a lookup if your DNS server is not responding. 292The \s-1MAC\s0 address to set the interface to. The script *must* set the
144.Pp 293interface \s-1MAC\s0 to this value. On GNU/Linux you will most likely use this:
145This does not affect resolving hostnames to IP addresses from the 294.Sp
146host configuration files. 295.Vb 1
147.It Va Interface Li = Ar interface 296\& ip link set $IFNAME address $MAC mtu $MTU up
148Defines the name of the interface corresponding to the virtual network device. 297.Ve
149Depending on the operating system and the type of device this may or may not actually set the name. 298.IP "NODENAME=branch1" 4
150Currently this option only affects the Linux tun/tap device. 299.IX Item "NODENAME=branch1"
151.It Va KeyExpire Li = Ar period Pq 3600 300The nickname of the current node, as passed to the vped daemon.
152This option controls the period the encryption keys used to encrypt the data are valid. 301.IP "NODEID=1" 4
153It is common practice to change keys at regular intervals to make it even harder for crackers, 302.IX Item "NODEID=1"
154even though it is thought to be nearly impossible to crack a single key. 303The numerical node id of the current node. The first node mentioned in the
155.It Va MACExpire Li = Ar period Pq 600 304config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on.
156This option controls the amount of time MAC addresses are kept before they are removed. 305.RE
157This only has effect when 306.RS 4
158.Va Mode 307.Sp
159is set to 308Here is a simple if-up script:
160.Qq switch . 309.Sp
161.It Va MaxTimeout Li = Ar period Pq 900 310.Vb 5
162This is the maximum delay before trying to reconnect to other tinc daemons. 311\& #!/bin/sh
163.It Va Mode Li = router | switch | hub Pq router 312\& ip link set $IFNAME address $MAC mtu $MTU up
164This option selects the way packets are routed to other daemons. 313\& [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME
165.Bl -tag -width indent 314\& [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME
166.It router 315\& ip route add 10.0.0.0/8 dev $IFNAME
167In this mode 316.Ve
168.Va Subnet 317.Sp
169variables in the host configuration files will be used to form a routing table. 318More complicated examples (using routing to reduce arp traffic) can be
170Only unicast packets of routable protocols (IPv4 and IPv6) are supported in this mode. 319found in the etc/ subdirectory of the distribution.
171.It switch 320.RE
172In this mode the MAC addresses of the packets on the VPN will be used to 321.IP "node-up = relative-or-absolute-path" 4
173dynamically create a routing table just like an Ethernet switch does. 322.IX Item "node-up = relative-or-absolute-path"
174Unicast, multicast and broadcast packets of every protocol that runs over Ethernet are supported in this mode 323Sets a command (default: no script) that should be called whenever a
175at the cost of frequent broadcast ARP requests and routing table updates. 324connection is established (even on rekeying operations). In addition
176.It hub 325to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment
177This mode is almost the same as the switch mode, but instead 326variables will be set:
178every packet will be broadcast to the other daemons 327.RS 4
179while no routing table is managed. 328.IP "DESTNODE=branch2" 4
180.El 329.IX Item "DESTNODE=branch2"
181.It Va Name Li = Ar name Bq required 330The name of the remote node.
182This is the name which identifies this tinc daemon. 331.IP "DESTID=2" 4
183It must be unique for the virtual private network this daemon will connect to. 332.IX Item "DESTID=2"
184.It Va PingTimeout Li = Ar period Pq 60 333The node id of the remote node.
185The number of seconds of inactivity that 334.IP "DESTIP=188.13.66.8" 4
186.Nm tinc 335.IX Item "DESTIP=188.13.66.8"
187will wait before sending a probe to the other end. 336The numerical \s-1IP\s0 address of the remote host (vped accepts connections from
188If that other end doesn't answer within that same amount of time, 337everywhere, as long as the other host can authenticate itself).
189the connection is terminated, 338.IP "DESTPORT=407 # deprecated" 4
190and the others will be notified of this. 339.IX Item "DESTPORT=407 # deprecated"
191.It Va PriorityInheritance Li = yes | no Po no Pc Bq experimental 340The \s-1UDP\s0 port used by the other side.
192When this option is enabled the value of the TOS field of tunneled IPv4 packets 341.IP "STATE=UP" 4
193will be inherited by the UDP packets that are sent out. 342.IX Item "STATE=UP"
194.It Va PrivateKey Li = Ar key Bq obsolete 343Node-up scripts get called with STATE=UP, node-down scripts get called
195The private RSA key of this tinc daemon. 344with STATE=DOWN.
196It will allow this tinc daemon to authenticate itself to other daemons. 345.RE
197.It Va PrivateKeyFile Li = Ar filename Bq recommended 346.RS 4
198The file in which the private RSA key of this tinc daemon resides. 347.Sp
199Note that there must be exactly one of 348Here is a nontrivial example that uses nsupdate to update the name => ip
200.Va PrivateKey 349mapping in some dns zone:
201or 350.Sp
202.Va PrivateKeyFile 351.Vb 6
203specified in the configuration file. 352\& #!/bin/sh
204.El 353\& {
205.Sh HOST CONFIGURATION FILES 354\& echo update delete $DESTNODE.lowttl.example.net. a
206The host configuration files contain all information needed 355\& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP
207to establish a connection to those hosts. 356\& echo
208A host configuration file is also required for the local tinc daemon, 357\& } | nsupdate -d -k $CONFBASE:key.example.net.
209it will use it to read in it's listen port, public key and subnets. 358.Ve
210.Pp 359.RE
211The idea is that these files are portable. 360.IP "node-down = relative-or-absolute-path" 4
212You can safely mail your own host configuration file to someone else. 361.IX Item "node-down = relative-or-absolute-path"
213That other person can then copy it to his own hosts directory, 362Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost.
214and now his tinc daemon will be able to connect to your tinc daemon. 363.Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0"
215Since host configuration files only contain public keys, 364.IX Subsection "NODE SPECIFIC SETTINGS"
216no secrets are revealed by sending out this information. 365The following settings are node\-specific, that is, every node can have
217.Bl -tag -width indent 366different settings, even within the same vped instance. Settings that are
218.It Va Address Li = Ar address Bq recommended 367executed before the first node section set the defaults, settings that are
219The IP address or hostname of this tinc daemon on the real network. 368executed within a node section only apply to the given node.
220This wil only be used when trying to make an outgoing connection to this tinc daemon. 369.IP "udp-port = port-number" 4
221Multiple 370.IX Item "udp-port = port-number"
222.Va Address 371Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW407\fR, not
223variables can be specified, in which case each address will be tried until a working 372officially assigned by \s-1IANA\s0!).
224connection has been established. 373.IP "router-priority = positive-number" 4
225.It Va Cipher Li = Ar cipher Pq blowfish 374.IX Item "router-priority = positive-number"
226The symmetric cipher algorithm used to encrypt UDP packets. 375Sets the router priority of the given host (default: \f(CW0\fR, disabled). If
227Any cipher supported by OpenSSL is recognised. 376some host tries to connect to another host without a hostname, it asks
228Furthermore, specifying 377the router host for it's \s-1IP\s0 address. The router host is the one with the
229.Qq none 378highest priority that is currently reachable. Make sure all clients always
230will turn off packet encryption. 379connect to the router hosts, otherwise conencting to them is impossible.
231.It Va Compression Li = Ar level Pq 0 380.IP "connect = ondemand|never|always|disabled" 4
232This option sets the level of compression used for UDP packets. 381.IX Item "connect = ondemand|never|always|disabled"
233Possible values are 0 (off), 1 (fast) and any integer up to 9 (best). 382Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always
234.It Va Digest Li = Ar digest Pq sha1 383try to establish and keep a conenction to the given host), \f(CW\*(C`never\*(C'\fR
235The digest algorithm used to authenticate UDP packets. 384(nevr initiate a connection to the given host, but accept connections),
236Any digest supported by OpenSSL is recognised. 385\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and
237Furthermore, specifying 386take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad,
238.Qq none 387don't talk to it).
239will turn off packet authentication. 388.IP "inherit-tos = yes|true|on | no|false|off" 4
240.It Va IndirectData Li = yes | no Pq no 389.IX Item "inherit-tos = yes|true|on | no|false|off"
241This option specifies whether other tinc daemons besides the one you specified with 390Wether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
242.Va ConnectTo 391sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then
243can make a direct connection to you. 392outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent
244This is especially useful if you are behind a firewall 393to the tunnel device, which is usually what you want.
245and it is impossible to make a connection from the outside to your tinc daemon. 394.IP "compress = yes|true|on | no|false|off" 4
246Otherwise, it is best to leave this option out or set it to no. 395.IX Item "compress = yes|true|on | no|false|off"
247.It Va MACLength Li = Ar length Pq 4 396Wether to compress data packets sent to this host (default: \f(CW\*(C`yes\*(C'\fR).
248The length of the message authentication code used to authenticate UDP packets. 397Compression is really cheap even on slow computers and has no size
249Can be anything from 398overhead at all, so enabling this is a good idea.
250.Qq 0 399.SH "CONFIG DIRECTORY LAYOUT"
251up to the length of the digest produced by the digest algorithm. 400.IX Header "CONFIG DIRECTORY LAYOUT"
252.It Va Port Li = Ar port Pq 655 401The default (or recommended) directory layout for the config directory is:
253The port number on which this tinc daemon is listening for incoming connections. 402.IP "vped.conf" 4
254.It Va PublicKey Li = Ar key Bq obsolete 403.IX Item "vped.conf"
255The public RSA key of this tinc daemon. 404The config file.
256It will be used to cryptographically verify it's identity and to set up a secure connection. 405.IP "if-up" 4
257.It Va PublicKeyFile Li = Ar filename Bq obsolete 406.IX Item "if-up"
258The file in which the public RSA key of this tinc daemon resides. 407The if-up script
259.Pp 408.IP "node\-up, node-down" 4
260From version 1.0pre4 on 409.IX Item "node-up, node-down"
261.Nm tinc 410If used the node up or node-down scripts.
262will store the public key directly into the host configuration file in PEM format, 411.IP "hostkey" 4
263the above two options then are not necessary. 412.IX Item "hostkey"
264Either the PEM format is used, or exactly one of the above two options must be specified 413The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host.
265in each host configuration file, 414.IP "pubkey/nodename" 4
266if you want to be able to establish a connection with that host. 415.IX Item "pubkey/nodename"
267.It Va Subnet Li = Ar address Ns Op Li / Ns Ar prefixlength 416The public keys of the other nodes, one file per node.
268The subnet which this tinc daemon will serve.
269.Nm tinc
270tries to look up which other daemon it should send a packet to by searching the appropriate subnet.
271If the packet matches a subnet,
272it will be sent to the daemon who has this subnet in his host configuration file.
273Multiple
274.Va Subnet
275variables can be specified.
276.Pp
277Subnets can either be single MAC, IPv4 or IPv6 addresses,
278in which case a subnet consisting of only that single address is assumed,
279or they can be a IPv4 or IPv6 network address with a prefixlength.
280Shorthand notations are not supported.
281For example, IPv4 subnets must be in a form like 192.168.1.0/24,
282where 192.168.1.0 is the network address and 24 is the number of bits set in the netmask.
283Note that subnets like 192.168.1.1/24 are invalid!
284Read a networking HOWTO/FAQ/guide if you don't understand this.
285IPv6 subnets are notated like fec0:0:0:1:0:0:0:0/64.
286MAC addresses are notated like 0:1a:2b:3c:4d:5e.
287.It Va TCPOnly Li = yes | no Pq no
288If this variable is set to yes,
289then the packets are tunnelled over the TCP connection instead of a UDP connection.
290This is especially useful for those who want to run a tinc daemon
291from behind a masquerading firewall,
292or if UDP packet routing is disabled somehow.
293Setting this options also implicitly sets IndirectData.
294.El
295.Sh FILES
296.Bl -tag -width indent
297.It Pa /etc/tinc/
298The top directory for configuration files.
299.It Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /tinc.conf
300The default name of the server configuration file for net
301.Ar NETNAME .
302.It Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /hosts/
303Host configuration files are kept in this directory.
304.It Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /tinc-up
305If an executable file with this name exists,
306it will be executed right after the tinc daemon has connected to the virtual network device.
307It can be used to set up the corresponding network interface.
308.Pp
309The environment variable
310.Ev $NETNAME
311will be passed to the executable.
312If specified with the
313.Va Interface
314configuration variable,
315or if the virtual network device is a Linux tun/tap device,
316the environment variable
317.Ev $INTERFACE
318will be set to the name of the network interface.
319.It Pa /etc/tinc/ Ns Ar NETNAME Ns Pa /tinc-down
320If an executable file with this name exists,
321it will be executed right before the tinc daemon is going to close
322its connection to the virtual network device.
323The same environment variables will be passed as mentioned above.
324.El
325.Sh SEE ALSO 417.SH "SEE ALSO"
326.Xr tincd 8 , 418.IX Header "SEE ALSO"
327.Pa http://tinc.nl.linux.org/ , 419\&\fIvpe\fR\|(5), \fIvped\fR\|(8), \fIvpectrl\fR\|(8).
328.Pa http://www.linuxdoc.org/LDP/nag2/ . 420.SH "AUTHOR"
329.Pp 421.IX Header "AUTHOR"
330The full documentation for 422Marc Lehmann <vpe@plan9.de>
331.Nm tinc
332is maintained as a Texinfo manual.
333If the info and tinc programs are properly installed at your site, the command
334.Ic info tinc
335should give you access to the complete manual.
336.Pp
337.Nm tinc
338comes with ABSOLUTELY NO WARRANTY.
339This is free software, and you are welcome to redistribute it under certain conditions;
340see the file COPYING for details.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines