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.3 by pcg, Mon Jan 10 19:21:06 2005 UTC vs.
Revision 1.29 by root, Tue Mar 8 17:33:30 2011 UTC

1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
2.\"
3.\" Standard preamble:
4.\" ========================================================================
5.de Sh \" Subsection heading
6.br
7.if t .Sp
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 "GVPE.CONF 5"
132.TH GVPE.CONF 5 "2004-12-04" "1.7" "GNU Virtual Private Ethernet"
133.SH "NAME"
134gvpe.conf \- configuration file for the GNU VPE daemon
135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS"
137.Vb 4
138\& enable-udp = yes
139\& udp-port = 407
140\& mtu = 1492
141\& ifname = vpn0
142.Ve
143.PP
144.Vb 2
145\& node = branch1
146\& hostname = 1.2.3.4
147.Ve
148.PP
149.Vb 3
150\& node = branch2
151\& hostname = www.example.net
152\& udp-port = 500 # this host uses a different udp-port
153.Ve
154.PP
155.Vb 2
156\& node = branch3
157\& connect = ondemand
158.Ve
159.SH "DESCRIPTION"
160.IX Header "DESCRIPTION"
161The gvpe config file consists of a series of lines that contain \f(CW\*(C`variable
162= value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and
163extend to the end of the line. They can be used on their own lines, or
164after any directives. Spaces are allowed before or after the \f(CW\*(C`=\*(C'\fR sign or
165after values, but not within the variable names or values themselves.
166.PP
167The only exception to the above is the \*(L"on\*(R" directive that can prefix any
168\&\f(CW\*(C`name = value\*(C'\fR setting and will only \*(L"execute\*(R" it on the named node, or
169(if the nodename starts with \*(L"!\*(R") on all nodes except the named one.
170.PP
171.Vb 3
172\& name = value
173\& on branch1 loglevel = noise
174\& on !branch2 connect = ondemand
175.Ve
176.PP
177All settings are executed \*(L"in order\*(R", that is, later settings of the same
178variable overwrite earlier ones.
179.SH "ANATOMY OF A CONFIG FILE"
180.IX Header "ANATOMY OF A CONFIG FILE"
181Usually, a config file starts with global settings (like the udp port to
182listen on), followed by node-specific sections that begin with a \f(CW\*(C`node =
183nickname\*(C'\fR line.
184.PP
185Every node that is part of the network must have a section that starts
186with \f(CW\*(C`node = nickname\*(C'\fR. The number and order of the nodes is important
187and must be the same on all hosts. It is not uncommon for node sections to
188be completely empty \- if the default values are right.
189.PP
190Node-specific settings can be used at any time. If used before the first
191node section they will set the default values for all following nodes.
192.SH "CONFIG VARIABLES"
193.IX Header "CONFIG VARIABLES"
194.Sh "\s-1GLOBAL\s0 \s-1SETTINGS\s0"
195.IX Subsection "GLOBAL SETTINGS"
196Global settings will affect the behaviour of the running gvpe daemon, that
197is, they are in some sense node-specific (config files can set different
198values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of
199the gvpe daemon and all connections it creates.
200.IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4
201.IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical"
202Set the logging level. Connection established messages are logged at level
203\&\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.
204.IP "node = nickname" 4
205.IX Item "node = nickname"
206Not really a config setting but introduces a node section. The nickname is
207used to select the right configuration section and must be passed as an
208argument to the gvpe daemon.
209.IP "private-key = relative-path-to-key" 4
210.IX Item "private-key = relative-path-to-key"
211Sets the path (relative to the config directory) to the private key
212(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must
213be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could
214use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where
215\&\f(CW\*(C`gvpectrl\*(C'\fR puts them.
216.Sp
217Since only the private key file of the current node is used and the
218private key file should be kept secret per-host to avoid spoofings, it is
219not recommended to use this feature.
220.IP "ifpersist = yes|true|on | no|false|off" 4
221.IX Item "ifpersist = yes|true|on | no|false|off"
222Should the tun/tap device be made persistent, that is, should the device
223stay up even when gvpe exits? Some versions of the tunnel device have
224problems sending packets when gvpe is restarted in persistent mode, so
225if the connections can be established but you cannot send packets from
226the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the
227device.
228.IP "ifname = devname" 4
229.IX Item "ifname = devname"
230Sets the tun interface name to the given name. The default is OS-specific
231and most probably something like \f(CW\*(C`tun0\*(C'\fR.
232.IP "rekey = seconds" 4
233.IX Item "rekey = seconds"
234Sets the rekeying interval in seconds (default: \f(CW3600\fR). Connections are
235reestablished every \f(CW\*(C`rekey\*(C'\fR seconds.
236.IP "keepalive = seconds" 4
237.IX Item "keepalive = seconds"
238Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this
239many seconds of inactivity the daemon will start to send keepalive probe
240every 5 seconds until it receives a reply from the other end. If no reply
241is received within 30 seconds, the peer is considered unreachable and the
242connection is closed.
243.IP "mtu = bytes" 4
244.IX Item "mtu = bytes"
245Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically
246the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate
247maximum overhead (e.g. udp header size, encryption blocksize...) and pass
248this information to the \f(CW\*(C`if\-up\*(C'\fR script.
249.Sp
250Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp).
251.Sp
252This value must be the minimum of the mtu values of all hosts.
253.IP "ip-proto = numerical-ip-protocol" 4
254.IX Item "ip-proto = numerical-ip-protocol"
255Sets the protocol number to be used for the rawip protocol. This is a
256global option because all hosts must use the same protocol, and since
257there are no port numbers, you cannot easily run more than one gvpe
258instance using the same protocol, nor can you share the protocol with
259other programs.
260.Sp
261The default is 47 (\s-1GRE\s0), which has a good chance of tunneling through
262firewalls (but note that the rawip protocol is not \s-1GRE\s0 compatible). Other
263common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 (\s-1IPIP\s0 tunnels) or 98
264(\s-1ENCAP\s0, rfc1241)
265.IP "if-up = relative-or-absolute-path" 4
266.IX Item "if-up = relative-or-absolute-path"
267Sets the path of a script that should be called immediately after the
268network interface is initialized (but not neccessarily up). The following
269environment variables are passed to it (the values are just examples):
270.RS 4
271.IP "CONFBASE=/etc/gvpe" 4
272.IX Item "CONFBASE=/etc/gvpe"
273The configuration base directory.
274.IP "IFNAME=vpn0" 4
275.IX Item "IFNAME=vpn0"
276The interface to initialize.
277.IP "MTU=1436" 4
278.IX Item "MTU=1436"
279The \s-1MTU\s0 to set the interface to. You can use lower values (if done
280consistently on all hosts), but this is usually ineffective.
281.IP "MAC=fe:fd:80:00:00:01" 4
282.IX Item "MAC=fe:fd:80:00:00:01"
283The \s-1MAC\s0 address to set the interface to. The script *must* set the
284interface \s-1MAC\s0 to this value. You will most likely use one of these:
285.Sp
286.Vb 2
287\& ip link set $IFNAME address $MAC mtu $MTU up # GNU/Linux
288\& ifconfig $IFNAME ether $MAC mtu $MTU up # FreeBSD
289.Ve
290.Sp
291Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for platform-specific information.
292.IP "IFTYPE=native # or tincd" 4
293.IX Item "IFTYPE=native # or tincd"
294.PD 0
295.IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4
296.IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.."
297.PD
298The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the os
299name in lowercase) that this gvpe was configured for. Can be used to select
300the correct syntax to use for network-related commands.
301.IP "NODENAME=branch1" 4
302.IX Item "NODENAME=branch1"
303The nickname of the current node, as passed to the gvpe daemon.
304.IP "NODEID=1" 4
305.IX Item "NODEID=1"
306The numerical node id of the current node. The first node mentioned in the
307config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on.
308.RE
309.RS 4
310.Sp
311Here is a simple if-up script:
312.Sp
313.Vb 5
314\& #!/bin/sh
315\& ip link set $IFNAME address $MAC mtu $MTU up
316\& [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME
317\& [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME
318\& ip route add 10.0.0.0/8 dev $IFNAME
319.Ve
320.Sp
321More complicated examples (using routing to reduce arp traffic) can be
322found in the etc/ subdirectory of the distribution.
323.RE
324.IP "node-up = relative-or-absolute-path" 4
325.IX Item "node-up = relative-or-absolute-path"
326Sets a command (default: no script) that should be called whenever a
327connection is established (even on rekeying operations). In addition
328to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment
329variables will be set:
330.RS 4
331.IP "DESTNODE=branch2" 4
332.IX Item "DESTNODE=branch2"
333The name of the remote node.
334.IP "DESTID=2" 4
335.IX Item "DESTID=2"
336The node id of the remote node.
337.IP "DESTIP=188.13.66.8" 4
338.IX Item "DESTIP=188.13.66.8"
339The numerical \s-1IP\s0 address of the remote host (gvpe accepts connections from
340everywhere, as long as the other host can authenticate itself).
341.IP "DESTPORT=655 # deprecated" 4
342.IX Item "DESTPORT=655 # deprecated"
343The \s-1UDP\s0 port used by the other side.
344.IP "STATE=UP" 4
345.IX Item "STATE=UP"
346Node-up scripts get called with STATE=UP, node-down scripts get called
347with STATE=DOWN.
348.RE
349.RS 4
350.Sp
351Here is a nontrivial example that uses nsupdate to update the name => ip
352mapping in some dns zone:
353.Sp
354.Vb 6
355\& #!/bin/sh
356\& {
357\& echo update delete $DESTNODE.lowttl.example.net. a
358\& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP
359\& echo
360\& } | nsupdate -d -k $CONFBASE:key.example.net.
361.Ve
362.RE
363.IP "node-down = relative-or-absolute-path" 4
364.IX Item "node-down = relative-or-absolute-path"
365Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost.
366.IP "http-proxy-host = hostname/ip" 4
367.IX Item "http-proxy-host = hostname/ip"
368The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was
369compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of
370tcp connections through a http proxy server.
371.Sp
372\&\f(CW\*(C`http\-proxy\-host\*(C'\fR and \f(CW\*(C`http\-proxy\-port\*(C'\fR should specify the hostname and
373port number of the proxy server. See \f(CW\*(C`http\-proxy\-loginpw\*(C'\fR if your proxy
374requires authentication.
375.Sp
376Please note that gvpe will still try to resolve all hostnames in the
377configuration file, so if you are behind a proxy without access to a dns
378server better use numerical \s-1IP\s0 addresses.
379.Sp
380To make best use of this option disable all protocols except tcp in your
381config file and make sure your routers (or all other hosts) are listening
382on a port that the proxy allows (443, https, is a common choice).
383.Sp
384If you have a router, connecting to it will suffice. Otherwise tcp must be
385enabled on all hosts.
386.Sp
387Example:
388.Sp
389.Vb 3
390\& http-proxy-host = proxy.example.com
391\& http-proxy-port = 3128 # 8080 is another common choice
392\& http-proxy-auth = schmorp:grumbeere
393.Ve
394.IP "http-proxy-port = proxy-tcp-port" 4
395.IX Item "http-proxy-port = proxy-tcp-port"
396The port where your proxy server listens.
397.IP "http-proxy-auth = login:password" 4
398.IX Item "http-proxy-auth = login:password"
399The optional login and password used to authenticate to the proxy server,
400seperated by a literal colon (\f(CW\*(C`:\*(C'\fR). Only basic authentication is
401currently supported.
402.IP "pid-file = path" 4
403.IX Item "pid-file = path"
404The path to the pid file to check and create (Default:
405.Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0"
406.IX Subsection "NODE SPECIFIC SETTINGS"
407The following settings are node\-specific, that is, every node can have
408different settings, even within the same gvpe instance. Settings that are
409executed before the first node section set the defaults, settings that are
410executed within a node section only apply to the given node.
411.IP "udp-port = port-number" 4
412.IX Item "udp-port = port-number"
413Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not
414officially assigned by \s-1IANA\s0!).
415.IP "tcp-port = port-number" 4
416.IX Item "tcp-port = port-number"
417Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number.
418.IP "enable-rawip = yes|true|on | no|false|off" 4
419.IX Item "enable-rawip = yes|true|on | no|false|off"
420Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol
421(default: \f(CW\*(C`no\*(C'\fR). This is the best choice, since the overhead per packet
422is only 38 bytes, as opposed to \s-1UDP\s0's 58 (or \s-1TCP\s0's 60+).
423.IP "enable-udp = yes|true|on | no|false|off" 4
424.IX Item "enable-udp = yes|true|on | no|false|off"
425Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`yes\*(C'\fR,
426but this will change!). This is a good general choice since \s-1UDP\s0 tunnels
427well through many firewalls.
428.Sp
429\&\s-1NOTE:\s0 Please specify \f(CW\*(C`enable\-udp = yes\*(C'\fR even though it is the default, as
430some future version will have all protocols disabled by default.
431.IP "enable-tcp = yes|true|on | no|false|off" 4
432.IX Item "enable-tcp = yes|true|on | no|false|off"
433Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port
434(default: \f(CW\*(C`no\*(C'\fR). Support for this horribly unsuitable protocol is only
435available when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option. Never
436use this transport unless you really must, it is horribly ineffiecent and
437resource-intensive compared to the other transports.
438.IP "router-priority = 0 | 1 | positive\-number>2" 4
439.IX Item "router-priority = 0 | 1 | positive-number>2"
440Sets the router priority of the given host (default: \f(CW0\fR, disabled). If
441some host tries to connect to another host without a hostname, it asks
442the router host for it's \s-1IP\s0 address. The router host is the one with the
443highest priority larger than \f(CW1\fR that is currently reachable.
444.Sp
445Make sure all hosts always connect (\f(CW\*(C`connect = always\*(C'\fR) to the router
446hosts, otherwise connecting to them might be impossible.
447.Sp
448The special value \f(CW1\fR allows other hosts to route through the router
449host, but they will never route through it by default. The value \f(CW0\fR
450disables routing. The idea behind this is that some hosts can, if
451required, bump the \f(CW\*(C`router\-priority\*(C'\fR setting to higher than \f(CW1\fR in their
452local config to route through specific hosts. If \f(CW\*(C`router\-priority\*(C'\fR is
453\&\f(CW0\fR, then routing will be refused, so \f(CW1\fR serves as a \*(L"enable, but do
454not use by default\*(R" switch.
455.IP "connect = ondemand | never | always | disabled" 4
456.IX Item "connect = ondemand | never | always | disabled"
457Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always
458try to establish and keep a connection to the given host), \f(CW\*(C`never\*(C'\fR
459(never initiate a connection to the given host, but accept connections),
460\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and
461take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad,
462don't talk to it).
463.IP "inherit-tos = yes|true|on | no|false|off" 4
464.IX Item "inherit-tos = yes|true|on | no|false|off"
465Wether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
466sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then
467outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent
468to the tunnel device, which is usually what you want.
469.IP "compress = yes|true|on | no|false|off" 4
470.IX Item "compress = yes|true|on | no|false|off"
471Wether to compress data packets sent to this host (default: \f(CW\*(C`yes\*(C'\fR).
472Compression is really cheap even on slow computers and has no size
473overhead at all, so enabling this is a good idea.
474.IP "max-retry = positive-number" 4
475.IX Item "max-retry = positive-number"
476The maximum interval in seconds (default: \f(CW28800\fR, 8 hours) between
477retries to establish a connection to this node. When a connection cannot
478be established, gvpe uses exponential backoff capped at this value. It's
479sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on
480connections to routers that usually are stable but sometimes are down, to
481assure quick reconnections.
482.SH "CONFIG DIRECTORY LAYOUT"
483.IX Header "CONFIG DIRECTORY LAYOUT"
484The default (or recommended) directory layout for the config directory is:
485.IP "gvpe.conf" 4
486.IX Item "gvpe.conf"
487The config file.
488.IP "if-up" 4
489.IX Item "if-up"
490The if-up script
491.IP "node\-up, node-down" 4
492.IX Item "node-up, node-down"
493If used the node up or node-down scripts.
494.IP "hostkey" 4
495.IX Item "hostkey"
496The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host.
497.IP "pubkey/nodename" 4
498.IX Item "pubkey/nodename"
499The public keys of the other nodes, one file per node.
500.SH "SEE ALSO"
501.IX Header "SEE ALSO"
502\&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8).
503.SH "AUTHOR"
504.IX Header "AUTHOR"
505Marc Lehmann <gvpe@plan9.de>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines