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.30 by root, Tue Dec 4 10:29:43 2012 UTC vs.
Revision 1.35 by root, Thu Jul 30 19:03:44 2015 UTC

1.\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14) 1.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.30)
2.\" 2.\"
3.\" Standard preamble: 3.\" Standard preamble:
4.\" ======================================================================== 4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP) 5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v 6.if t .sp .5v
… …
36.el\{\ 36.el\{\
37. ds -- \|\(em\| 37. ds -- \|\(em\|
38. ds PI \(*p 38. ds PI \(*p
39. ds L" `` 39. ds L" ``
40. ds R" '' 40. ds R" ''
41. ds C`
42. ds C'
41'br\} 43'br\}
42.\" 44.\"
43.\" Escape single quotes in literal strings from groff's Unicode transform. 45.\" Escape single quotes in literal strings from groff's Unicode transform.
44.ie \n(.g .ds Aq \(aq 46.ie \n(.g .ds Aq \(aq
45.el .ds Aq ' 47.el .ds Aq '
46.\" 48.\"
47.\" If the F register is turned on, we'll generate index entries on stderr for 49.\" If the F register is turned on, we'll generate index entries on stderr for
48.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index 50.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
49.\" entries marked with X<> in POD. Of course, you'll have to process the 51.\" entries marked with X<> in POD. Of course, you'll have to process the
50.\" output yourself in some meaningful fashion. 52.\" output yourself in some meaningful fashion.
51.ie \nF \{\ 53.\"
54.\" Avoid warning from groff about undefined register 'F'.
52. de IX 55.de IX
53. tm Index:\\$1\t\\n%\t"\\$2"
54.. 56..
55. nr % 0 57.nr rF 0
56. rr F 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. \}
57.\} 69.\}
58.el \{\ 70.rr rF
59. de IX
60..
61.\}
62.\" 71.\"
63.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). 72.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
64.\" Fear. Run. Save yourself. No user-serviceable parts. 73.\" Fear. Run. Save yourself. No user-serviceable parts.
65. \" fudge factors for nroff and troff 74. \" fudge factors for nroff and troff
66.if n \{\ 75.if n \{\
… …
122.\} 131.\}
123.rm #[ #] #H #V #F C 132.rm #[ #] #H #V #F C
124.\" ======================================================================== 133.\" ========================================================================
125.\" 134.\"
126.IX Title "GVPE.CONF 5" 135.IX Title "GVPE.CONF 5"
127.TH GVPE.CONF 5 "2012-07-06" "2.24" "GNU Virtual Private Ethernet" 136.TH GVPE.CONF 5 "2015-06-25" "2.25" "GNU Virtual Private Ethernet"
128.\" For nroff, turn off justification. Always turn off hyphenation; it makes 137.\" For nroff, turn off justification. Always turn off hyphenation; it makes
129.\" way too many mistakes in technical documents. 138.\" way too many mistakes in technical documents.
130.if n .ad l 139.if n .ad l
131.nh 140.nh
132.SH "NAME" 141.SH "NAME"
… …
161values, but not within the variable names or values themselves. 170values, but not within the variable names or values themselves.
162.PP 171.PP
163All settings are applied \*(L"in order\*(R", that is, later settings of the same 172All settings are applied \*(L"in order\*(R", that is, later settings of the same
164variable overwrite earlier ones. 173variable overwrite earlier ones.
165.PP 174.PP
166The only exceptions to the above are the \*(L"on\*(R" and \*(L"include\*(R" directives: 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
167.IP "on nodename ..." 4 195.IP "on nodename ..." 4
168.IX Item "on nodename ..." 196.IX Item "on nodename ..."
169.PD 0 197.PD 0
170.IP "on !nodename ..." 4 198.IP "on !nodename ..." 4
171.IX Item "on !nodename ..." 199.IX Item "on !nodename ..."
… …
219.PP 247.PP
220Node-specific settings can be used at any time. If used before the first 248Node-specific settings can be used at any time. If used before the first
221node section they will set the default values for all following nodes. 249node section they will set the default values for all following nodes.
222.SH "CONFIG VARIABLES" 250.SH "CONFIG VARIABLES"
223.IX Header "CONFIG VARIABLES" 251.IX Header "CONFIG VARIABLES"
224.SS "\s-1GLOBAL\s0 \s-1SETTINGS\s0" 252.SS "\s-1GLOBAL SETTINGS\s0"
225.IX Subsection "GLOBAL SETTINGS" 253.IX Subsection "GLOBAL SETTINGS"
226Global settings will affect the behaviour of the running gvpe daemon, that 254Global settings will affect the behaviour of the running gvpe daemon, that
227is, they are in some sense node-specific (config files can set different 255is, they are in some sense node-specific (config files can set different
228values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of 256values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of
229the gvpe daemon and all connections it creates. 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).
230.IP "dns-forw-host = hostname/ip" 4 283.IP "dns-forw-host = hostname/ip" 4
231.IX Item "dns-forw-host = hostname/ip" 284.IX Item "dns-forw-host = hostname/ip"
232The \s-1DNS\s0 server to forward \s-1DNS\s0 requests to for the \s-1DNS\s0 tunnel protocol 285The \s-1DNS\s0 server to forward \s-1DNS\s0 requests to for the \s-1DNS\s0 tunnel protocol
233(default: \f(CW127.0.0.1\fR, changing it is highly recommended). 286(default: \f(CW127.0.0.1\fR, changing it is highly recommended).
234.IP "dns-forw-port = port-number" 4 287.IP "dns-forw-port = port-number" 4
… …
341.IP "NODENAME=branch1" 4 394.IP "NODENAME=branch1" 4
342.IX Item "NODENAME=branch1" 395.IX Item "NODENAME=branch1"
343The nickname of the node. 396The nickname of the node.
344.IP "NODEID=1" 4 397.IP "NODEID=1" 4
345.IX Item "NODEID=1" 398.IX Item "NODEID=1"
346The numerical node \s-1ID\s0 of the node running this instance of \s-1GVPE\s0. The first 399The numerical node \s-1ID\s0 of the node running this instance of \s-1GVPE.\s0 The first
347node mentioned in the config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on. 400node mentioned in the config file gets \s-1ID 1,\s0 the second \s-1ID 2\s0 and so on.
348.RE 401.RE
349.RS 4 402.RS 4
350.Sp 403.Sp
351In addition, all node-specific variables (except \f(CW\*(C`NODEID\*(C'\fR) will be 404In addition, all node-specific variables (except \f(CW\*(C`NODEID\*(C'\fR) will be
352available with a postfix of \f(CW\*(C`_nodeid\*(C'\fR, which contains the value for that 405available with a postfix of \f(CW\*(C`_nodeid\*(C'\fR, which contains the value for that
… …
386instance using the same protocol, nor can you share the protocol with 439instance using the same protocol, nor can you share the protocol with
387other programs. 440other programs.
388.Sp 441.Sp
389The default is 47 (\s-1GRE\s0), which has a good chance of tunneling 442The default is 47 (\s-1GRE\s0), which has a good chance of tunneling
390through firewalls (but note that gvpe's rawip protocol is not \s-1GRE\s0 443through firewalls (but note that gvpe's rawip protocol is not \s-1GRE\s0
391compatible). Other common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 444compatible). Other common choices are 50 (\s-1IPSEC, ESP\s0), 51 (\s-1IPSEC, AH\s0), 4
392(\s-1IPIP\s0 tunnels) or 98 (\s-1ENCAP\s0, rfc1241). 445(\s-1IPIP\s0 tunnels) or 98 (\s-1ENCAP,\s0 rfc1241).
393.Sp 446.Sp
394Many versions of Linux seem to have a bug that causes them to reorder 447Many versions of Linux seem to have a bug that causes them to reorder
395packets for some ip protocols (\s-1GRE\s0, \s-1ESP\s0) but not for others (\s-1AH\s0), so 448packets for some ip protocols (\s-1GRE, ESP\s0) but not for others (\s-1AH\s0), so
396choose wisely (that is, use 51, \s-1AH\s0). 449choose wisely (that is, use 51, \s-1AH\s0).
397.IP "http-proxy-host = hostname/ip" 4 450.IP "http-proxy-host = hostname/ip" 4
398.IX Item "http-proxy-host = hostname/ip" 451.IX Item "http-proxy-host = hostname/ip"
399The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was 452The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was
400compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of 453compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of
… …
449this information to the \f(CW\*(C`if\-up\*(C'\fR script. 502this information to the \f(CW\*(C`if\-up\*(C'\fR script.
450.Sp 503.Sp
451Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). 504Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp).
452.Sp 505.Sp
453This value must be the minimum of the \s-1MTU\s0 values of all nodes. 506This value must be the minimum of the \s-1MTU\s0 values of all nodes.
454.IP "node = nickname" 4 507.IP "nfmark = integer" 4
455.IX Item "node = nickname" 508.IX Item "nfmark = integer"
456Not really a config setting but introduces a node section. The nickname is 509This advanced option, when set to a nonzero value (default: \f(CW0\fR), tries
457used to select the right configuration section and must be passed as an 510to set the netfilter mark (or fwmark) value on all sockets gvpe uses to
458argument to the gvpe daemon. 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
459.IP "node-up = relative-or-absolute-path" 4 522.IP "node-up = relative-or-absolute-path" 4
460.IX Item "node-up = relative-or-absolute-path" 523.IX Item "node-up = relative-or-absolute-path"
461Sets a command (default: none) that should be called whenever a connection 524Sets a command (default: none) that should be called whenever a connection
462is established (even on rekeying operations). Note that node\-up/down 525is established (even on rekeying operations). Note that node\-up/down
463scripts will be run asynchronously, but execution is serialised, so there 526scripts will be run asynchronously, but execution is serialised, so there
… …
496.Vb 6 559.Vb 6
497\& #!/bin/sh 560\& #!/bin/sh
498\& { 561\& {
499\& echo update delete $DESTNODE.lowttl.example.net. a 562\& echo update delete $DESTNODE.lowttl.example.net. a
500\& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP 563\& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP
501\& echo 564\& echo
502\& } | nsupdate \-d \-k $CONFBASE:key.example.net. 565\& } | nsupdate \-d \-k $CONFBASE:key.example.net.
503.Ve 566.Ve
504.RE 567.RE
505.IP "node-change = relative-or-absolute-path" 4 568.IP "node-change = relative-or-absolute-path" 4
506.IX Item "node-change = relative-or-absolute-path" 569.IX Item "node-change = relative-or-absolute-path"
… …
510.IX Item "node-down = relative-or-absolute-path" 573.IX Item "node-down = relative-or-absolute-path"
511Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost. 574Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost.
512.IP "pid-file = path" 4 575.IP "pid-file = path" 4
513.IX Item "pid-file = path" 576.IX Item "pid-file = path"
514The path to the pid file to check and create 577The path to the pid file to check and create
515(default: \f(CW\*(C`LOCALSTATEDIR/run/gvpe.pid\*(C'\fR). 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.
516.IP "private-key = relative-path-to-key" 4 580.IP "private-key = relative-path-to-key" 4
517.IX Item "private-key = relative-path-to-key" 581.IX Item "private-key = relative-path-to-key"
518Sets the path (relative to the config directory) to the private key 582Sets the path (relative to the config directory) to the private key
519(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must 583(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must
520be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could 584be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could
… …
524Since only the private key file of the current node is used and the 588Since only the private key file of the current node is used and the
525private key file should be kept secret per-node to avoid spoofing, it is 589private key file should be kept secret per-node to avoid spoofing, it is
526not recommended to use this feature. 590not recommended to use this feature.
527.IP "rekey = seconds" 4 591.IP "rekey = seconds" 4
528.IX Item "rekey = seconds" 592.IX Item "rekey = seconds"
529Sets the rekeying interval in seconds (default: \f(CW3600\fR). Connections are 593Sets the rekeying interval in seconds (default: \f(CW3607\fR). Connections are
530reestablished every \f(CW\*(C`rekey\*(C'\fR seconds, making them use a new encryption 594reestablished every \f(CW\*(C`rekey\*(C'\fR seconds, making them use a new encryption
531key. 595key.
532.IP "nfmark = integer" 4 596.IP "seed-device = path" 4
533.IX Item "nfmark = integer" 597.IX Item "seed-device = path"
534This advanced option, when set to a nonzero value (default: \f(CW0\fR), tries 598The random device used to initially and regularly seed the random
535to set the netfilter mark (or fwmark) value on all sockets gvpe uses to 599number generator (default: \fI/dev/urandom\fR). Randomness is of paramount
536send packets. 600importance to the security of the algorithms used in gvpe.
537.Sp 601.Sp
538This can be used to make gvpe use a different set of routing rules. For 602On program start and every seed-interval, gvpe will read 64 octets.
539example, on GNU/Linux, the \f(CW\*(C`if\-up\*(C'\fR could set \f(CW\*(C`nfmark\*(C'\fR to 1000 and then
540put all routing rules into table \f(CW99\fR and then use an ip rule to make
541gvpe traffic avoid that routing table, in effect routing normal traffic
542via gvpe and gvpe traffic via the normal system routing tables:
543.Sp 603.Sp
544.Vb 1 604Setting this path to the empty string will disable this functionality
545\& ip rule add not fwmark 1000 lookup 99 605completely (the underlying crypto library will likely look for entropy
546.Ve 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 conenction 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.
547.SS "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0" 628.SS "\s-1NODE SPECIFIC SETTINGS\s0"
548.IX Subsection "NODE SPECIFIC SETTINGS" 629.IX Subsection "NODE SPECIFIC SETTINGS"
549The following settings are node-specific, that is, every node can have 630The following settings are node-specific, that is, every node can have
550different settings, even within the same gvpe instance. Settings that are 631different settings, even within the same gvpe instance. Settings that are
551set before the first node section set the defaults, settings that are 632set before the first node section set the defaults, settings that are
552set within a node section only apply to the given node. 633set within a node section only apply to the given node.
… …
638.Sp 719.Sp
639Enable the \s-1ICMP\s0 transport using \s-1ICMP\s0 packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this 720Enable the \s-1ICMP\s0 transport using \s-1ICMP\s0 packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this
640node. 721node.
641.IP "enable-rawip = yes|true|on | no|false|off" 4 722.IP "enable-rawip = yes|true|on | no|false|off" 4
642.IX Item "enable-rawip = yes|true|on | no|false|off" 723.IX Item "enable-rawip = yes|true|on | no|false|off"
643See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW\s0 \s-1IP\s0 transport protocol. 724See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW IP\s0 transport protocol.
644.Sp 725.Sp
645Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol 726Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol
646(default: \f(CW\*(C`no\*(C'\fR). 727(default: \f(CW\*(C`no\*(C'\fR).
647.IP "enable-tcp = yes|true|on | no|false|off" 4 728.IP "enable-tcp = yes|true|on | no|false|off" 4
648.IX Item "enable-tcp = yes|true|on | no|false|off" 729.IX Item "enable-tcp = yes|true|on | no|false|off"
… …
655.IX Item "enable-udp = yes|true|on | no|false|off" 736.IX Item "enable-udp = yes|true|on | no|false|off"
656See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol. 737See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol.
657.Sp 738.Sp
658Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR). 739Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR).
659.IP "hostname = hostname | ip [can not be defaulted]" 4 740.IP "hostname = hostname | ip [can not be defaulted]" 4
660.IX Item "hostname = hostname | ip [can not be defaulted]" 741.IX Item "hostname = hostname | ip [can not be defaulted]"
661Forces the address of this node to be set to the given \s-1DNS\s0 hostname or \s-1IP\s0 742Forces the address of this node to be set to the given \s-1DNS\s0 hostname or \s-1IP\s0
662address. It will be resolved before each connect request, so dyndns should 743address. It will be resolved before each connect request, so dyndns should
663work fine. If this setting is not specified and a router is available, 744work fine. If this setting is not specified and a router is available,
664then the router will be queried for the address of this node. Otherwise, 745then the router will be queried for the address of this node. Otherwise,
665the connection attempt will fail. 746the connection attempt will fail.
… …
682.IX Item "inherit-tos = yes|true|on | no|false|off" 763.IX Item "inherit-tos = yes|true|on | no|false|off"
683Whether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when 764Whether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
684sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then 765sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then
685outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent 766outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent
686to the tunnel device, which is usually what you want. 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.
687.IP "max-retry = positive-number" 4 777.IP "max-retry = positive-number" 4
688.IX Item "max-retry = positive-number" 778.IX Item "max-retry = positive-number"
689The maximum interval in seconds (default: \f(CW3600\fR, one hour) between 779The maximum interval in seconds (default: \f(CW3600\fR, one hour) between
690retries to establish a connection to this node. When a connection cannot 780retries to establish a connection to this node. When a connection cannot
691be established, gvpe uses exponential back-off capped at this value. It's 781be established, gvpe uses exponential back-off capped at this value. It's
… …
750.IP "node-up, node-down" 4 840.IP "node-up, node-down" 4
751.IX Item "node-up, node-down" 841.IX Item "node-up, node-down"
752If used the node up or node-down scripts. 842If used the node up or node-down scripts.
753.IP "hostkey" 4 843.IP "hostkey" 4
754.IX Item "hostkey" 844.IX Item "hostkey"
755The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host. 845The (default path of the) private key of the current host.
756.IP "pubkey/nodename" 4 846.IP "pubkey/nodename" 4
757.IX Item "pubkey/nodename" 847.IX Item "pubkey/nodename"
758The public keys of the other nodes, one file per node. 848The public keys of the other nodes, one file per node.
759.SH "SEE ALSO" 849.SH "SEE ALSO"
760.IX Header "SEE ALSO" 850.IX Header "SEE ALSO"

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines