… | |
… | |
2 | |
2 | |
3 | gvpe.conf - configuration file for the GNU VPE daemon |
3 | gvpe.conf - configuration file for the GNU VPE daemon |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
|
|
7 | # global options for all nodes |
7 | udp-port = 407 |
8 | udp-port = 407 |
8 | mtu = 1492 |
9 | mtu = 1492 |
9 | ifname = vpn0 |
10 | ifname = vpn0 |
10 | |
11 | |
|
|
12 | # first node is named branch1 and is at 1.2.3.4 |
11 | node = branch1 |
13 | node = branch1 |
12 | hostname = 1.2.3.4 |
14 | hostname = 1.2.3.4 |
13 | |
15 | |
|
|
16 | # second node uses dns to resolve the address |
14 | node = branch2 |
17 | node = branch2 |
15 | hostname = www.example.net |
18 | hostname = www.example.net |
16 | udp-port = 500 # this host uses a different udp-port |
19 | udp-port = 500 # this host uses a different udp-port |
17 | |
20 | |
|
|
21 | # third node has no fixed ip address |
18 | node = branch3 |
22 | node = branch3 |
19 | connect = ondemand |
23 | connect = ondemand |
20 | |
24 | |
21 | =head1 DESCRIPTION |
25 | =head1 DESCRIPTION |
22 | |
26 | |
… | |
… | |
28 | |
32 | |
29 | The only exception to the above is the "on" directive that can prefix any |
33 | The only exception to the above is the "on" directive that can prefix any |
30 | C<name = value> setting and will only "execute" it on the named node, or |
34 | C<name = value> setting and will only "execute" it on the named node, or |
31 | (if the nodename starts with "!") on all nodes except the named one. |
35 | (if the nodename starts with "!") on all nodes except the named one. |
32 | |
36 | |
33 | name = value |
37 | For example, set the MTU to C<1450> everywhere, loglevel to C<noise> on |
|
|
38 | branch1, and connect to C<ondemand> everywhere but on branch2: |
|
|
39 | |
|
|
40 | mtu = 1450 |
34 | on branch1 loglevel = noise |
41 | on branch1 loglevel = noise |
35 | on !branch2 connect = ondemand |
42 | on !branch2 connect = ondemand |
36 | |
43 | |
37 | All settings are executed "in order", that is, later settings of the same |
44 | All settings are applied "in order", that is, later settings of the same |
38 | variable overwrite earlier ones. |
45 | variable overwrite earlier ones. |
39 | |
46 | |
40 | =head1 ANATOMY OF A CONFIG FILE |
47 | =head1 ANATOMY OF A CONFIG FILE |
41 | |
48 | |
42 | Usually, a config file starts with global settings (like the udp port to |
49 | Usually, a config file starts with a few global settings (like the UDP |
43 | listen on), followed by node-specific sections that begin with a C<node = |
50 | port to listen on), followed by node-specific sections that begin with a |
44 | nickname> line. |
51 | C<node = nickname> line. |
45 | |
52 | |
46 | Every node that is part of the network must have a section that starts |
53 | Every node that is part of the network must have a section that starts |
47 | with C<node = nickname>. The number and order of the nodes is important |
54 | with C<node = nickname>. The number and order of the nodes is important |
48 | and must be the same on all hosts. It is not uncommon for node sections to |
55 | and must be the same on all nodes. It is not uncommon for node sections to |
49 | be completely empty - if the default values are right. |
56 | be completely empty - if the default values are right. |
50 | |
57 | |
51 | Node-specific settings can be used at any time. If used before the first |
58 | Node-specific settings can be used at any time. If used before the first |
52 | node section they will set the default values for all following nodes. |
59 | node section they will set the default values for all following nodes. |
53 | |
60 | |
… | |
… | |
62 | |
69 | |
63 | =over 4 |
70 | =over 4 |
64 | |
71 | |
65 | =item dns-forw-host = hostname/ip |
72 | =item dns-forw-host = hostname/ip |
66 | |
73 | |
67 | The dns server to forward dns requests to for the DNS tunnel protocol |
74 | The DNS server to forward DNS requests to for the DNS tunnel protocol |
68 | (default: C<127.0.0.1>, changing it is highly recommended). |
75 | (default: C<127.0.0.1>, changing it is highly recommended). |
69 | |
76 | |
70 | =item dns-forw-port = port-number |
77 | =item dns-forw-port = port-number |
71 | |
78 | |
72 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
79 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
… | |
… | |
78 | (default: C<100>). GVPE will never issue more requests then the given |
85 | (default: C<100>). GVPE will never issue more requests then the given |
79 | limit without receiving replies. In heavily overloaded situations it might |
86 | limit without receiving replies. In heavily overloaded situations it might |
80 | help to set this to a low number (e.g. C<3> or even C<1>) to limit the |
87 | help to set this to a low number (e.g. C<3> or even C<1>) to limit the |
81 | number of parallel requests. |
88 | number of parallel requests. |
82 | |
89 | |
83 | The default should be working ok for most links. |
90 | The default should be working OK for most links. |
84 | |
91 | |
85 | =item dns-overlap-factor = float |
92 | =item dns-overlap-factor = float |
86 | |
93 | |
87 | The DNS transport uses the minimum request latency (B<min_latency>) seen |
94 | The DNS transport uses the minimum request latency (B<min_latency>) seen |
88 | during a connection as it's timing base. This factor (default: C<0.5>, |
95 | during a connection as it's timing base. This factor (default: C<0.5>, |
… | |
… | |
91 | request might be generated every B<min_latency> seconds, which means on |
98 | request might be generated every B<min_latency> seconds, which means on |
92 | average there should only ever be one outstanding request. A factor of |
99 | average there should only ever be one outstanding request. A factor of |
93 | C<0.5> means that GVPE will send requests twice as often as the minimum |
100 | C<0.5> means that GVPE will send requests twice as often as the minimum |
94 | latency measured. |
101 | latency measured. |
95 | |
102 | |
96 | For congested or picky dns forwarders you could use a value nearer to or |
103 | For congested or picky DNS forwarders you could use a value nearer to or |
97 | exceeding C<1>. |
104 | exceeding C<1>. |
98 | |
105 | |
99 | The default should be working ok for most links. |
106 | The default should be working OK for most links. |
100 | |
107 | |
101 | =item dns-send-interval = send-interval-in-seconds |
108 | =item dns-send-interval = send-interval-in-seconds |
102 | |
109 | |
103 | The minimum send interval (= maximum rate) that the DNS transport will |
110 | The minimum send interval (= maximum rate) that the DNS transport will |
104 | use to send new DNS requests. GVPE will not exceed this rate even when |
111 | use to send new DNS requests. GVPE will not exceed this rate even when |
… | |
… | |
106 | not send more than 100 DNS requests per connection per second. For |
113 | not send more than 100 DNS requests per connection per second. For |
107 | high-bandwidth links you could go lower, e.g. to C<0.001> or so. For |
114 | high-bandwidth links you could go lower, e.g. to C<0.001> or so. For |
108 | congested or rate-limited links, you might want to go higher, say C<0.1>, |
115 | congested or rate-limited links, you might want to go higher, say C<0.1>, |
109 | C<0.2> or even higher. |
116 | C<0.2> or even higher. |
110 | |
117 | |
111 | The default should be working ok for most links. |
118 | The default should be working OK for most links. |
112 | |
119 | |
113 | =item dns-timeout-factor = float |
120 | =item dns-timeout-factor = float |
114 | |
121 | |
115 | Factor to multiply the C<min_latency> (see C<dns-overlap-factor>) by to |
122 | Factor to multiply the C<min_latency> (see C<dns-overlap-factor>) by to |
116 | get request timeouts. The default of C<8> means that the DNS transport |
123 | get request timeouts. The default of C<8> means that the DNS transport |
117 | will resend the request when no reply has been received for longer than |
124 | will resend the request when no reply has been received for longer than |
118 | eight times the minimum (= expected) latency, assuming the request or |
125 | eight times the minimum (= expected) latency, assuming the request or |
119 | reply has been lost. |
126 | reply has been lost. |
120 | |
127 | |
121 | For congested links a higher value might be necessary (e.g. C<30>). If the |
128 | For congested links a higher value might be necessary (e.g. C<30>). If |
122 | link is very stable lower values (e.g. C<2>) might work nicely. Values |
129 | the link is very stable lower values (e.g. C<2>) might work |
123 | near or below C<1> makes no sense whatsoever. |
130 | nicely. Values near or below C<1> makes no sense whatsoever. |
124 | |
131 | |
125 | The default should be working ok for most links. |
132 | The default should be working OK for most links but will result in low |
|
|
133 | throughput if packet loss is high. |
126 | |
134 | |
127 | =item if-up = relative-or-absolute-path |
135 | =item if-up = relative-or-absolute-path |
128 | |
136 | |
129 | Sets the path of a script that should be called immediately after the |
137 | Sets the path of a script that should be called immediately after the |
130 | network interface is initialized (but not neccessarily up). The following |
138 | network interface is initialized (but not necessarily up). The following |
131 | environment variables are passed to it (the values are just examples). |
139 | environment variables are passed to it (the values are just examples). |
132 | |
140 | |
133 | Variables that have the same value on all nodes: |
141 | Variables that have the same value on all nodes: |
134 | |
142 | |
135 | =over 4 |
143 | =over 4 |
… | |
… | |
151 | select the correct syntax to use for network-related commands. |
159 | select the correct syntax to use for network-related commands. |
152 | |
160 | |
153 | =item MTU=1436 |
161 | =item MTU=1436 |
154 | |
162 | |
155 | The MTU to set the interface to. You can use lower values (if done |
163 | The MTU to set the interface to. You can use lower values (if done |
156 | consistently on all hosts), but this is usually ineffective. |
164 | consistently on all nodes), but this is usually either inefficient or |
|
|
165 | simply ineffective. |
157 | |
166 | |
158 | =item NODES=5 |
167 | =item NODES=5 |
159 | |
168 | |
160 | The number of nodes in this GVPE network. |
169 | The number of nodes in this GVPE network. |
161 | |
170 | |
… | |
… | |
173 | =item MAC=fe:fd:80:00:00:01 |
182 | =item MAC=fe:fd:80:00:00:01 |
174 | |
183 | |
175 | The MAC address the network interface has to use. |
184 | The MAC address the network interface has to use. |
176 | |
185 | |
177 | Might be used to initialize interfaces on platforms where GVPE does not |
186 | Might be used to initialize interfaces on platforms where GVPE does not |
178 | do this automatically. Please see the C<gvpe.osdep(5)> manpage for |
187 | do this automatically. Please see the C<gvpe.osdep(5)> man page for |
179 | platform-specific information. |
188 | platform-specific information. |
180 | |
189 | |
181 | =item NODENAME=branch1 |
190 | =item NODENAME=branch1 |
182 | |
191 | |
183 | The nickname of the node. |
192 | The nickname of the node. |
… | |
… | |
200 | ip link set $IFNAME up |
209 | ip link set $IFNAME up |
201 | [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME |
210 | [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME |
202 | [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME |
211 | [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME |
203 | ip route add 10.0.0.0/8 dev $IFNAME |
212 | ip route add 10.0.0.0/8 dev $IFNAME |
204 | |
213 | |
205 | More complicated examples (using routing to reduce arp traffic) can be |
214 | More complicated examples (using routing to reduce ARP traffic) can be |
206 | found in the etc/ subdirectory of the distribution. |
215 | found in the F<etc/> subdirectory of the distribution. |
207 | |
216 | |
208 | =item ifname = devname |
217 | =item ifname = devname |
209 | |
218 | |
210 | Sets the tun interface name to the given name. The default is OS-specific |
219 | Sets the tun interface name to the given name. The default is OS-specific |
211 | and most probably something like C<tun0>. |
220 | and most probably something like C<tun0>. |
… | |
… | |
220 | device. |
229 | device. |
221 | |
230 | |
222 | =item ip-proto = numerical-ip-protocol |
231 | =item ip-proto = numerical-ip-protocol |
223 | |
232 | |
224 | Sets the protocol number to be used for the rawip protocol. This is a |
233 | Sets the protocol number to be used for the rawip protocol. This is a |
225 | global option because all hosts must use the same protocol, and since |
234 | global option because all nodes must use the same protocol, and since |
226 | there are no port numbers, you cannot easily run more than one gvpe |
235 | there are no port numbers, you cannot easily run more than one gvpe |
227 | instance using the same protocol, nor can you share the protocol with |
236 | instance using the same protocol, nor can you share the protocol with |
228 | other programs. |
237 | other programs. |
229 | |
238 | |
230 | The default is 47 (GRE), which has a good chance of tunneling through |
239 | The default is 47 (GRE), which has a good chance of tunneling |
231 | firewalls (but note that the rawip protocol is not GRE compatible). Other |
240 | through firewalls (but note that gvpe's rawip protocol is not GRE |
232 | common choices are 50 (IPSEC, ESP), 51 (IPSEC, AH), 4 (IPIP tunnels) or 98 |
241 | compatible). Other common choices are 50 (IPSEC, ESP), 51 (IPSEC, AH), 4 |
233 | (ENCAP, rfc1241) |
242 | (IPIP tunnels) or 98 (ENCAP, rfc1241) |
234 | |
243 | |
235 | =item http-proxy-host = hostname/ip |
244 | =item http-proxy-host = hostname/ip |
236 | |
245 | |
237 | The C<http-proxy-*> family of options are only available if gvpe was |
246 | The C<http-proxy-*> family of options are only available if gvpe was |
238 | compiled with the C<--enable-http-proxy> option and enable tunneling of |
247 | compiled with the C<--enable-http-proxy> option and enable tunneling of |
… | |
… | |
241 | C<http-proxy-host> and C<http-proxy-port> should specify the hostname and |
250 | C<http-proxy-host> and C<http-proxy-port> should specify the hostname and |
242 | port number of the proxy server. See C<http-proxy-loginpw> if your proxy |
251 | port number of the proxy server. See C<http-proxy-loginpw> if your proxy |
243 | requires authentication. |
252 | requires authentication. |
244 | |
253 | |
245 | Please note that gvpe will still try to resolve all hostnames in the |
254 | Please note that gvpe will still try to resolve all hostnames in the |
246 | configuration file, so if you are behind a proxy without access to a dns |
255 | configuration file, so if you are behind a proxy without access to a DNS |
247 | server better use numerical IP addresses. |
256 | server better use numerical IP addresses. |
248 | |
257 | |
249 | To make best use of this option disable all protocols except tcp in your |
258 | To make best use of this option disable all protocols except TCP in your |
250 | config file and make sure your routers (or all other hosts) are listening |
259 | config file and make sure your routers (or all other nodes) are listening |
251 | on a port that the proxy allows (443, https, is a common choice). |
260 | on a port that the proxy allows (443, https, is a common choice). |
252 | |
261 | |
253 | If you have a router, connecting to it will suffice. Otherwise tcp must be |
262 | If you have a router, connecting to it will suffice. Otherwise TCP must be |
254 | enabled on all hosts. |
263 | enabled on all nodes. |
255 | |
264 | |
256 | Example: |
265 | Example: |
257 | |
266 | |
258 | http-proxy-host = proxy.example.com |
267 | http-proxy-host = proxy.example.com |
259 | http-proxy-port = 3128 # 8080 is another common choice |
268 | http-proxy-port = 3128 # 8080 is another common choice |
… | |
… | |
264 | The port where your proxy server listens. |
273 | The port where your proxy server listens. |
265 | |
274 | |
266 | =item http-proxy-auth = login:password |
275 | =item http-proxy-auth = login:password |
267 | |
276 | |
268 | The optional login and password used to authenticate to the proxy server, |
277 | The optional login and password used to authenticate to the proxy server, |
269 | seperated by a literal colon (C<:>). Only basic authentication is |
278 | separated by a literal colon (C<:>). Only basic authentication is |
270 | currently supported. |
279 | currently supported. |
271 | |
280 | |
272 | =item keepalive = seconds |
281 | =item keepalive = seconds |
273 | |
282 | |
274 | Sets the keepalive probe interval in seconds (default: C<60>). After this |
283 | Sets the keepalive probe interval in seconds (default: C<60>). After this |
275 | many seconds of inactivity the daemon will start to send keepalive probe |
284 | many seconds of inactivity the daemon will start to send keepalive probe |
276 | every 5 seconds until it receives a reply from the other end. If no reply |
285 | every 3 seconds until it receives a reply from the other end. If no reply |
277 | is received within 30 seconds, the peer is considered unreachable and the |
286 | is received within 15 seconds, the peer is considered unreachable and the |
278 | connection is closed. |
287 | connection is closed. |
279 | |
288 | |
280 | =item loglevel = noise|trace|debug|info|notice|warn|error|critical |
289 | =item loglevel = noise|trace|debug|info|notice|warn|error|critical |
281 | |
290 | |
282 | Set the logging level. Connection established messages are logged at level |
291 | Set the logging level. Connection established messages are logged at level |
… | |
… | |
284 | |
293 | |
285 | =item mtu = bytes |
294 | =item mtu = bytes |
286 | |
295 | |
287 | Sets the maximum MTU that should be used on outgoing packets (basically |
296 | Sets the maximum MTU that should be used on outgoing packets (basically |
288 | the MTU of the outgoing interface) The daemon will automatically calculate |
297 | the MTU of the outgoing interface) The daemon will automatically calculate |
289 | maximum overhead (e.g. udp header size, encryption blocksize...) and pass |
298 | maximum overhead (e.g. UDP header size, encryption blocksize...) and pass |
290 | this information to the C<if-up> script. |
299 | this information to the C<if-up> script. |
291 | |
300 | |
292 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
301 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
293 | |
302 | |
294 | This value must be the minimum of the mtu values of all hosts. |
303 | This value must be the minimum of the MTU values of all nodes. |
295 | |
304 | |
296 | =item node = nickname |
305 | =item node = nickname |
297 | |
306 | |
298 | Not really a config setting but introduces a node section. The nickname is |
307 | Not really a config setting but introduces a node section. The nickname is |
299 | used to select the right configuration section and must be passed as an |
308 | used to select the right configuration section and must be passed as an |
300 | argument to the gvpe daemon. |
309 | argument to the gvpe daemon. |
301 | |
310 | |
302 | =item node-up = relative-or-absolute-path |
311 | =item node-up = relative-or-absolute-path |
303 | |
312 | |
304 | Sets a command (default: no script) that should be called whenever a |
313 | Sets a command (default: none) that should be called whenever a connection |
305 | connection is established (even on rekeying operations). In addition to |
314 | is established (even on rekeying operations). Note that node-up/down |
|
|
315 | scripts will be run asynchronously, but execution is serialised, so there |
|
|
316 | will only ever be one such script running. |
|
|
317 | |
306 | all the variables passed to C<if-up> scripts, the following environment |
318 | In addition to all the variables passed to C<if-up> scripts, the following |
307 | variables will be set: |
319 | environment variables will be set: |
308 | |
320 | |
309 | =over 4 |
321 | =over 4 |
310 | |
322 | |
311 | =item DESTNODE=branch2 |
323 | =item DESTNODE=branch2 |
312 | |
324 | |
… | |
… | |
316 | |
328 | |
317 | The node id of the remote node. |
329 | The node id of the remote node. |
318 | |
330 | |
319 | =item DESTIP=188.13.66.8 |
331 | =item DESTIP=188.13.66.8 |
320 | |
332 | |
321 | The numerical IP address of the remote host (gvpe accepts connections from |
333 | The numerical IP address of the remote node (gvpe accepts connections from |
322 | everywhere, as long as the other host can authenticate itself). |
334 | everywhere, as long as the other node can authenticate itself). |
323 | |
335 | |
324 | =item DESTPORT=655 # deprecated |
336 | =item DESTPORT=655 # deprecated |
325 | |
337 | |
326 | The UDP port used by the other side. |
338 | The UDP port used by the other side. |
327 | |
339 | |
… | |
… | |
331 | with STATE=DOWN. |
343 | with STATE=DOWN. |
332 | |
344 | |
333 | =back |
345 | =back |
334 | |
346 | |
335 | Here is a nontrivial example that uses nsupdate to update the name => ip |
347 | Here is a nontrivial example that uses nsupdate to update the name => ip |
336 | mapping in some dns zone: |
348 | mapping in some DNS zone: |
337 | |
349 | |
338 | #!/bin/sh |
350 | #!/bin/sh |
339 | { |
351 | { |
340 | echo update delete $DESTNODE.lowttl.example.net. a |
352 | echo update delete $DESTNODE.lowttl.example.net. a |
341 | echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
353 | echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
… | |
… | |
358 | be doubled. A single C<%s> is replaced by the hostname, so you could |
370 | be doubled. A single C<%s> is replaced by the hostname, so you could |
359 | use paths like C<hostkeys/%s> to fetch the files at the location where |
371 | use paths like C<hostkeys/%s> to fetch the files at the location where |
360 | C<gvpectrl> puts them. |
372 | C<gvpectrl> puts them. |
361 | |
373 | |
362 | Since only the private key file of the current node is used and the |
374 | Since only the private key file of the current node is used and the |
363 | private key file should be kept secret per-host to avoid spoofings, it is |
375 | private key file should be kept secret per-node to avoid spoofing, it is |
364 | not recommended to use this feature. |
376 | not recommended to use this feature. |
365 | |
377 | |
366 | =item rekey = seconds |
378 | =item rekey = seconds |
367 | |
379 | |
368 | Sets the rekeying interval in seconds (default: C<3600>). Connections are |
380 | Sets the rekeying interval in seconds (default: C<3600>). Connections are |
369 | reestablished every C<rekey> seconds. |
381 | reestablished every C<rekey> seconds, making them use a new encryption |
|
|
382 | key. |
370 | |
383 | |
371 | =back |
384 | =back |
372 | |
385 | |
373 | =head2 NODE SPECIFIC SETTINGS |
386 | =head2 NODE SPECIFIC SETTINGS |
374 | |
387 | |
… | |
… | |
383 | |
396 | |
384 | Allow direct connections to this node. See C<deny-direct> for more info. |
397 | Allow direct connections to this node. See C<deny-direct> for more info. |
385 | |
398 | |
386 | =item compress = yes|true|on | no|false|off |
399 | =item compress = yes|true|on | no|false|off |
387 | |
400 | |
388 | Wether to compress data packets sent to this host (default: C<yes>). |
401 | Wether to compress data packets sent to this node (default: C<yes>). |
389 | Compression is really cheap even on slow computers and has no size |
402 | Compression is really cheap even on slow computers and has no size |
390 | overhead at all, so enabling this is a good idea. |
403 | overhead at all, so enabling this is often a good idea. |
391 | |
404 | |
392 | =item connect = ondemand | never | always | disabled |
405 | =item connect = ondemand | never | always | disabled |
393 | |
406 | |
394 | Sets the connect mode (default: C<always>). It can be C<always> (always |
407 | Sets the connect mode (default: C<always>). It can be C<always> (always |
395 | try to establish and keep a connection to the given host), C<never> |
408 | try to establish and keep a connection to the given node), C<never> |
396 | (never initiate a connection to the given host, but accept connections), |
409 | (never initiate a connection to the given host, but accept connections), |
397 | C<ondemand> (try to establish a connection on the first packet sent, and |
410 | C<ondemand> (try to establish a connection when there are outstanding |
398 | take it down after the keepalive interval) or C<disabled> (node is bad, |
411 | packets in the queue and take it down after the keepalive interval) or |
399 | don't talk to it). |
412 | C<disabled> (node is bad, don't talk to it). |
|
|
413 | |
|
|
414 | Routers will automatically be forced to C<always> unless they are |
|
|
415 | C<disabled>, to ensure all nodes can talk to each other. |
400 | |
416 | |
401 | =item deny-direct = nodename | * |
417 | =item deny-direct = nodename | * |
402 | |
418 | |
403 | Deny direct connections to the specified node (or all nodes when C<*> |
419 | Deny direct connections to the specified node (or all nodes when C<*> |
404 | is given). Only one node can be specified, but you can use multiple |
420 | is given). Only one node can be specified, but you can use multiple |
405 | C<allow-direct> and C<deny-direct> statements. This only makes sense in |
421 | C<allow-direct> and C<deny-direct> statements. This only makes sense in |
406 | networks with routers, as routers are required for indirect connections. |
422 | networks with routers, as routers are required for indirect connections. |
407 | |
423 | |
408 | Sometimes, a node cannot reach some other nodes for reasons of network |
424 | Sometimes, a node cannot reach some other nodes for reasons of network |
409 | connectivity. For example, a node behind a firewall that only allows |
425 | connectivity. For example, a node behind a firewall that only allows |
410 | conenctions to/from a single other node in the network. In this case one |
426 | connections to/from a single other node in the network. In this case one |
411 | should specify C<deny-direct = *> and C<allow-direct = othernodename> (the other |
427 | should specify C<deny-direct = *> and C<allow-direct = othernodename> (the other |
412 | node I<must> be a router for this to work). |
428 | node I<must> be a router for this to work). |
413 | |
429 | |
414 | The algorithm to check wether a connection may be direct is as follows: |
430 | The algorithm to check whether a connection may be direct is as follows: |
415 | |
431 | |
416 | 1. Other node mentioned in a C<allow-direct>? If yes, allow the connection. |
432 | 1. Other node mentioned in an C<allow-direct>? If yes, allow the connection. |
417 | |
433 | |
418 | 2. Other node mentioned in a C<deny-direct>? If yes, deny direct connections. |
434 | 2. Other node mentioned in a C<deny-direct>? If yes, deny direct connections. |
419 | |
435 | |
420 | 3. Allow the connection. |
436 | 3. Allow the connection. |
421 | |
437 | |
… | |
… | |
461 | |
477 | |
462 | =item enable-icmp = yes|true|on | no|false|off |
478 | =item enable-icmp = yes|true|on | no|false|off |
463 | |
479 | |
464 | See gvpe.protocol(7) for a description of the ICMP transport protocol. |
480 | See gvpe.protocol(7) for a description of the ICMP transport protocol. |
465 | |
481 | |
466 | Enable the ICMP transport using icmp packets of type C<icmp-type> on this |
482 | Enable the ICMP transport using ICMP packets of type C<icmp-type> on this |
467 | node. |
483 | node. |
468 | |
484 | |
469 | =item enable-rawip = yes|true|on | no|false|off |
485 | =item enable-rawip = yes|true|on | no|false|off |
470 | |
486 | |
471 | See gvpe.protocol(7) for a description of the RAW IP transport protocol. |
487 | See gvpe.protocol(7) for a description of the RAW IP transport protocol. |
… | |
… | |
487 | |
503 | |
488 | Enable the UDPv4 transport using the C<udp-port> port (default: C<no>, |
504 | Enable the UDPv4 transport using the C<udp-port> port (default: C<no>, |
489 | unless no other protocol is enabled for a node, in which case this |
505 | unless no other protocol is enabled for a node, in which case this |
490 | protocol is enabled automatically). |
506 | protocol is enabled automatically). |
491 | |
507 | |
492 | NOTE: Please specify C<enable-udp = yes> if you want t use it even though |
508 | NOTE: Please specify C<enable-udp = yes> if you want to use it even though |
493 | it might get switched on automatically, as some future version might |
509 | it might get switched on automatically, as some future version might |
494 | default to another default protocol. |
510 | default to another default protocol. |
495 | |
511 | |
496 | =item hostname = hostname | ip [can not be defaulted] |
512 | =item hostname = hostname | ip [can not be defaulted] |
497 | |
513 | |
498 | Forces the address of this node to be set to the given dns hostname or ip |
514 | Forces the address of this node to be set to the given DNS hostname or IP |
499 | address. It will be resolved before each connect request, so dyndns should |
515 | address. It will be resolved before each connect request, so dyndns should |
500 | work fine. If this setting is not specified and a router is available, |
516 | work fine. If this setting is not specified and a router is available, |
501 | then the router will be queried for the address of this node. Otherwise, |
517 | then the router will be queried for the address of this node. Otherwise, |
502 | the connection attempt will fail. |
518 | the connection attempt will fail. |
503 | |
519 | |
|
|
520 | Note that DNS resolving is done synchronously, pausing the daemon. If that |
|
|
521 | is an issue you need to specify IP addresses. |
|
|
522 | |
504 | =item icmp-type = integer |
523 | =item icmp-type = integer |
505 | |
524 | |
506 | Sets the type value to be used for outgoing (and incoming) packets sent |
525 | Sets the type value to be used for outgoing (and incoming) packets sent |
507 | via the ICMP transport. |
526 | via the ICMP transport. |
508 | |
527 | |
509 | The default is C<0> (which is C<echo-reply>, also known as |
528 | The default is C<0> (which is C<echo-reply>, also known as |
510 | "ping-replies"). Other useful values include C<8> (C<echo-request>, a.k.a. |
529 | "ping-reply"). Other useful values include C<8> (C<echo-request>, a.k.a. |
511 | "ping") and C<11> (C<time-exceeded>), but any 8-bit value can be used. |
530 | "ping") and C<11> (C<time-exceeded>), but any 8-bit value can be used. |
512 | |
531 | |
513 | =item if-up-data = value |
532 | =item if-up-data = value |
514 | |
533 | |
515 | The value specified using this directive will be passed to the C<if-up> |
534 | The value specified using this directive will be passed to the C<if-up> |
… | |
… | |
524 | |
543 | |
525 | =item max-retry = positive-number |
544 | =item max-retry = positive-number |
526 | |
545 | |
527 | The maximum interval in seconds (default: C<3600>, one hour) between |
546 | The maximum interval in seconds (default: C<3600>, one hour) between |
528 | retries to establish a connection to this node. When a connection cannot |
547 | retries to establish a connection to this node. When a connection cannot |
529 | be established, gvpe uses exponential backoff capped at this value. It's |
548 | be established, gvpe uses exponential back-off capped at this value. It's |
530 | sometimes useful to set this to a much lower value (e.g. C<120>) on |
549 | sometimes useful to set this to a much lower value (e.g. C<120>) on |
531 | connections to routers that usually are stable but sometimes are down, to |
550 | connections to routers that usually are stable but sometimes are down, to |
532 | assure quick reconnections even after longer downtimes. |
551 | assure quick reconnections even after longer downtimes. |
533 | |
552 | |
|
|
553 | =item max-ttl = seconds |
|
|
554 | |
|
|
555 | Expire packets that couldn't be sent after this many seconds |
|
|
556 | (default: C<60>). Gvpe will normally queue packets for a node without an |
|
|
557 | active connection, in the hope of establishing a connection soon. This |
|
|
558 | value specifies the maximum lifetime a packet will stay in the queue, if a |
|
|
559 | packet gets older, it will be thrown away. |
|
|
560 | |
|
|
561 | =item max-queue = positive-number>=1 |
|
|
562 | |
|
|
563 | The maximum number of packets that will be queued (default: C<512>) |
|
|
564 | for this node. If more packets are sent then earlier packets will be |
|
|
565 | expired. See C<max-ttl>, above. |
|
|
566 | |
534 | =item router-priority = 0 | 1 | positive-number>=2 |
567 | =item router-priority = 0 | 1 | positive-number>=2 |
535 | |
568 | |
536 | Sets the router priority of the given host (default: C<0>, disabled). If |
569 | Sets the router priority of the given node (default: C<0>, disabled). |
537 | some host tries to connect to another host without a hostname, it asks |
|
|
538 | the router host for it's IP address. The router host is the one with the |
|
|
539 | highest priority larger than C<1> that is currently reachable. |
|
|
540 | |
570 | |
541 | Make sure all hosts always connect (C<connect = always>) to the router |
571 | If some node tries to connect to another node but it doesn't have a |
542 | hosts, otherwise connecting to them might be impossible. |
572 | hostname, it asks a router node for it's IP address. The router node |
|
|
573 | chosen is the one with the highest priority larger than C<1> that is |
|
|
574 | currently reachable. This is called a I<mediated> connection, as the |
|
|
575 | connection itself will still be direct, but it uses another node to |
|
|
576 | mediate between the two nodes. |
|
|
577 | |
|
|
578 | The value C<0> disables routing, that means if the node receives a packet |
|
|
579 | not for itself it will not forward it but instead drop it. |
543 | |
580 | |
544 | The special value C<1> allows other hosts to route through the router |
581 | The special value C<1> allows other hosts to route through the router |
545 | host, but they will never route through it by default. The value C<0> |
582 | host, but they will never route through it by default (i.e. the config |
546 | disables routing. The idea behind this is that some hosts can, if |
583 | file of another node needs to specify a router priority higher than one |
|
|
584 | to choose such a node for routing). |
|
|
585 | |
|
|
586 | The idea behind this is that some hosts can, if required, bump the |
547 | required, bump the C<router-priority> setting to higher than C<1> in their |
587 | C<router-priority> setting to higher than C<1> in their local config to |
548 | local config to route through specific hosts. If C<router-priority> is |
588 | route through specific hosts. If C<router-priority> is C<0>, then routing |
549 | C<0>, then routing will be refused, so C<1> serves as a "enable, but do |
589 | will be refused, so C<1> serves as a "enable, but do not use by default" |
550 | not use by default" switch. |
590 | switch. |
|
|
591 | |
|
|
592 | Nodes with C<router-priority> set to C<2> or higher will always be forced |
|
|
593 | to C<connect> = C<always> (unless they are C<disabled>). |
551 | |
594 | |
552 | =item tcp-port = port-number |
595 | =item tcp-port = port-number |
553 | |
596 | |
554 | Similar to C<udp-port> (default: C<655>), but sets the TCP port number. |
597 | Similar to C<udp-port> (default: C<655>), but sets the TCP port number. |
555 | |
598 | |
… | |
… | |
564 | |
607 | |
565 | The default (or recommended) directory layout for the config directory is: |
608 | The default (or recommended) directory layout for the config directory is: |
566 | |
609 | |
567 | =over 4 |
610 | =over 4 |
568 | |
611 | |
569 | =item X<gvpe.conf> |
612 | =item gvpe.conf |
570 | |
613 | |
571 | The config file. |
614 | The config file. |
572 | |
615 | |
573 | =item X<if-up> |
616 | =item if-up |
574 | |
617 | |
575 | The if-up script |
618 | The if-up script |
576 | |
619 | |
577 | =item X<node-up>, X<node-down> |
620 | =item node-up, node-down |
578 | |
621 | |
579 | If used the node up or node-down scripts. |
622 | If used the node up or node-down scripts. |
580 | |
623 | |
581 | =item X<hostkey> |
624 | =item hostkey |
582 | |
625 | |
583 | The private key (taken from C<hostkeys/nodename>) of the current host. |
626 | The private key (taken from C<hostkeys/nodename>) of the current host. |
584 | |
627 | |
585 | =item X<pubkey/nodename> |
628 | =item pubkey/nodename |
586 | |
629 | |
587 | The public keys of the other nodes, one file per node. |
630 | The public keys of the other nodes, one file per node. |
588 | |
631 | |
589 | =back |
632 | =back |
590 | |
633 | |