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

Comparing gvpe/doc/gvpe.conf.5 (file contents):
Revision 1.31 by root, Tue Dec 4 13:23:17 2012 UTC vs.
Revision 1.38 by root, Thu Oct 25 03:13:13 2018 UTC

1.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
2.\"
3.\" Standard preamble:
4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v
7.if n .sp
8..
9.de Vb \" Begin verbatim text
10.ft CW
11.nf
12.ne \\$1
13..
14.de Ve \" End verbatim text
15.ft R
16.fi
17..
18.\" Set up some character translations and predefined strings. \*(-- will
19.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
20.\" double quote, and \*(R" will give a right double quote. \*(C+ will
21.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
22.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
23.\" nothing in troff, for use with C<>.
24.tr \(*W-
25.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
26.ie n \{\
27. ds -- \(*W-
28. ds PI pi
29. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
31. ds L" ""
32. ds R" ""
33. ds C`
34. ds C'
35'br\}
36.el\{\
37. ds -- \|\(em\|
38. ds PI \(*p
39. ds L" ``
40. ds R" ''
41. ds C`
42. ds C'
43'br\}
44.\"
45.\" Escape single quotes in literal strings from groff's Unicode transform.
46.ie \n(.g .ds Aq \(aq
47.el .ds Aq '
48.\"
49.\" If the F register is turned on, we'll generate index entries on stderr for
50.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
51.\" entries marked with X<> in POD. Of course, you'll have to process the
52.\" output yourself in some meaningful fashion.
53.\"
54.\" Avoid warning from groff about undefined register 'F'.
55.de IX
56..
57.nr rF 0
58.if \n(.g .if rF .nr rF 1
59.if (\n(rF:(\n(.g==0)) \{
60. if \nF \{
61. de IX
62. tm Index:\\$1\t\\n%\t"\\$2"
63..
64. if !\nF==2 \{
65. nr % 0
66. nr F 2
67. \}
68. \}
69.\}
70.rr rF
71.\"
72.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
73.\" Fear. Run. Save yourself. No user-serviceable parts.
74. \" fudge factors for nroff and troff
75.if n \{\
76. ds #H 0
77. ds #V .8m
78. ds #F .3m
79. ds #[ \f1
80. ds #] \fP
81.\}
82.if t \{\
83. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
84. ds #V .6m
85. ds #F 0
86. ds #[ \&
87. ds #] \&
88.\}
89. \" simple accents for nroff and troff
90.if n \{\
91. ds ' \&
92. ds ` \&
93. ds ^ \&
94. ds , \&
95. ds ~ ~
96. ds /
97.\}
98.if t \{\
99. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
100. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
101. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
102. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
103. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
104. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
105.\}
106. \" troff and (daisy-wheel) nroff accents
107.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
108.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
109.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
110.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
111.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
112.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
113.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
114.ds ae a\h'-(\w'a'u*4/10)'e
115.ds Ae A\h'-(\w'A'u*4/10)'E
116. \" corrections for vroff
117.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
118.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
119. \" for low resolution devices (crt and lpr)
120.if \n(.H>23 .if \n(.V>19 \
121\{\
122. ds : e
123. ds 8 ss
124. ds o a
125. ds d- d\h'-1'\(ga
126. ds D- D\h'-1'\(hy
127. ds th \o'bp'
128. ds Th \o'LP'
129. ds ae ae
130. ds Ae AE
131.\}
132.rm #[ #] #H #V #F C
133.\" ========================================================================
134.\"
135.IX Title "GVPE.CONF 5"
136.TH GVPE.CONF 5 "2016-11-12" "3.0" "GNU Virtual Private Ethernet"
137.\" For nroff, turn off justification. Always turn off hyphenation; it makes
138.\" way too many mistakes in technical documents.
139.if n .ad l
140.nh
141.SH "NAME"
142gvpe.conf \- configuration file for the GNU VPE daemon
143.SH "SYNOPSIS"
144.IX Header "SYNOPSIS"
145.Vb 4
146\& # global options for all nodes
147\& udp\-port = 407
148\& mtu = 1492
149\& ifname = vpn0
150\&
151\& # first node is named branch1 and is at 1.2.3.4
152\& node = branch1
153\& hostname = 1.2.3.4
154\&
155\& # second node uses dns to resolve the address
156\& node = branch2
157\& hostname = www.example.net
158\& udp\-port = 500 # this host uses a different udp\-port
159\&
160\& # third node has no fixed ip address
161\& node = branch3
162\& connect = ondemand
163.Ve
164.SH "DESCRIPTION"
165.IX Header "DESCRIPTION"
166The gvpe config file consists of a series of lines that contain \f(CW\*(C`variable
167= value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and
168extend to the end of the line. They can be used on their own lines, or
169after any directives. Whitespace is allowed around the \f(CW\*(C`=\*(C'\fR sign or after
170values, but not within the variable names or values themselves.
171.PP
172All settings are applied \*(L"in order\*(R", that is, later settings of the same
173variable overwrite earlier ones.
174.PP
175The only exceptions to the above are the following directives:
176.IP "node nodename" 4
177.IX Item "node nodename"
178Introduces a node section. The nodename is used to select the right
179configuration section and is the same string as is passed as an argument
180to the gvpe daemon.
181.Sp
182Multiple \f(CW\*(C`node\*(C'\fR statements with the same node name are supported and will
183be merged together.
184.IP "global" 4
185.IX Item "global"
186This statement switches back to the global section, which is mainly
187useful if you want to include a second config file, e..g for local
188customisations. To do that, simply include this at the very end of your
189config file:
190.Sp
191.Vb 2
192\& global
193\& include local.conf
194.Ve
195.IP "on nodename ..." 4
196.IX Item "on nodename ..."
197.PD 0
198.IP "on !nodename ..." 4
199.IX Item "on !nodename ..."
200.PD
201You can prefix any configuration directive with \f(CW\*(C`on\*(C'\fR and a nodename. \s-1GVPE\s0
202will will only \*(L"execute\*(R" it on the named node, or (if the nodename starts
203with \f(CW\*(C`!\*(C'\fR) on all nodes except the named one.
204.Sp
205Example: set the \s-1MTU\s0 to \f(CW1450\fR everywhere, \f(CW\*(C`loglevel\*(C'\fR to \f(CW\*(C`noise\*(C'\fR on
206\&\f(CW\*(C`branch1\*(C'\fR, and \f(CW\*(C`connect\*(C'\fR to \f(CW\*(C`ondemand\*(C'\fR everywhere but on branch2.
207.Sp
208.Vb 3
209\& mtu = 1450
210\& on branch1 loglevel = noise
211\& on !branch2 connect = ondemand
212.Ve
213.IP "include relative-or-absolute-path" 4
214.IX Item "include relative-or-absolute-path"
215Reads the specified file (the path must not contain whitespace or \f(CW\*(C`=\*(C'\fR
216characters) and evaluate all config directives in it as if they were
217spelled out in place of the \f(CW\*(C`include\*(C'\fR directive.
218.Sp
219The path is a printf format string, that is, you must escape any \f(CW\*(C`%\*(C'\fR
220by doubling it, and you can have a single \f(CW%s\fR inside, which will be
221replaced by the current nodename.
222.Sp
223Relative paths are interpreted relative to the \s-1GVPE\s0 config directory.
224.Sp
225Example: include the file \fIlocal.conf\fR in the config directory on every
226node.
227.Sp
228.Vb 1
229\& include local.conf
230.Ve
231.Sp
232Example: include a file \fIconf/\fRnodename\fI.conf\fR
233.Sp
234.Vb 1
235\& include conf/%s.conf
236.Ve
237.SH "ANATOMY OF A CONFIG FILE"
238.IX Header "ANATOMY OF A CONFIG FILE"
239Usually, a config file starts with a few global settings (like the \s-1UDP\s0
240port to listen on), followed by node-specific sections that begin with a
241\&\f(CW\*(C`node = nickname\*(C'\fR line.
242.PP
243Every node that is part of the network must have a section that starts
244with \f(CW\*(C`node = nickname\*(C'\fR. The number and order of the nodes is important
245and must be the same on all nodes. It is not uncommon for node sections to
246be completely empty \- if the default values are right.
247.PP
248Node-specific settings can be used at any time. If used before the first
249node section they will set the default values for all following nodes.
250.SH "CONFIG VARIABLES"
251.IX Header "CONFIG VARIABLES"
252.SS "\s-1GLOBAL SETTINGS\s0"
253.IX Subsection "GLOBAL SETTINGS"
254Global settings will affect the behaviour of the running gvpe daemon, that
255is, they are in some sense node-specific (config files can set different
256values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of
257the gvpe daemon and all connections it creates.
258.IP "chroot = path or /" 4
259.IX Item "chroot = path or /"
260Tells \s-1GVPE\s0 to \fIchroot\fR\|(2) to the specified path after reading all necessary
261files, binding to sockets and running the \f(CW\*(C`if\-up\*(C'\fR script, but before
262running \f(CW\*(C`node\-up\*(C'\fR or any other scripts.
263.Sp
264The special path \fI/\fR instructs \s-1GVPE\s0 to create (and remove) an empty
265temporary directory to use as new root. This is most secure, but makes it
266impossible to use any scripts other than the \f(CW\*(C`if\-up\*(C'\fR one.
267.IP "chuid = numerical-uid" 4
268.IX Item "chuid = numerical-uid"
269.PD 0
270.IP "chgid = numerical-gid" 4
271.IX Item "chgid = numerical-gid"
272.PD
273These two options tell \s-1GVPE\s0 to change to the given user and/or group id
274after reading all necessary files, binding to sockets and running the
275\&\f(CW\*(C`if\-up\*(C'\fR script.
276.Sp
277Other scripts, such as \f(CW\*(C`node\-up\*(C'\fR, are run with the new user id or group id.
278.IP "chuser = username" 4
279.IX Item "chuser = username"
280Alternative to \f(CW\*(C`chuid\*(C'\fR and \f(CW\*(C`chgid\*(C'\fR: Sets both \f(CW\*(C`chuid\*(C'\fR and \f(CW\*(C`chgid\*(C'\fR
281to the user and (primary) group ids of the specified user (for example,
282\&\f(CW\*(C`nobody\*(C'\fR).
283.IP "dns-forw-host = hostname/ip" 4
284.IX Item "dns-forw-host = hostname/ip"
285The \s-1DNS\s0 server to forward \s-1DNS\s0 requests to for the \s-1DNS\s0 tunnel protocol
286(default: \f(CW127.0.0.1\fR, changing it is highly recommended).
287.IP "dns-forw-port = port-number" 4
288.IX Item "dns-forw-port = port-number"
289The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR,
290which is fine in most cases).
291.IP "dns-case-preserving = yes|true|on | no|false|off" 4
292.IX Item "dns-case-preserving = yes|true|on | no|false|off"
293Sets whether the \s-1DNS\s0 transport forwarding server preserves case (\s-1DNS\s0
294servers have to, but some access systems are even more broken than others)
295(default: true).
296.Sp
297Normally, when the forwarding server changes the case of domain names then
298\&\s-1GVPE\s0 will automatically set this to false.
299.IP "dns-max-outstanding = integer-number-of-requests" 4
300.IX Item "dns-max-outstanding = integer-number-of-requests"
301The maximum number of outstanding \s-1DNS\s0 transport requests
302(default: \f(CW100\fR). \s-1GVPE\s0 will never issue more requests then the given
303limit without receiving replies. In heavily overloaded situations it might
304help to set this to a low number (e.g. \f(CW3\fR or even \f(CW1\fR) to limit the
305number of parallel requests.
306.Sp
307The default should be working \s-1OK\s0 for most links.
308.IP "dns-overlap-factor = float" 4
309.IX Item "dns-overlap-factor = float"
310The \s-1DNS\s0 transport uses the minimum request latency (\fBmin_latency\fR) seen
311during a connection as it's timing base. This factor (default: \f(CW0.5\fR,
312must be > 0) is multiplied by \fBmin_latency\fR to get the maximum sending
313rate (= minimum send interval), i.e. a factor of \f(CW1\fR means that a new
314request might be generated every \fBmin_latency\fR seconds, which means on
315average there should only ever be one outstanding request. A factor of
316\&\f(CW0.5\fR means that \s-1GVPE\s0 will send requests twice as often as the minimum
317latency measured.
318.Sp
319For congested or picky \s-1DNS\s0 forwarders you could use a value nearer to or
320exceeding \f(CW1\fR.
321.Sp
322The default should be working \s-1OK\s0 for most links.
323.IP "dns-send-interval = send-interval-in-seconds" 4
324.IX Item "dns-send-interval = send-interval-in-seconds"
325The minimum send interval (= maximum rate) that the \s-1DNS\s0 transport will
326use to send new \s-1DNS\s0 requests. \s-1GVPE\s0 will not exceed this rate even when
327the latency is very low. The default is \f(CW0.01\fR, which means \s-1GVPE\s0 will
328not send more than 100 \s-1DNS\s0 requests per connection per second. For
329high-bandwidth links you could go lower, e.g. to \f(CW0.001\fR or so. For
330congested or rate-limited links, you might want to go higher, say \f(CW0.1\fR,
331\&\f(CW0.2\fR or even higher.
332.Sp
333The default should be working \s-1OK\s0 for most links.
334.IP "dns-timeout-factor = float" 4
335.IX Item "dns-timeout-factor = float"
336Factor to multiply the \f(CW\*(C`min_latency\*(C'\fR (see \f(CW\*(C`dns\-overlap\-factor\*(C'\fR) by to
337get request timeouts. The default of \f(CW8\fR means that the \s-1DNS\s0 transport
338will resend the request when no reply has been received for longer than
339eight times the minimum (= expected) latency, assuming the request or
340reply has been lost.
341.Sp
342For congested links a higher value might be necessary (e.g. \f(CW30\fR). If
343the link is very stable lower values (e.g. \f(CW2\fR) might work
344nicely. Values near or below \f(CW1\fR makes no sense whatsoever.
345.Sp
346The default should be working \s-1OK\s0 for most links but will result in low
347throughput if packet loss is high.
348.IP "if-up = relative-or-absolute-path" 4
349.IX Item "if-up = relative-or-absolute-path"
350Sets the path of a script that should be called immediately after the
351network interface is initialized (but not necessarily up). The following
352environment variables are passed to it (the values are just examples).
353.Sp
354Variables that have the same value on all nodes:
355.RS 4
356.IP "CONFBASE=/etc/gvpe" 4
357.IX Item "CONFBASE=/etc/gvpe"
358The configuration base directory.
359.IP "IFNAME=vpn0" 4
360.IX Item "IFNAME=vpn0"
361The network interface to initialize.
362.IP "IFTYPE=native # or tincd" 4
363.IX Item "IFTYPE=native # or tincd"
364.PD 0
365.IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4
366.IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.."
367.PD
368The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the
369\&\s-1OS\s0 name in lowercase) that this \s-1GVPE\s0 was configured for. Can be used to
370select the correct syntax to use for network-related commands.
371.IP "MTU=1436" 4
372.IX Item "MTU=1436"
373The \s-1MTU\s0 to set the interface to. You can use lower values (if done
374consistently on all nodes), but this is usually either inefficient or
375simply ineffective.
376.IP "NODES=5" 4
377.IX Item "NODES=5"
378The number of nodes in this \s-1GVPE\s0 network.
379.RE
380.RS 4
381.Sp
382Variables that are node-specific and with values pertaining to the node
383running this \s-1GVPE:\s0
384.IP "IFUPDATA=string" 4
385.IX Item "IFUPDATA=string"
386The value of the configuration directive \f(CW\*(C`if\-up\-data\*(C'\fR.
387.IP "MAC=fe:fd:80:00:00:01" 4
388.IX Item "MAC=fe:fd:80:00:00:01"
389The \s-1MAC\s0 address the network interface has to use.
390.Sp
391Might be used to initialize interfaces on platforms where \s-1GVPE\s0 does not
392do this automatically. Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR man page for
393platform-specific information.
394.IP "NODENAME=branch1" 4
395.IX Item "NODENAME=branch1"
396The nickname of the node.
397.IP "NODEID=1" 4
398.IX Item "NODEID=1"
399The numerical node \s-1ID\s0 of the node running this instance of \s-1GVPE.\s0 The first
400node mentioned in the config file gets \s-1ID 1,\s0 the second \s-1ID 2\s0 and so on.
401.RE
402.RS 4
403.Sp
404In addition, all node-specific variables (except \f(CW\*(C`NODEID\*(C'\fR) will be
405available with a postfix of \f(CW\*(C`_nodeid\*(C'\fR, which contains the value for that
406node, e.g. the \f(CW\*(C`MAC_1\*(C'\fR variable contains the \s-1MAC\s0 address of node #1, while
407the \f(CW\*(C`NODENAME_22\*(C'\fR variable contains the name of node #22.
408.Sp
409Here is a simple if-up script:
410.Sp
411.Vb 5
412\& #!/bin/sh
413\& ip link set $IFNAME up
414\& [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME
415\& [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME
416\& ip route add 10.0.0.0/8 dev $IFNAME
417.Ve
418.Sp
419More complicated examples (using routing to reduce \s-1ARP\s0 traffic) can be
420found in the \fIetc/\fR subdirectory of the distribution.
421.RE
422.IP "ifname = devname" 4
423.IX Item "ifname = devname"
424Sets the tun interface name to the given name. The default is OS-specific
425and most probably something like \f(CW\*(C`tun0\*(C'\fR.
426.IP "ifpersist = yes|true|on | no|false|off" 4
427.IX Item "ifpersist = yes|true|on | no|false|off"
428Should the tun/tap device be made persistent, that is, should the device
429stay up even when gvpe exits? Some versions of the tunnel device have
430problems sending packets when gvpe is restarted in persistent mode, so
431if the connections can be established but you cannot send packets from
432the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the
433device.
434.IP "ip-proto = numerical-ip-protocol" 4
435.IX Item "ip-proto = numerical-ip-protocol"
436Sets the protocol number to be used for the rawip protocol. This is a
437global option because all nodes must use the same protocol, and since
438there are no port numbers, you cannot easily run more than one gvpe
439instance using the same protocol, nor can you share the protocol with
440other programs.
441.Sp
442The default is 47 (\s-1GRE\s0), which has a good chance of tunneling
443through firewalls (but note that gvpe's rawip protocol is not \s-1GRE\s0
444compatible). Other common choices are 50 (\s-1IPSEC, ESP\s0), 51 (\s-1IPSEC, AH\s0), 4
445(\s-1IPIP\s0 tunnels) or 98 (\s-1ENCAP,\s0 rfc1241).
446.Sp
447Many versions of Linux seem to have a bug that causes them to reorder
448packets for some ip protocols (\s-1GRE, ESP\s0) but not for others (\s-1AH\s0), so
449choose wisely (that is, use 51, \s-1AH\s0).
450.IP "http-proxy-host = hostname/ip" 4
451.IX Item "http-proxy-host = hostname/ip"
452The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was
453compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of
454tcp connections through a http proxy server.
455.Sp
456\&\f(CW\*(C`http\-proxy\-host\*(C'\fR and \f(CW\*(C`http\-proxy\-port\*(C'\fR should specify the hostname and
457port number of the proxy server. See \f(CW\*(C`http\-proxy\-loginpw\*(C'\fR if your proxy
458requires authentication.
459.Sp
460Please note that gvpe will still try to resolve all hostnames in the
461configuration file, so if you are behind a proxy without access to a \s-1DNS\s0
462server better use numerical \s-1IP\s0 addresses.
463.Sp
464To make best use of this option disable all protocols except \s-1TCP\s0 in your
465config file and make sure your routers (or all other nodes) are listening
466on a port that the proxy allows (443, https, is a common choice).
467.Sp
468If you have a router, connecting to it will suffice. Otherwise \s-1TCP\s0 must be
469enabled on all nodes.
470.Sp
471Example:
472.Sp
473.Vb 3
474\& http\-proxy\-host = proxy.example.com
475\& http\-proxy\-port = 3128 # 8080 is another common choice
476\& http\-proxy\-auth = schmorp:grumbeere
477.Ve
478.IP "http-proxy-port = proxy-tcp-port" 4
479.IX Item "http-proxy-port = proxy-tcp-port"
480The port where your proxy server listens.
481.IP "http-proxy-auth = login:password" 4
482.IX Item "http-proxy-auth = login:password"
483The optional login and password used to authenticate to the proxy server,
484separated by a literal colon (\f(CW\*(C`:\*(C'\fR). Only basic authentication is
485currently supported.
486.IP "keepalive = seconds" 4
487.IX Item "keepalive = seconds"
488Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this
489many seconds of inactivity the daemon will start to send keepalive probe
490every 3 seconds until it receives a reply from the other end. If no reply
491is received within 15 seconds, the peer is considered unreachable and the
492connection is closed.
493.IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4
494.IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical"
495Set the logging level. Connection established messages are logged at level
496\&\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.
497.IP "mtu = bytes" 4
498.IX Item "mtu = bytes"
499Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically
500the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate
501maximum overhead (e.g. \s-1UDP\s0 header size, encryption blocksize...) and pass
502this information to the \f(CW\*(C`if\-up\*(C'\fR script.
503.Sp
504Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp).
505.Sp
506This value must be the minimum of the \s-1MTU\s0 values of all nodes.
507.IP "nfmark = integer" 4
508.IX Item "nfmark = integer"
509This advanced option, when set to a nonzero value (default: \f(CW0\fR), tries
510to set the netfilter mark (or fwmark) value on all sockets gvpe uses to
511send packets.
512.Sp
513This can be used to make gvpe use a different set of routing rules. For
514example, on GNU/Linux, the \f(CW\*(C`if\-up\*(C'\fR could set \f(CW\*(C`nfmark\*(C'\fR to 1000 and then
515put all routing rules into table \f(CW99\fR and then use an ip rule to make
516gvpe traffic avoid that routing table, in effect routing normal traffic
517via gvpe and gvpe traffic via the normal system routing tables:
518.Sp
519.Vb 1
520\& ip rule add not fwmark 1000 lookup 99
521.Ve
522.IP "node-up = relative-or-absolute-path" 4
523.IX Item "node-up = relative-or-absolute-path"
524Sets a command (default: none) that should be called whenever a connection
525is established (even on rekeying operations). Note that node\-up/down
526scripts will be run asynchronously, but execution is serialised, so there
527will only ever be one such script running.
528.Sp
529In addition to all the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following
530environment variables will be set (values are just examples):
531.RS 4
532.IP "DESTNODE=branch2" 4
533.IX Item "DESTNODE=branch2"
534The name of the remote node.
535.IP "DESTID=2" 4
536.IX Item "DESTID=2"
537The node id of the remote node.
538.IP "DESTSI=rawip/88.99.77.55:0" 4
539.IX Item "DESTSI=rawip/88.99.77.55:0"
540The \*(L"socket info\*(R" of the target node, protocol dependent but usually in
541the format protocol/ip:port.
542.IP "DESTIP=188.13.66.8" 4
543.IX Item "DESTIP=188.13.66.8"
544The numerical \s-1IP\s0 address of the remote node (gvpe accepts connections from
545everywhere, as long as the other node can authenticate itself).
546.IP "DESTPORT=655 # deprecated" 4
547.IX Item "DESTPORT=655 # deprecated"
548The protocol port used by the other side, if applicable.
549.IP "STATE=up" 4
550.IX Item "STATE=up"
551Node-up scripts get called with STATE=up, node-change scripts get called
552with STATE=change and node-down scripts get called with STATE=down.
553.RE
554.RS 4
555.Sp
556Here is a nontrivial example that uses nsupdate to update the name => ip
557mapping in some \s-1DNS\s0 zone:
558.Sp
559.Vb 6
560\& #!/bin/sh
561\& {
562\& echo update delete $DESTNODE.lowttl.example.net. a
563\& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP
564\& echo
565\& } | nsupdate \-d \-k $CONFBASE:key.example.net.
566.Ve
567.RE
568.IP "node-change = relative-or-absolute-path" 4
569.IX Item "node-change = relative-or-absolute-path"
570Same as \f(CW\*(C`node\-change\*(C'\fR, but gets called whenever something about a
571connection changes (such as the source \s-1IP\s0 address).
572.IP "node-down = relative-or-absolute-path" 4
573.IX Item "node-down = relative-or-absolute-path"
574Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost.
575.IP "pid-file = path" 4
576.IX Item "pid-file = path"
577The path to the pid file to check and create
578(default: \f(CW\*(C`LOCALSTATEDIR/run/gvpe.pid\*(C'\fR). The first \f(CW%s\fR is replaced by
579the nodename \- any other use of \f(CW\*(C`%\*(C'\fR must be written as \f(CW\*(C`%%\*(C'\fR.
580.IP "private-key = relative-path-to-key" 4
581.IX Item "private-key = relative-path-to-key"
582Sets the path (relative to the config directory) to the private key
583(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must
584be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could use
585paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to be able to share the same config directory
586between nodes.
587.Sp
588Since only the private key file of the current node is used and the
589private key file should be kept secret per-node to avoid spoofing, it is
590not recommended to use this feature this way though.
591.IP "rekey = seconds" 4
592.IX Item "rekey = seconds"
593Sets the rekeying interval in seconds (default: \f(CW3607\fR). Connections are
594reestablished every \f(CW\*(C`rekey\*(C'\fR seconds, making them use a new encryption
595key.
596.IP "seed-device = path" 4
597.IX Item "seed-device = path"
598The random device used to initially and regularly seed the random
599number generator (default: \fI/dev/urandom\fR). Randomness is of paramount
600importance to the security of the algorithms used in gvpe.
601.Sp
602On program start and every seed-interval, gvpe will read 64 octets.
603.Sp
604Setting this path to the empty string will disable this functionality
605completely (the underlying crypto library will likely look for entropy
606sources on it's own though, so not all is lost).
607.IP "seed-interval = seconds" 4
608.IX Item "seed-interval = seconds"
609The number of seconds between reseeds of the random number generator
610(default: \f(CW3613\fR). A value of \f(CW0\fR disables this regular reseeding.
611.IP "serial = string" 4
612.IX Item "serial = string"
613The configuration serial number. This can be any string up to 16 bytes
614length. Only when the serial matches on both sides of a connection will
615the connection succeed. This is \fInot\fR a security mechanism and eay to
616spoof, this mechanism exists to alert users that their config is outdated.
617.Sp
618It's recommended to specify this is a date string such as \f(CW\*(C`2013\-05\-05\*(C'\fR or
619\&\f(CW20121205084417\fR.
620.Sp
621The exact algorithm is as this: if a connection request is received form a
622node with an identical serial, then it succeeds normally.
623.Sp
624If the remote serial is lower than the local serial, it is ignored.
625.Sp
626If the remote serial is higher than the local serial, a warning message is
627logged.
628.SS "\s-1NODE SPECIFIC SETTINGS\s0"
629.IX Subsection "NODE SPECIFIC SETTINGS"
630The following settings are node-specific, that is, every node can have
631different settings, even within the same gvpe instance. Settings that are
632set before the first node section set the defaults, settings that are
633set within a node section only apply to the given node.
634.IP "allow-direct = nodename" 4
635.IX Item "allow-direct = nodename"
636Allow direct connections to this node. See \f(CW\*(C`deny\-direct\*(C'\fR for more info.
637.IP "compress = yes|true|on | no|false|off" 4
638.IX Item "compress = yes|true|on | no|false|off"
639For the current node, this specified whether it will accept compressed
640packets, and for all other nodes, this specifies whether to try to
641compress data packets sent to this node (default: \f(CW\*(C`yes\*(C'\fR). Compression is
642really cheap even on slow computers, has no size overhead at all and will
643only be used when the other side supports compression, so enabling this is
644often a good idea.
645.IP "connect = ondemand | never | always | disabled" 4
646.IX Item "connect = ondemand | never | always | disabled"
647Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always
648try to establish and keep a connection to the given node), \f(CW\*(C`never\*(C'\fR
649(never initiate a connection to the given host, but accept connections),
650\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection when there are outstanding
651packets in the queue and take it down after the keepalive interval) or
652\&\f(CW\*(C`disabled\*(C'\fR (node is bad, don't talk to it).
653.Sp
654Routers will automatically be forced to \f(CW\*(C`always\*(C'\fR unless they are
655\&\f(CW\*(C`disabled\*(C'\fR, to ensure all nodes can talk to each other.
656.IP "deny-direct = nodename | *" 4
657.IX Item "deny-direct = nodename | *"
658Deny direct connections to the specified node (or all nodes when \f(CW\*(C`*\*(C'\fR
659is given). Only one node can be specified, but you can use multiple
660\&\f(CW\*(C`allow\-direct\*(C'\fR and \f(CW\*(C`deny\-direct\*(C'\fR statements. This only makes sense in
661networks with routers, as routers are required for indirect connections.
662.Sp
663Sometimes, a node cannot reach some other nodes for reasons of network
664connectivity. For example, a node behind a firewall that only allows
665connections to/from a single other node in the network. In this case one
666should specify \f(CW\*(C`deny\-direct = *\*(C'\fR and \f(CW\*(C`allow\-direct = othernodename\*(C'\fR (the other
667node \fImust\fR be a router for this to work).
668.Sp
669The algorithm to check whether a connection may be direct is as follows:
670.Sp
6711. Other node mentioned in an \f(CW\*(C`allow\-direct\*(C'\fR? If yes, allow the connection.
672.Sp
6732. Other node mentioned in a \f(CW\*(C`deny\-direct\*(C'\fR? If yes, deny direct connections.
674.Sp
6753. Allow the connection.
676.Sp
677That is, \f(CW\*(C`allow\-direct\*(C'\fR takes precedence over \f(CW\*(C`deny\-direct\*(C'\fR.
678.Sp
679The check is done in both directions, i.e. both nodes must allow a direct
680connection before one is attempted, so you only need to specify connect
681limitations on one node.
682.IP "dns-domain = domain-suffix" 4
683.IX Item "dns-domain = domain-suffix"
684The \s-1DNS\s0 domain suffix that points to the \s-1DNS\s0 tunnel server for this node.
685.Sp
686The domain must point to a \s-1NS\s0 record that points to the \fIdns-hostname\fR,
687i.e.
688.Sp
689.Vb 2
690\& dns\-domainname = tunnel.example.net
691\& dns\-hostname = tunnel\-server.example.net
692.Ve
693.Sp
694Corresponds to the following \s-1DNS\s0 entries in the \f(CW\*(C`example.net\*(C'\fR domain:
695.Sp
696.Vb 2
697\& tunnel.example.net. NS tunnel\-server.example.net.
698\& tunnel\-server.example.net. A 13.13.13.13
699.Ve
700.IP "dns-hostname = hostname/ip" 4
701.IX Item "dns-hostname = hostname/ip"
702The address to bind the \s-1DNS\s0 tunnel socket to, similar to the \f(CW\*(C`hostname\*(C'\fR,
703but for the \s-1DNS\s0 tunnel protocol only. Default: \f(CW0.0.0.0\fR, but that might
704change.
705.IP "dns-port = port-number" 4
706.IX Item "dns-port = port-number"
707The port to bind the \s-1DNS\s0 tunnel socket to. Must be \f(CW53\fR on \s-1DNS\s0 tunnel servers.
708.IP "enable-dns = yes|true|on | no|false|off" 4
709.IX Item "enable-dns = yes|true|on | no|false|off"
710See \fIgvpe.protocol\fR\|(7) for a description of the \s-1DNS\s0 transport
711protocol. Avoid this protocol if you can.
712.Sp
713Enable the \s-1DNS\s0 tunneling protocol on this node, either as server or as
714client. Support for this transport protocol is only available when gvpe
715was compiled using the \f(CW\*(C`\-\-enable\-dns\*(C'\fR option.
716.IP "enable-icmp = yes|true|on | no|false|off" 4
717.IX Item "enable-icmp = yes|true|on | no|false|off"
718See \fIgvpe.protocol\fR\|(7) for a description of the \s-1ICMP\s0 transport protocol.
719.Sp
720Enable the \s-1ICMP\s0 transport using \s-1ICMP\s0 packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this
721node.
722.IP "enable-rawip = yes|true|on | no|false|off" 4
723.IX Item "enable-rawip = yes|true|on | no|false|off"
724See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW IP\s0 transport protocol.
725.Sp
726Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol
727(default: \f(CW\*(C`no\*(C'\fR).
728.IP "enable-tcp = yes|true|on | no|false|off" 4
729.IX Item "enable-tcp = yes|true|on | no|false|off"
730See \fIgvpe.protocol\fR\|(7) for a description of the \s-1TCP\s0 transport protocol.
731.Sp
732Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port
733(default: \f(CW\*(C`no\*(C'\fR). Support for this transport protocol is only available
734when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option.
735.IP "enable-udp = yes|true|on | no|false|off" 4
736.IX Item "enable-udp = yes|true|on | no|false|off"
737See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol.
738.Sp
739Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR).
740.IP "hostname = hostname | ip [can not be defaulted]" 4
741.IX Item "hostname = hostname | ip [can not be defaulted]"
742Forces the address of this node to be set to the given \s-1DNS\s0 hostname or \s-1IP\s0
743address. It will be resolved before each connect request, so dyndns should
744work fine. If this setting is not specified and a router is available,
745then the router will be queried for the address of this node. Otherwise,
746the connection attempt will fail.
747.Sp
748Note that \s-1DNS\s0 resolving is done synchronously, pausing the daemon. If that
749is an issue you need to specify \s-1IP\s0 addresses.
750.IP "icmp-type = integer" 4
751.IX Item "icmp-type = integer"
752Sets the type value to be used for outgoing (and incoming) packets sent
753via the \s-1ICMP\s0 transport.
754.Sp
755The default is \f(CW0\fR (which is \f(CW\*(C`echo\-reply\*(C'\fR, also known as
756\&\*(L"ping-reply\*(R"). Other useful values include \f(CW8\fR (\f(CW\*(C`echo\-request\*(C'\fR, a.k.a.
757\&\*(L"ping\*(R") and \f(CW11\fR (\f(CW\*(C`time\-exceeded\*(C'\fR), but any 8\-bit value can be used.
758.IP "if-up-data = value" 4
759.IX Item "if-up-data = value"
760The value specified using this directive will be passed to the \f(CW\*(C`if\-up\*(C'\fR
761script in the environment variable \f(CW\*(C`IFUPDATA\*(C'\fR.
762.IP "inherit-tos = yes|true|on | no|false|off" 4
763.IX Item "inherit-tos = yes|true|on | no|false|off"
764Whether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
765sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then
766outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent
767to the tunnel device, which is usually what you want.
768.IP "low-power = yes|true|on | no|false|off" 4
769.IX Item "low-power = yes|true|on | no|false|off"
770If true, designates a node as a low-power node. Low-power nodes use
771larger timeouts and try to reduce cpu time. Other nodes talking to a
772low-power node will also use larger timeouts, and will use less aggressive
773optimisations, in the hope of reducing load. Security is not compromised.
774.Sp
775The typical low-power node would be a mobile phone, where wakeups and
776encryption can significantly increase power drain.
777.IP "max-retry = positive-number" 4
778.IX Item "max-retry = positive-number"
779The maximum interval in seconds (default: \f(CW3600\fR, one hour) between
780retries to establish a connection to this node. When a connection cannot
781be established, gvpe uses exponential back-off capped at this value. It's
782sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on
783connections to routers that usually are stable but sometimes are down, to
784assure quick reconnections even after longer downtimes.
785.IP "max-ttl = seconds" 4
786.IX Item "max-ttl = seconds"
787Expire packets that couldn't be sent after this many seconds
788(default: \f(CW60\fR). Gvpe will normally queue packets for a node without an
789active connection, in the hope of establishing a connection soon. This
790value specifies the maximum lifetime a packet will stay in the queue, if a
791packet gets older, it will be thrown away.
792.IP "max-queue = positive\-number>=1" 4
793.IX Item "max-queue = positive-number>=1"
794The maximum number of packets that will be queued (default: \f(CW512\fR)
795for this node. If more packets are sent then earlier packets will be
796expired. See \f(CW\*(C`max\-ttl\*(C'\fR, above.
797.IP "router-priority = 0 | 1 | positive\-number>=2" 4
798.IX Item "router-priority = 0 | 1 | positive-number>=2"
799Sets the router priority of the given node (default: \f(CW0\fR, disabled).
800.Sp
801If some node tries to connect to another node but it doesn't have a
802hostname, it asks a router node for it's \s-1IP\s0 address. The router node
803chosen is the one with the highest priority larger than \f(CW1\fR that is
804currently reachable. This is called a \fImediated\fR connection, as the
805connection itself will still be direct, but it uses another node to
806mediate between the two nodes.
807.Sp
808The value \f(CW0\fR disables routing, that means if the node receives a packet
809not for itself it will not forward it but instead drop it.
810.Sp
811The special value \f(CW1\fR allows other hosts to route through the router
812host, but they will never route through it by default (i.e. the config
813file of another node needs to specify a router priority higher than one
814to choose such a node for routing).
815.Sp
816The idea behind this is that some hosts can, if required, bump the
817\&\f(CW\*(C`router\-priority\*(C'\fR setting to higher than \f(CW1\fR in their local config to
818route through specific hosts. If \f(CW\*(C`router\-priority\*(C'\fR is \f(CW0\fR, then routing
819will be refused, so \f(CW1\fR serves as a \*(L"enable, but do not use by default\*(R"
820switch.
821.Sp
822Nodes with \f(CW\*(C`router\-priority\*(C'\fR set to \f(CW2\fR or higher will always be forced
823to \f(CW\*(C`connect\*(C'\fR = \f(CW\*(C`always\*(C'\fR (unless they are \f(CW\*(C`disabled\*(C'\fR).
824.IP "tcp-port = port-number" 4
825.IX Item "tcp-port = port-number"
826Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number.
827.IP "udp-port = port-number" 4
828.IX Item "udp-port = port-number"
829Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not
830officially assigned by \s-1IANA\s0!).
831.SH "CONFIG DIRECTORY LAYOUT"
832.IX Header "CONFIG DIRECTORY LAYOUT"
833The default (or recommended) directory layout for the config directory is:
834.IP "gvpe.conf" 4
835.IX Item "gvpe.conf"
836The config file.
837.IP "if-up" 4
838.IX Item "if-up"
839The if-up script
840.IP "node-up, node-down" 4
841.IX Item "node-up, node-down"
842If used the node up or node-down scripts.
843.IP "hostkey" 4
844.IX Item "hostkey"
845The (default path of the) private key of the current host.
846.IP "pubkey/nodename" 4
847.IX Item "pubkey/nodename"
848The public keys of the other nodes, one file per node.
849.SH "SEE ALSO"
850.IX Header "SEE ALSO"
851\&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8).
852.SH "AUTHOR"
853.IX Header "AUTHOR"
854Marc Lehmann <gvpe@schmorp.de>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines