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.2 by pcg, Sun Jul 25 18:11:39 2004 UTC vs.
Revision 1.12 by pcg, Wed Mar 23 17:03:58 2005 UTC

… …
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "GVPE.CONF 5" 131.IX Title "GVPE.CONF 5"
132.TH GVPE.CONF 5 "2004-07-25" "1.7" "GNU Virtual Private Ethernet" 132.TH GVPE.CONF 5 "2005-03-23" "1.8" "GNU Virtual Private Ethernet"
133.SH "NAME" 133.SH "NAME"
134gvpe.conf \- configuration file for the GNU VPE daemon 134gvpe.conf \- configuration file for the GNU VPE daemon
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 4 137.Vb 3
138\& enable-udp = yes
139\& udp-port = 407 138\& udp-port = 407
140\& mtu = 1492 139\& mtu = 1492
141\& ifname = vpn0 140\& ifname = vpn0
142.Ve 141.Ve
143.PP 142.PP
… …
195.IX Subsection "GLOBAL SETTINGS" 194.IX Subsection "GLOBAL SETTINGS"
196Global settings will affect the behaviour of the running gvpe daemon, that 195Global settings will affect the behaviour of the running gvpe daemon, that
197is, they are in some sense node-specific (config files can set different 196is, 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 197values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of
199the gvpe daemon and all connections it creates. 198the gvpe daemon and all connections it creates.
200.IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4 199.IP "dns-forw-host = hostname/ip" 4
201.IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical" 200.IX Item "dns-forw-host = hostname/ip"
202Set the logging level. Connection established messages are logged at level 201The dns server to forward dns requests to for the \s-1DNS\s0 tunnel protocol
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. 202(default: \f(CW127.0.0.1\fR, changing it is highly recommended).
204.IP "node = nickname" 4 203.IP "dns-forw-port = port-number" 4
205.IX Item "node = nickname" 204.IX Item "dns-forw-port = port-number"
206Not really a config setting but introduces a node section. The nickname is 205The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR,
207used to select the right configuration section and must be passed as an 206which is fine in most cases).
208argument to the gvpe daemon. 207.IP "dns-max-outstanding = integer-number-of-requests" 4
209.IP "private-key = relative-path-to-key" 4 208.IX Item "dns-max-outstanding = integer-number-of-requests"
210.IX Item "private-key = relative-path-to-key" 209The maximum number of outstanding \s-1DNS\s0 transport requests
211Sets the path (relative to the config directory) to the private key 210(default: \f(CW100\fR). \s-1GVPE\s0 will never issue more requests then the given
212(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must 211limit without receiving replies. In heavily overloaded situations it might
213be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could 212help to set this to a low number (e.g. \f(CW3\fR or even \f(CW1\fR) to limit the
214use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where 213number of parallel requests.
215\&\f(CW\*(C`gvpectrl\*(C'\fR puts them.
216.Sp 214.Sp
217Since only the private key file of the current node is used and the 215The default should be working ok for most links.
218private key file should be kept secret per-host to avoid spoofings, it is 216.IP "dns-overlap-factor = float" 4
219not recommended to use this feature. 217.IX Item "dns-overlap-factor = float"
220.IP "ifpersist = yes|true|on | no|false|off" 4 218The \s-1DNS\s0 transport uses the minimum request latency (\fBmin_latency\fR) seen
221.IX Item "ifpersist = yes|true|on | no|false|off" 219during a connection as it's timing base. This factor (default: \f(CW0.5\fR,
222Should the tun/tap device be made persistent, that is, should the device 220must be > 0) is multiplied by \fBmin_latency\fR to get the maximum sending
223stay up even when gvpe exits? Some versions of the tunnel device have 221rate (= minimum send interval), i.e. a factor of \f(CW1\fR means that a new
224problems sending packets when gvpe is restarted in persistent mode, so 222request might be generated every \fBmin_latency\fR seconds, which means on
225if the connections can be established but you cannot send packets from 223average there should only ever be one outstanding request. A factor of
226the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the 224\&\f(CW0.5\fR means that \s-1GVPE\s0 will send requests twice as often as the minimum
227device. 225latency measured.
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 226.Sp
250Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). 227For congested or picky dns forwarders you could use a value nearer to or
228exceeding \f(CW1\fR.
251.Sp 229.Sp
252This value must be the minimum of the mtu values of all hosts. 230The default should be working ok for most links.
253.IP "ip-proto = numerical-ip-protocol" 4 231.IP "dns-send-interval = send-interval-in-seconds" 4
254.IX Item "ip-proto = numerical-ip-protocol" 232.IX Item "dns-send-interval = send-interval-in-seconds"
255Sets the protocol number to be used for the rawip protocol. This is a 233The minimum send interval (= maximum rate) that the \s-1DNS\s0 transport will
256global option because all hosts must use the same protocol, and since 234use to send new \s-1DNS\s0 requests. \s-1GVPE\s0 will not exceed this rate even when
257there are no port numbers, you cannot easily run more than one gvpe 235the latency is very low. The default is \f(CW0.01\fR, which means \s-1GVPE\s0 will
258instance using the same protocol, nor can you share the protocol with 236not send more than 100 \s-1DNS\s0 requests per connection per second. For
259other programs. 237high-bandwidth links you could go lower, e.g. to \f(CW0.001\fR or so. For
238congested or rate-limited links, you might want to go higher, say \f(CW0.1\fR,
239\&\f(CW0.2\fR or even higher.
260.Sp 240.Sp
261The default is 47 (\s-1GRE\s0), which has a good chance of tunneling through 241The default should be working ok for most links.
262firewalls (but note that the rawip protocol is not \s-1GRE\s0 compatible). Other 242.IP "dns-timeout-factor = float" 4
263common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 (\s-1IPIP\s0 tunnels) or 98 243.IX Item "dns-timeout-factor = float"
264(\s-1ENCAP\s0, rfc1241) 244Factor to multiply the \f(CW\*(C`min_latency\*(C'\fR (see \f(CW\*(C`dns\-overlap\-factor\*(C'\fR) by to
245get request timeouts. The default of \f(CW8\fR means that the \s-1DNS\s0 transport
246will resend the request when no reply has been received for longer than
247eight times the minimum (= expected) latency, assuming the request or
248reply has been lost.
249.Sp
250For congested links a higher value might be necessary (e.g. \f(CW30\fR). If the
251link is very stable lower values (e.g. \f(CW2\fR) might work nicely. Values
252near or below \f(CW1\fR makes no sense whatsoever.
253.Sp
254The default should be working ok for most links.
265.IP "if-up = relative-or-absolute-path" 4 255.IP "if-up = relative-or-absolute-path" 4
266.IX Item "if-up = relative-or-absolute-path" 256.IX Item "if-up = relative-or-absolute-path"
267Sets the path of a script that should be called immediately after the 257Sets the path of a script that should be called immediately after the
268network interface is initialized (but not neccessarily up). The following 258network interface is initialized (but not neccessarily up). The following
269environment variables are passed to it (the values are just examples): 259environment variables are passed to it (the values are just examples):
… …
319.Ve 309.Ve
320.Sp 310.Sp
321More complicated examples (using routing to reduce arp traffic) can be 311More complicated examples (using routing to reduce arp traffic) can be
322found in the etc/ subdirectory of the distribution. 312found in the etc/ subdirectory of the distribution.
323.RE 313.RE
314.IP "ifname = devname" 4
315.IX Item "ifname = devname"
316Sets the tun interface name to the given name. The default is OS-specific
317and most probably something like \f(CW\*(C`tun0\*(C'\fR.
318.IP "ifpersist = yes|true|on | no|false|off" 4
319.IX Item "ifpersist = yes|true|on | no|false|off"
320Should the tun/tap device be made persistent, that is, should the device
321stay up even when gvpe exits? Some versions of the tunnel device have
322problems sending packets when gvpe is restarted in persistent mode, so
323if the connections can be established but you cannot send packets from
324the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the
325device.
326.IP "ip-proto = numerical-ip-protocol" 4
327.IX Item "ip-proto = numerical-ip-protocol"
328Sets the protocol number to be used for the rawip protocol. This is a
329global option because all hosts must use the same protocol, and since
330there are no port numbers, you cannot easily run more than one gvpe
331instance using the same protocol, nor can you share the protocol with
332other programs.
333.Sp
334The default is 47 (\s-1GRE\s0), which has a good chance of tunneling through
335firewalls (but note that the rawip protocol is not \s-1GRE\s0 compatible). Other
336common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 (\s-1IPIP\s0 tunnels) or 98
337(\s-1ENCAP\s0, rfc1241)
338.IP "http-proxy-host = hostname/ip" 4
339.IX Item "http-proxy-host = hostname/ip"
340The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was
341compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of
342tcp connections through a http proxy server.
343.Sp
344\&\f(CW\*(C`http\-proxy\-host\*(C'\fR and \f(CW\*(C`http\-proxy\-port\*(C'\fR should specify the hostname and
345port number of the proxy server. See \f(CW\*(C`http\-proxy\-loginpw\*(C'\fR if your proxy
346requires authentication.
347.Sp
348Please note that gvpe will still try to resolve all hostnames in the
349configuration file, so if you are behind a proxy without access to a dns
350server better use numerical \s-1IP\s0 addresses.
351.Sp
352To make best use of this option disable all protocols except tcp in your
353config file and make sure your routers (or all other hosts) are listening
354on a port that the proxy allows (443, https, is a common choice).
355.Sp
356If you have a router, connecting to it will suffice. Otherwise tcp must be
357enabled on all hosts.
358.Sp
359Example:
360.Sp
361.Vb 3
362\& http-proxy-host = proxy.example.com
363\& http-proxy-port = 3128 # 8080 is another common choice
364\& http-proxy-auth = schmorp:grumbeere
365.Ve
366.IP "http-proxy-port = proxy-tcp-port" 4
367.IX Item "http-proxy-port = proxy-tcp-port"
368The port where your proxy server listens.
369.IP "http-proxy-auth = login:password" 4
370.IX Item "http-proxy-auth = login:password"
371The optional login and password used to authenticate to the proxy server,
372seperated by a literal colon (\f(CW\*(C`:\*(C'\fR). Only basic authentication is
373currently supported.
374.IP "keepalive = seconds" 4
375.IX Item "keepalive = seconds"
376Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this
377many seconds of inactivity the daemon will start to send keepalive probe
378every 5 seconds until it receives a reply from the other end. If no reply
379is received within 30 seconds, the peer is considered unreachable and the
380connection is closed.
381.IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4
382.IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical"
383Set the logging level. Connection established messages are logged at level
384\&\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.
385.IP "mtu = bytes" 4
386.IX Item "mtu = bytes"
387Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically
388the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate
389maximum overhead (e.g. udp header size, encryption blocksize...) and pass
390this information to the \f(CW\*(C`if\-up\*(C'\fR script.
391.Sp
392Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp).
393.Sp
394This value must be the minimum of the mtu values of all hosts.
395.IP "node = nickname" 4
396.IX Item "node = nickname"
397Not really a config setting but introduces a node section. The nickname is
398used to select the right configuration section and must be passed as an
399argument to the gvpe daemon.
324.IP "node-up = relative-or-absolute-path" 4 400.IP "node-up = relative-or-absolute-path" 4
325.IX Item "node-up = relative-or-absolute-path" 401.IX Item "node-up = relative-or-absolute-path"
326Sets a command (default: no script) that should be called whenever a 402Sets a command (default: no script) that should be called whenever a
327connection is established (even on rekeying operations). In addition 403connection is established (even on rekeying operations). In addition
328to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment 404to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment
… …
361.Ve 437.Ve
362.RE 438.RE
363.IP "node-down = relative-or-absolute-path" 4 439.IP "node-down = relative-or-absolute-path" 4
364.IX Item "node-down = relative-or-absolute-path" 440.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. 441Same 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 442.IP "pid-file = path" 4
403.IX Item "pid-file = path" 443.IX Item "pid-file = path"
404The path to the pid file to check and create (Default: 444The path to the pid file to check and create
445(default: \f(CW\*(C`LOCALSTATEDIR/run/gvpe.pid\*(C'\fR).
446.IP "private-key = relative-path-to-key" 4
447.IX Item "private-key = relative-path-to-key"
448Sets the path (relative to the config directory) to the private key
449(default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must
450be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could
451use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where
452\&\f(CW\*(C`gvpectrl\*(C'\fR puts them.
453.Sp
454Since only the private key file of the current node is used and the
455private key file should be kept secret per-host to avoid spoofings, it is
456not recommended to use this feature.
457.IP "rekey = seconds" 4
458.IX Item "rekey = seconds"
459Sets the rekeying interval in seconds (default: \f(CW3600\fR). Connections are
460reestablished every \f(CW\*(C`rekey\*(C'\fR seconds.
405.Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0" 461.Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0"
406.IX Subsection "NODE SPECIFIC SETTINGS" 462.IX Subsection "NODE SPECIFIC SETTINGS"
407The following settings are node\-specific, that is, every node can have 463The following settings are node\-specific, that is, every node can have
408different settings, even within the same gvpe instance. Settings that are 464different settings, even within the same gvpe instance. Settings that are
409executed before the first node section set the defaults, settings that are 465executed before the first node section set the defaults, settings that are
410executed within a node section only apply to the given node. 466executed within a node section only apply to the given node.
467.IP "compress = yes|true|on | no|false|off" 4
468.IX Item "compress = yes|true|on | no|false|off"
469Wether to compress data packets sent to this host (default: \f(CW\*(C`yes\*(C'\fR).
470Compression is really cheap even on slow computers and has no size
471overhead at all, so enabling this is a good idea.
472.IP "connect = ondemand | never | always | disabled" 4
473.IX Item "connect = ondemand | never | always | disabled"
474Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always
475try to establish and keep a connection to the given host), \f(CW\*(C`never\*(C'\fR
476(never initiate a connection to the given host, but accept connections),
477\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and
478take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad,
479don't talk to it).
480.IP "dns-domain = domain-suffix" 4
481.IX Item "dns-domain = domain-suffix"
482The \s-1DNS\s0 domain suffix that points to the \s-1DNS\s0 tunnel server for this node.
483.Sp
484The domain must point to a \s-1NS\s0 record that points to the \fIdns-hostname\fR,
485i.e.
486.Sp
487.Vb 2
488\& dns-domainname = tunnel.example.net
489\& dns-hostname = tunnel-server.example.net
490.Ve
491.Sp
492Corresponds to the following \s-1DNS\s0 entries in the \f(CW\*(C`example.net\*(C'\fR domain:
493.Sp
494.Vb 2
495\& tunnel.example.net. NS tunnel-server.example.net.
496\& tunnel-server.example.net. A 13.13.13.13
497.Ve
498.IP "dns-hostname = hostname/ip" 4
499.IX Item "dns-hostname = hostname/ip"
500The address to bind the \s-1DNS\s0 tunnel socket to, similar to the \f(CW\*(C`hostname\*(C'\fR,
501but for the \s-1DNS\s0 tunnel protocol only. Default: \f(CW0.0.0.0\fR, but that might
502change.
411.IP "udp-port = port-number" 4 503.IP "dns-port = port-number" 4
412.IX Item "udp-port = port-number" 504.IX Item "dns-port = port-number"
413Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not 505The port to bind the \s-1DNS\s0 tunnel socket to. Must be \f(CW53\fR on \s-1DNS\s0 tunnel servers.
414officially assigned by \s-1IANA\s0!). 506.IP "enable-dns = yes|true|on | no|false|off" 4
415.IP "tcp-port = port-number" 4 507.IX Item "enable-dns = yes|true|on | no|false|off"
416.IX Item "tcp-port = port-number" 508See \fIgvpe.protocol\fR\|(7) for a description of the \s-1DNS\s0 transport
417Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number. 509protocol. Avoid this protocol if you can.
510.Sp
511Enable the \s-1DNS\s0 tunneling protocol on this node, either as server or as
512client. Support for this transport protocol is only available when gvpe
513was compiled using the \f(CW\*(C`\-\-enable\-dns\*(C'\fR option.
514.IP "enable-icmp = yes|true|on | no|false|off" 4
515.IX Item "enable-icmp = yes|true|on | no|false|off"
516See \fIgvpe.protocol\fR\|(7) for a description of the \s-1ICMP\s0 transport protocol.
517.Sp
518Enable the \s-1ICMP\s0 transport using icmp packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this
519node.
418.IP "enable-rawip = yes|true|on | no|false|off" 4 520.IP "enable-rawip = yes|true|on | no|false|off" 4
419.IX Item "enable-rawip = yes|true|on | no|false|off" 521.IX Item "enable-rawip = yes|true|on | no|false|off"
522See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW\s0 \s-1IP\s0 transport protocol.
523.Sp
420Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol 524Enable 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 525(default: \f(CW\*(C`no\*(C'\fR).
422is only 38 bytes, as opposed to \s-1UDP\s0's 58 (or \s-1TCP\s0's 60+). 526.IP "enable-tcp = yes|true|on | no|false|off" 4
527.IX Item "enable-tcp = yes|true|on | no|false|off"
528See \fIgvpe.protocol\fR\|(7) for a description of the \s-1TCP\s0 transport protocol.
529.Sp
530Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port
531(default: \f(CW\*(C`no\*(C'\fR). Support for this transport protocol is only available
532when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option.
423.IP "enable-udp = yes|true|on | no|false|off" 4 533.IP "enable-udp = yes|true|on | no|false|off" 4
424.IX Item "enable-udp = yes|true|on | no|false|off" 534.IX Item "enable-udp = yes|true|on | no|false|off"
535See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol.
536.Sp
425Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`yes\*(C'\fR, 537Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR,
426but this will change!). This is a good general choice since \s-1UDP\s0 tunnels 538unless no other protocol is enabled for a node, in which case this
427well through many firewalls. 539protocol is enabled automatically).
428.Sp 540.Sp
429\&\s-1NOTE:\s0 Please specify \f(CW\*(C`enable\-udp = yes\*(C'\fR even though it is the default, as 541\&\s-1NOTE:\s0 Please specify \f(CW\*(C`enable\-udp = yes\*(C'\fR if you want t use it even though
430some future version will have all protocols disabled by default. 542it might get switched on automatically, as some future version might
543default to another default protocol.
544.IP "icmp-type = integer" 4
545.IX Item "icmp-type = integer"
546Sets the type value to be used for outgoing (and incoming) packets sent
547via the \s-1ICMP\s0 transport.
548.Sp
549The default is \f(CW0\fR (which is \f(CW\*(C`echo\-reply\*(C'\fR, also known as
550\&\*(L"ping\-replies\*(R"). Other useful values include \f(CW8\fR (\f(CW\*(C`echo\-request\*(C'\fR, a.k.a.
551\&\*(L"ping\*(R") and \f(CW11\fR (\f(CW\*(C`time\-exceeded\*(C'\fR), but any 8\-bit value can be used.
431.IP "enable-tcp = yes|true|on | no|false|off" 4 552.IP "inherit-tos = yes|true|on | no|false|off" 4
432.IX Item "enable-tcp = yes|true|on | no|false|off" 553.IX Item "inherit-tos = yes|true|on | no|false|off"
433Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port 554Wether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
434(default: \f(CW\*(C`no\*(C'\fR). Support for this horribly unsuitable protocol is only 555sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then
435available when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option. Never 556outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent
436use this transport unless you really must, it is horribly ineffiecent and 557to the tunnel device, which is usually what you want.
437resource-intensive compared to the other transports. 558.IP "max-retry = positive-number" 4
559.IX Item "max-retry = positive-number"
560The maximum interval in seconds (default: \f(CW3600\fR, one hour) between
561retries to establish a connection to this node. When a connection cannot
562be established, gvpe uses exponential backoff capped at this value. It's
563sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on
564connections to routers that usually are stable but sometimes are down, to
565assure quick reconnections even after longer downtimes.
438.IP "router-priority = 0 | 1 | positive\-number>2" 4 566.IP "router-priority = 0 | 1 | positive\-number>=2" 4
439.IX Item "router-priority = 0 | 1 | positive-number>2" 567.IX Item "router-priority = 0 | 1 | positive-number>=2"
440Sets the router priority of the given host (default: \f(CW0\fR, disabled). If 568Sets 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 569some 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 570the 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. 571highest priority larger than \f(CW1\fR that is currently reachable.
444.Sp 572.Sp
… …
450disables routing. The idea behind this is that some hosts can, if 578disables 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 579required, 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 580local 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 581\&\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. 582not use by default\*(R" switch.
455.IP "connect = ondemand | never | always | disabled" 4 583.IP "tcp-port = port-number" 4
456.IX Item "connect = ondemand | never | always | disabled" 584.IX Item "tcp-port = port-number"
457Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always 585Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number.
458try to establish and keep a connection to the given host), \f(CW\*(C`never\*(C'\fR 586.IP "udp-port = port-number" 4
459(nevr initiate a connection to the given host, but accept connections), 587.IX Item "udp-port = port-number"
460\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and 588Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not
461take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad, 589officially assigned by \s-1IANA\s0!).
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" 590.SH "CONFIG DIRECTORY LAYOUT"
483.IX Header "CONFIG DIRECTORY LAYOUT" 591.IX Header "CONFIG DIRECTORY LAYOUT"
484The default (or recommended) directory layout for the config directory is: 592The default (or recommended) directory layout for the config directory is:
485.IP "gvpe.conf" 4 593.IP "\(bu" 4
486.IX Item "gvpe.conf" 594.IX Xref "gvpe.conf"
487The config file. 595The config file.
488.IP "if-up" 4 596.IP "\(bu" 4
489.IX Item "if-up" 597.IX Xref "if-up"
490The if-up script 598The if-up script
491.IP "node\-up, node-down" 4 599.IP "," 4
492.IX Item "node-up, node-down" 600.IX Xref "node-up node-down"
493If used the node up or node-down scripts. 601If used the node up or node-down scripts.
494.IP "hostkey" 4 602.IP "\(bu" 4
495.IX Item "hostkey" 603.IX Xref "hostkey"
496The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host. 604The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host.
497.IP "pubkey/nodename" 4 605.IP "\(bu" 4
498.IX Item "pubkey/nodename" 606.IX Xref "pubkey nodename"
499The public keys of the other nodes, one file per node. 607The public keys of the other nodes, one file per node.
500.SH "SEE ALSO" 608.SH "SEE ALSO"
501.IX Header "SEE ALSO" 609.IX Header "SEE ALSO"
502\&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8). 610\&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8).
503.SH "AUTHOR" 611.SH "AUTHOR"

Diff Legend

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