--- gvpe/doc/gvpe.conf.5	2005/03/07 01:31:26	1.8
+++ gvpe/doc/gvpe.conf.5	2008/08/10 10:35:26	1.20
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -25,11 +25,11 @@
 ..
 .\" Set up some character translations and predefined strings.  \*(-- will
 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
-.\" double quote, and \*(R" will give a right double quote.  | will give a
-.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
-.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
-.\" expand to `' in nroff, nothing in troff, for use with C<>.
-.tr \(*W-|\(bv\*(Tr
+.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
+.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
+.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
+.\" nothing in troff, for use with C<>.
+.tr \(*W-
 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
 .ie n \{\
 .    ds -- \(*W-
@@ -48,22 +48,25 @@
 .    ds R" ''
 'br\}
 .\"
+.\" Escape single quotes in literal strings from groff's Unicode transform.
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\"
 .\" If the F register is turned on, we'll generate index entries on stderr for
 .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.if \nF \{\
+.ie \nF \{\
 .    de IX
 .    tm Index:\\$1\t\\n%\t"\\$2"
 ..
 .    nr % 0
 .    rr F
 .\}
-.\"
-.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
-.\" way too many mistakes in technical documents.
-.hy 0
-.if n .na
+.el \{\
+.    de IX
+..
+.\}
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -129,29 +132,27 @@
 .\" ========================================================================
 .\"
 .IX Title "GVPE.CONF 5"
-.TH GVPE.CONF 5 "2005-03-07" "1.8" "GNU Virtual Private Ethernet"
+.TH GVPE.CONF 5 "2008-08-07" "2.2" "GNU Virtual Private Ethernet"
+.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.if n .ad l
+.nh
 .SH "NAME"
 gvpe.conf \- configuration file for the GNU VPE daemon
 .SH "SYNOPSIS"
 .IX Header "SYNOPSIS"
 .Vb 3
-\&   udp-port = 407
+\&   udp\-port = 407
 \&   mtu = 1492
 \&   ifname = vpn0
-.Ve
-.PP
-.Vb 2
+\&
 \&   node = branch1
 \&   hostname = 1.2.3.4
-.Ve
-.PP
-.Vb 3
+\&
 \&   node = branch2
 \&   hostname = www.example.net
-\&   udp-port = 500       # this host uses a different udp-port
-.Ve
-.PP
-.Vb 2
+\&   udp\-port = 500       # this host uses a different udp\-port
+\&
 \&   node = branch3
 \&   connect = ondemand
 .Ve
@@ -160,8 +161,8 @@
 The gvpe config file consists of a series of lines that contain \f(CW\*(C`variable
 = value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and
 extend to the end of the line. They can be used on their own lines, or
-after any directives. Spaces are allowed before or after the \f(CW\*(C`=\*(C'\fR sign or
-after values, but not within the variable names or values themselves.
+after any directives. Whitespace is allowed around the \f(CW\*(C`=\*(C'\fR sign or after
+values, but not within the variable names or values themselves.
 .PP
 The only exception to the above is the \*(L"on\*(R" directive that can prefix any
 \&\f(CW\*(C`name = value\*(C'\fR setting and will only \*(L"execute\*(R" it on the named node, or
@@ -204,57 +205,120 @@
 .IX Item "dns-forw-port = port-number"
 The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR,
 which is fine in most cases).
+.IP "dns-max-outstanding = integer-number-of-requests" 4
+.IX Item "dns-max-outstanding = integer-number-of-requests"
+The maximum number of outstanding \s-1DNS\s0 transport requests
+(default: \f(CW100\fR). \s-1GVPE\s0 will never issue more requests then the given
+limit without receiving replies. In heavily overloaded situations it might
+help to set this to a low number (e.g. \f(CW3\fR or even \f(CW1\fR) to limit the
+number of parallel requests.
+.Sp
+The default should be working ok for most links.
+.IP "dns-overlap-factor = float" 4
+.IX Item "dns-overlap-factor = float"
+The \s-1DNS\s0 transport uses the minimum request latency (\fBmin_latency\fR) seen
+during a connection as it's timing base. This factor (default: \f(CW0.5\fR,
+must be > 0) is multiplied by \fBmin_latency\fR to get the maximum sending
+rate (= minimum send interval), i.e. a factor of \f(CW1\fR means that a new
+request might be generated every \fBmin_latency\fR seconds, which means on
+average there should only ever be one outstanding request.  A factor of
+\&\f(CW0.5\fR means that \s-1GVPE\s0 will send requests twice as often as the minimum
+latency measured.
+.Sp
+For congested or picky dns forwarders you could use a value nearer to or
+exceeding \f(CW1\fR.
+.Sp
+The default should be working ok for most links.
+.IP "dns-send-interval = send-interval-in-seconds" 4
+.IX Item "dns-send-interval = send-interval-in-seconds"
+The minimum send interval (= maximum rate) that the \s-1DNS\s0 transport will
+use to send new \s-1DNS\s0 requests. \s-1GVPE\s0 will not exceed this rate even when
+the latency is very low. The default is \f(CW0.01\fR, which means \s-1GVPE\s0 will
+not send more than 100 \s-1DNS\s0 requests per connection per second. For
+high-bandwidth links you could go lower, e.g. to \f(CW0.001\fR or so. For
+congested or rate-limited links, you might want to go higher, say \f(CW0.1\fR,
+\&\f(CW0.2\fR or even higher.
+.Sp
+The default should be working ok for most links.
+.IP "dns-timeout-factor = float" 4
+.IX Item "dns-timeout-factor = float"
+Factor to multiply the \f(CW\*(C`min_latency\*(C'\fR (see \f(CW\*(C`dns\-overlap\-factor\*(C'\fR) by to
+get request timeouts. The default of \f(CW8\fR means that the \s-1DNS\s0 transport
+will resend the request when no reply has been received for longer than
+eight times the minimum (= expected) latency, assuming the request or
+reply has been lost.
+.Sp
+For congested links a higher value might be necessary (e.g. \f(CW30\fR). If
+the link is very stable lower values (e.g. \f(CW2\fR) might work
+nicely. Values near or below \f(CW1\fR makes no sense whatsoever.
+.Sp
+The default should be working ok for most links but will result in low
+throughput if packet loss is high.
 .IP "if-up = relative-or-absolute-path" 4
 .IX Item "if-up = relative-or-absolute-path"
 Sets the path of a script that should be called immediately after the
 network interface is initialized (but not neccessarily up). The following
-environment variables are passed to it (the values are just examples):
+environment variables are passed to it (the values are just examples).
+.Sp
+Variables that have the same value on all nodes:
 .RS 4
 .IP "CONFBASE=/etc/gvpe" 4
 .IX Item "CONFBASE=/etc/gvpe"
 The configuration base directory.
 .IP "IFNAME=vpn0" 4
 .IX Item "IFNAME=vpn0"
-The interface to initialize.
+The network interface to initialize.
+.IP "IFTYPE=native # or tincd" 4
+.IX Item "IFTYPE=native # or tincd"
+.PD 0
+.IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4
+.IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.."
+.PD
+The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the
+\&\s-1OS\s0 name in lowercase) that this \s-1GVPE\s0 was configured for. Can be used to
+select the correct syntax to use for network-related commands.
 .IP "MTU=1436" 4
 .IX Item "MTU=1436"
 The \s-1MTU\s0 to set the interface to. You can use lower values (if done
 consistently on all hosts), but this is usually ineffective.
+.IP "NODES=5" 4
+.IX Item "NODES=5"
+The number of nodes in this \s-1GVPE\s0 network.
+.RE
+.RS 4
+.Sp
+Variables that are node-specific and with values pertaining to the node
+running this \s-1GVPE:\s0
+.IP "IFUPDATA=string" 4
+.IX Item "IFUPDATA=string"
+The value of the configuration directive \f(CW\*(C`if\-up\-data\*(C'\fR.
 .IP "MAC=fe:fd:80:00:00:01" 4
 .IX Item "MAC=fe:fd:80:00:00:01"
-The \s-1MAC\s0 address to set the interface to. The script *must* set the
-interface \s-1MAC\s0 to this value. You will most likely use one of these:
+The \s-1MAC\s0 address the network interface has to use.
 .Sp
-.Vb 2
-\&   ip link set $IFNAME address $MAC mtu $MTU up # GNU/Linux
-\&   ifconfig $IFNAME ether $MAC mtu $MTU up      # FreeBSD
-.Ve
-.Sp
-Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for platform-specific information.
-.IP "IFTYPE=native # or tincd" 4
-.IX Item "IFTYPE=native # or tincd"
-.PD 0
-.IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4
-.IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.."
-.PD
-The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the os
-name in lowercase) that this gvpe was configured for. Can be used to select
-the correct syntax to use for network-related commands.
+Might be used to initialize interfaces on platforms where \s-1GVPE\s0 does not
+do this automatically.  Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for
+platform-specific information.
 .IP "NODENAME=branch1" 4
 .IX Item "NODENAME=branch1"
-The nickname of the current node, as passed to the gvpe daemon.
+The nickname of the node.
 .IP "NODEID=1" 4
 .IX Item "NODEID=1"
-The numerical node id of the current node. The first node mentioned in the
-config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on.
+The numerical node \s-1ID\s0 of the node running this instance of \s-1GVPE\s0. The first
+node mentioned in the config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on.
 .RE
 .RS 4
 .Sp
+In addition, all node-specific variables (except \f(CW\*(C`NODEID\*(C'\fR) will be
+available with a postfix of \f(CW\*(C`_nodeid\*(C'\fR, which contains the value for that
+node, e.g. the \f(CW\*(C`MAC_1\*(C'\fR variable contains the \s-1MAC\s0 address of node #1, while
+the \f(CW\*(C`NODENAME_22\*(C'\fR variable contains the name of node #22.
+.Sp
 Here is a simple if-up script:
 .Sp
 .Vb 5
 \&   #!/bin/sh
-\&   ip link set $IFNAME address $MAC mtu $MTU up
+\&   ip link set $IFNAME up
 \&   [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME
 \&   [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME
 \&   ip route add 10.0.0.0/8 dev $IFNAME
@@ -311,9 +375,9 @@
 Example:
 .Sp
 .Vb 3
-\&   http-proxy-host = proxy.example.com
-\&   http-proxy-port = 3128       # 8080 is another common choice
-\&   http-proxy-auth = schmorp:grumbeere
+\&   http\-proxy\-host = proxy.example.com
+\&   http\-proxy\-port = 3128       # 8080 is another common choice
+\&   http\-proxy\-auth = schmorp:grumbeere
 .Ve
 .IP "http-proxy-port = proxy-tcp-port" 4
 .IX Item "http-proxy-port = proxy-tcp-port"
@@ -351,10 +415,13 @@
 argument to the gvpe daemon.
 .IP "node-up = relative-or-absolute-path" 4
 .IX Item "node-up = relative-or-absolute-path"
-Sets a command (default: no script) that should be called whenever a
-connection is established (even on rekeying operations). In addition
-to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment
-variables will be set:
+Sets a command (default: none) that should be called whenever a connection
+is established (even on rekeying operations). Note that node\-up/down
+scripts will be run asynchronously, but execution is serialised, so there
+will only ever be one such script running.
+.Sp
+In addition to all the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following
+environment variables will be set:
 .RS 4
 .IP "DESTNODE=branch2" 4
 .IX Item "DESTNODE=branch2"
@@ -385,7 +452,7 @@
 \&     echo update delete $DESTNODE.lowttl.example.net. a
 \&     echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP
 \&     echo   
-\&   } | nsupdate -d -k $CONFBASE:key.example.net.
+\&   } | nsupdate \-d \-k $CONFBASE:key.example.net.
 .Ve
 .RE
 .IP "node-down = relative-or-absolute-path" 4
@@ -412,10 +479,13 @@
 reestablished every \f(CW\*(C`rekey\*(C'\fR seconds.
 .Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0"
 .IX Subsection "NODE SPECIFIC SETTINGS"
-The following settings are node\-specific, that is, every node can have
+The following settings are node-specific, that is, every node can have
 different settings, even within the same gvpe instance. Settings that are
-executed before the first node section set the defaults, settings that are
-executed within a node section only apply to the given node.
+set before the first node section set the defaults, settings that are
+set within a node section only apply to the given node.
+.IP "allow-direct = nodename" 4
+.IX Item "allow-direct = nodename"
+Allow direct connections to this node. See \f(CW\*(C`deny\-direct\*(C'\fR for more info.
 .IP "compress = yes|true|on | no|false|off" 4
 .IX Item "compress = yes|true|on | no|false|off"
 Wether to compress data packets sent to this host (default: \f(CW\*(C`yes\*(C'\fR).
@@ -426,9 +496,35 @@
 Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always
 try to establish and keep a connection to the given host), \f(CW\*(C`never\*(C'\fR
 (never initiate a connection to the given host, but accept connections),
-\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and
-take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad,
-don't talk to it).
+\&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection when there are outstanding
+packets in the queue and take it down after the keepalive interval) or
+\&\f(CW\*(C`disabled\*(C'\fR (node is bad, don't talk to it).
+.IP "deny-direct = nodename | *" 4
+.IX Item "deny-direct = nodename | *"
+Deny direct connections to the specified node (or all nodes when \f(CW\*(C`*\*(C'\fR
+is given). Only one node can be specified, but you can use multiple
+\&\f(CW\*(C`allow\-direct\*(C'\fR and \f(CW\*(C`deny\-direct\*(C'\fR statements. This only makes sense in
+networks with routers, as routers are required for indirect connections.
+.Sp
+Sometimes, a node cannot reach some other nodes for reasons of network
+connectivity. For example, a node behind a firewall that only allows
+conenctions to/from a single other node in the network. In this case one
+should specify \f(CW\*(C`deny\-direct = *\*(C'\fR and \f(CW\*(C`allow\-direct = othernodename\*(C'\fR (the other
+node \fImust\fR be a router for this to work).
+.Sp
+The algorithm to check wether a connection may be direct is as follows:
+.Sp
+1. Other node mentioned in a \f(CW\*(C`allow\-direct\*(C'\fR? If yes, allow the connection.
+.Sp
+2. Other node mentioned in a \f(CW\*(C`deny\-direct\*(C'\fR? If yes, deny direct connections.
+.Sp
+3. Allow the connection.
+.Sp
+That is, \f(CW\*(C`allow\-direct\*(C'\fR takes precedence over \f(CW\*(C`deny\-direct\*(C'\fR.
+.Sp
+The check is done in both directions, i.e. both nodes must allow a direct
+connection before one is attempted, so you only need to specify connect
+limitations on one node.
 .IP "dns-domain = domain-suffix" 4
 .IX Item "dns-domain = domain-suffix"
 The \s-1DNS\s0 domain suffix that points to the \s-1DNS\s0 tunnel server for this node.
@@ -437,15 +533,15 @@
 i.e.
 .Sp
 .Vb 2
-\&   dns-domainname = tunnel.example.net
-\&   dns-hostname   = tunnel-server.example.net
+\&   dns\-domainname = tunnel.example.net
+\&   dns\-hostname   = tunnel\-server.example.net
 .Ve
 .Sp
 Corresponds to the following \s-1DNS\s0 entries in the \f(CW\*(C`example.net\*(C'\fR domain:
 .Sp
 .Vb 2
-\&   tunnel.example.net.         NS tunnel-server.example.net.
-\&   tunnel-server.example.net.  A  13.13.13.13
+\&   tunnel.example.net.         NS tunnel\-server.example.net.
+\&   tunnel\-server.example.net.  A  13.13.13.13
 .Ve
 .IP "dns-hostname = hostname/ip" 4
 .IX Item "dns-hostname = hostname/ip"
@@ -457,35 +553,61 @@
 The port to bind the \s-1DNS\s0 tunnel socket to. Must be \f(CW53\fR on \s-1DNS\s0 tunnel servers.
 .IP "enable-dns = yes|true|on | no|false|off" 4
 .IX Item "enable-dns = yes|true|on | no|false|off"
+See \fIgvpe.protocol\fR\|(7) for a description of the \s-1DNS\s0 transport
+protocol. Avoid this protocol if you can.
+.Sp
 Enable the \s-1DNS\s0 tunneling protocol on this node, either as server or as
-client (only available when gvpe was compiled with \f(CW\*(C`\-\-enable\-dns\*(C'\fR).
+client. Support for this transport protocol is only available when gvpe
+was compiled using the \f(CW\*(C`\-\-enable\-dns\*(C'\fR option.
+.IP "enable-icmp = yes|true|on | no|false|off" 4
+.IX Item "enable-icmp = yes|true|on | no|false|off"
+See \fIgvpe.protocol\fR\|(7) for a description of the \s-1ICMP\s0 transport protocol.
 .Sp
-This is the worst choice of transport protocol with respect to overhead
-(overhead cna be 2\-3 times higher than the transferred data), and probably
-the best choice when tunneling through firewalls.
+Enable the \s-1ICMP\s0 transport using icmp packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this
+node.
 .IP "enable-rawip = yes|true|on | no|false|off" 4
 .IX Item "enable-rawip = yes|true|on | no|false|off"
+See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW\s0 \s-1IP\s0 transport protocol.
+.Sp
 Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol
-(default: \f(CW\*(C`no\*(C'\fR). This is the best choice, since the minimum overhead per
-packet is only 38 bytes, as opposed to \s-1UDP\s0's 58 (or \s-1TCP\s0's 60+).
+(default: \f(CW\*(C`no\*(C'\fR).
 .IP "enable-tcp = yes|true|on | no|false|off" 4
 .IX Item "enable-tcp = yes|true|on | no|false|off"
+See \fIgvpe.protocol\fR\|(7) for a description of the \s-1TCP\s0 transport protocol.
+.Sp
 Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port
-(default: \f(CW\*(C`no\*(C'\fR). Support for this horribly unsuitable protocol is only
-available when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option. Never
-use this transport unless you really must, it is very inefficient and
-resource-intensive compared to the other transports (except for \s-1DNS\s0, which
-is worse).
+(default: \f(CW\*(C`no\*(C'\fR). Support for this transport protocol is only available
+when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option.
 .IP "enable-udp = yes|true|on | no|false|off" 4
 .IX Item "enable-udp = yes|true|on | no|false|off"
+See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol.
+.Sp
 Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR,
 unless no other protocol is enabled for a node, in which case this
-protocol is enabled automatically). This is a good general choice since
-\&\s-1UDP\s0 tunnels well through many firewalls.
+protocol is enabled automatically).
 .Sp
 \&\s-1NOTE:\s0 Please specify \f(CW\*(C`enable\-udp = yes\*(C'\fR if you want t use it even though
 it might get switched on automatically, as some future version might
 default to another default protocol.
+.IP "hostname = hostname | ip    [can not be defaulted]" 4
+.IX Item "hostname = hostname | ip    [can not be defaulted]"
+Forces the address of this node to be set to the given dns hostname or ip
+address. It will be resolved before each connect request, so dyndns should
+work fine. If this setting is not specified and a router is available,
+then the router will be queried for the address of this node. Otherwise,
+the connection attempt will fail.
+.IP "icmp-type = integer" 4
+.IX Item "icmp-type = integer"
+Sets the type value to be used for outgoing (and incoming) packets sent
+via the \s-1ICMP\s0 transport.
+.Sp
+The default is \f(CW0\fR (which is \f(CW\*(C`echo\-reply\*(C'\fR, also known as
+\&\*(L"ping-replies\*(R"). Other useful values include \f(CW8\fR (\f(CW\*(C`echo\-request\*(C'\fR, a.k.a.
+\&\*(L"ping\*(R") and \f(CW11\fR (\f(CW\*(C`time\-exceeded\*(C'\fR), but any 8\-bit value can be used.
+.IP "if-up-data = value" 4
+.IX Item "if-up-data = value"
+The value specified using this directive will be passed to the \f(CW\*(C`if\-up\*(C'\fR
+script in the environment variable \f(CW\*(C`IFUPDATA\*(C'\fR.
 .IP "inherit-tos = yes|true|on | no|false|off" 4
 .IX Item "inherit-tos = yes|true|on | no|false|off"
 Wether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when
@@ -500,6 +622,18 @@
 sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on
 connections to routers that usually are stable but sometimes are down, to
 assure quick reconnections even after longer downtimes.
+.IP "max-ttl = seconds" 4
+.IX Item "max-ttl = seconds"
+Expire packets that couldn't be sent after this many seconds
+(default: \f(CW60\fR). Gvpe will normally queue packets for a node without an
+active connection, in the hope of establishing a connection soon. This
+value specifies the maximum lifetime a packet will stay in the queue, if a
+packet gets older, it will be thrown away.
+.IP "max-queue = positive-number" 4
+.IX Item "max-queue = positive-number"
+The maximum number of packets that will be queued (default: \f(CW512\fR)
+for this node. If more packets are sent then earlier packets will be
+expired. See \f(CW\*(C`max\-ttl\*(C'\fR, above.
 .IP "router-priority = 0 | 1 | positive\-number>=2" 4
 .IX Item "router-priority = 0 | 1 | positive-number>=2"
 Sets the router priority of the given host (default: \f(CW0\fR, disabled). If
@@ -527,19 +661,19 @@
 .SH "CONFIG DIRECTORY LAYOUT"
 .IX Header "CONFIG DIRECTORY LAYOUT"
 The default (or recommended) directory layout for the config directory is:
-.IP "\(bu" 4
+.IP "" 4
 .IX Xref "gvpe.conf"
 The config file.
-.IP "\(bu" 4
+.IP "" 4
 .IX Xref "if-up"
 The if-up script
 .IP "," 4
 .IX Xref "node-up node-down"
 If used the node up or node-down scripts.
-.IP "\(bu" 4
+.IP "" 4
 .IX Xref "hostkey"
 The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host.
-.IP "\(bu" 4
+.IP "" 4
 .IX Xref "pubkey nodename"
 The public keys of the other nodes, one file per node.
 .SH "SEE ALSO"
@@ -547,4 +681,4 @@
 \&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8).
 .SH "AUTHOR"
 .IX Header "AUTHOR"
-Marc Lehmann <gvpe@plan9.de>
+Marc Lehmann <gvpe@schmorp.de>