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