… | |
… | |
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). |
|
|
243 | |
|
|
244 | Many versions of Linux seem to have a bug that causes them to reorder |
|
|
245 | packets for some ip protocols (GRE, ESP) but not for others (AH), so |
|
|
246 | choose wisely (that is, use 51, AH). |
234 | |
247 | |
235 | =item http-proxy-host = hostname/ip |
248 | =item http-proxy-host = hostname/ip |
236 | |
249 | |
237 | The C<http-proxy-*> family of options are only available if gvpe was |
250 | 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 |
251 | 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 |
254 | 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 |
255 | port number of the proxy server. See C<http-proxy-loginpw> if your proxy |
243 | requires authentication. |
256 | requires authentication. |
244 | |
257 | |
245 | Please note that gvpe will still try to resolve all hostnames in the |
258 | 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 |
259 | configuration file, so if you are behind a proxy without access to a DNS |
247 | server better use numerical IP addresses. |
260 | server better use numerical IP addresses. |
248 | |
261 | |
249 | To make best use of this option disable all protocols except tcp in your |
262 | 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 |
263 | 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). |
264 | on a port that the proxy allows (443, https, is a common choice). |
252 | |
265 | |
253 | If you have a router, connecting to it will suffice. Otherwise tcp must be |
266 | If you have a router, connecting to it will suffice. Otherwise TCP must be |
254 | enabled on all hosts. |
267 | enabled on all nodes. |
255 | |
268 | |
256 | Example: |
269 | Example: |
257 | |
270 | |
258 | http-proxy-host = proxy.example.com |
271 | http-proxy-host = proxy.example.com |
259 | http-proxy-port = 3128 # 8080 is another common choice |
272 | http-proxy-port = 3128 # 8080 is another common choice |
… | |
… | |
264 | The port where your proxy server listens. |
277 | The port where your proxy server listens. |
265 | |
278 | |
266 | =item http-proxy-auth = login:password |
279 | =item http-proxy-auth = login:password |
267 | |
280 | |
268 | The optional login and password used to authenticate to the proxy server, |
281 | The optional login and password used to authenticate to the proxy server, |
269 | seperated by a literal colon (C<:>). Only basic authentication is |
282 | separated by a literal colon (C<:>). Only basic authentication is |
270 | currently supported. |
283 | currently supported. |
271 | |
284 | |
272 | =item keepalive = seconds |
285 | =item keepalive = seconds |
273 | |
286 | |
274 | Sets the keepalive probe interval in seconds (default: C<60>). After this |
287 | 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 |
288 | 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 |
289 | 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 |
290 | is received within 15 seconds, the peer is considered unreachable and the |
278 | connection is closed. |
291 | connection is closed. |
279 | |
292 | |
280 | =item loglevel = noise|trace|debug|info|notice|warn|error|critical |
293 | =item loglevel = noise|trace|debug|info|notice|warn|error|critical |
281 | |
294 | |
282 | Set the logging level. Connection established messages are logged at level |
295 | Set the logging level. Connection established messages are logged at level |
… | |
… | |
284 | |
297 | |
285 | =item mtu = bytes |
298 | =item mtu = bytes |
286 | |
299 | |
287 | Sets the maximum MTU that should be used on outgoing packets (basically |
300 | Sets the maximum MTU that should be used on outgoing packets (basically |
288 | the MTU of the outgoing interface) The daemon will automatically calculate |
301 | the MTU of the outgoing interface) The daemon will automatically calculate |
289 | maximum overhead (e.g. udp header size, encryption blocksize...) and pass |
302 | maximum overhead (e.g. UDP header size, encryption blocksize...) and pass |
290 | this information to the C<if-up> script. |
303 | this information to the C<if-up> script. |
291 | |
304 | |
292 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
305 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
293 | |
306 | |
294 | This value must be the minimum of the mtu values of all hosts. |
307 | This value must be the minimum of the MTU values of all nodes. |
295 | |
308 | |
296 | =item node = nickname |
309 | =item node = nickname |
297 | |
310 | |
298 | Not really a config setting but introduces a node section. The nickname is |
311 | 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 |
312 | used to select the right configuration section and must be passed as an |
300 | argument to the gvpe daemon. |
313 | argument to the gvpe daemon. |
301 | |
314 | |
302 | =item node-up = relative-or-absolute-path |
315 | =item node-up = relative-or-absolute-path |
303 | |
316 | |
304 | Sets a command (default: no script) that should be called whenever a |
317 | Sets a command (default: none) that should be called whenever a connection |
305 | connection is established (even on rekeying operations). In addition to |
318 | is established (even on rekeying operations). Note that node-up/down |
|
|
319 | scripts will be run asynchronously, but execution is serialised, so there |
|
|
320 | will only ever be one such script running. |
|
|
321 | |
306 | all the variables passed to C<if-up> scripts, the following environment |
322 | In addition to all the variables passed to C<if-up> scripts, the following |
307 | variables will be set: |
323 | environment variables will be set (values are just examples): |
308 | |
324 | |
309 | =over 4 |
325 | =over 4 |
310 | |
326 | |
311 | =item DESTNODE=branch2 |
327 | =item DESTNODE=branch2 |
312 | |
328 | |
… | |
… | |
314 | |
330 | |
315 | =item DESTID=2 |
331 | =item DESTID=2 |
316 | |
332 | |
317 | The node id of the remote node. |
333 | The node id of the remote node. |
318 | |
334 | |
|
|
335 | =item DESTSI=rawip/88.99.77.55:0 |
|
|
336 | |
|
|
337 | The "socket info" of the target node, protocol dependent but usually in |
|
|
338 | the format protocol/ip:port. |
|
|
339 | |
319 | =item DESTIP=188.13.66.8 |
340 | =item DESTIP=188.13.66.8 |
320 | |
341 | |
321 | The numerical IP address of the remote host (gvpe accepts connections from |
342 | The numerical IP address of the remote node (gvpe accepts connections from |
322 | everywhere, as long as the other host can authenticate itself). |
343 | everywhere, as long as the other node can authenticate itself). |
323 | |
344 | |
324 | =item DESTPORT=655 # deprecated |
345 | =item DESTPORT=655 # deprecated |
325 | |
346 | |
326 | The UDP port used by the other side. |
347 | The protocol port used by the other side, if applicable. |
327 | |
348 | |
328 | =item STATE=UP |
349 | =item STATE=up |
329 | |
350 | |
330 | Node-up scripts get called with STATE=UP, node-down scripts get called |
351 | Node-up scripts get called with STATE=up, node-change scripts get called |
331 | with STATE=DOWN. |
352 | with STATE=change and node-down scripts get called with STATE=down. |
332 | |
353 | |
333 | =back |
354 | =back |
334 | |
355 | |
335 | Here is a nontrivial example that uses nsupdate to update the name => ip |
356 | Here is a nontrivial example that uses nsupdate to update the name => ip |
336 | mapping in some dns zone: |
357 | mapping in some DNS zone: |
337 | |
358 | |
338 | #!/bin/sh |
359 | #!/bin/sh |
339 | { |
360 | { |
340 | echo update delete $DESTNODE.lowttl.example.net. a |
361 | echo update delete $DESTNODE.lowttl.example.net. a |
341 | echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
362 | echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
342 | echo |
363 | echo |
343 | } | nsupdate -d -k $CONFBASE:key.example.net. |
364 | } | nsupdate -d -k $CONFBASE:key.example.net. |
344 | |
365 | |
|
|
366 | =item node-change = relative-or-absolute-path |
|
|
367 | |
|
|
368 | Same as C<node-change>, but gets called whenever something about a |
|
|
369 | connection changes (such as the source IP address). |
|
|
370 | |
345 | =item node-down = relative-or-absolute-path |
371 | =item node-down = relative-or-absolute-path |
346 | |
372 | |
347 | Same as C<node-up>, but gets called whenever a connection is lost. |
373 | Same as C<node-up>, but gets called whenever a connection is lost. |
348 | |
374 | |
349 | =item pid-file = path |
375 | =item pid-file = path |
… | |
… | |
358 | be doubled. A single C<%s> is replaced by the hostname, so you could |
384 | 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 |
385 | use paths like C<hostkeys/%s> to fetch the files at the location where |
360 | C<gvpectrl> puts them. |
386 | C<gvpectrl> puts them. |
361 | |
387 | |
362 | Since only the private key file of the current node is used and the |
388 | 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 |
389 | private key file should be kept secret per-node to avoid spoofing, it is |
364 | not recommended to use this feature. |
390 | not recommended to use this feature. |
365 | |
391 | |
366 | =item rekey = seconds |
392 | =item rekey = seconds |
367 | |
393 | |
368 | Sets the rekeying interval in seconds (default: C<3600>). Connections are |
394 | Sets the rekeying interval in seconds (default: C<3600>). Connections are |
369 | reestablished every C<rekey> seconds. |
395 | reestablished every C<rekey> seconds, making them use a new encryption |
|
|
396 | key. |
|
|
397 | |
|
|
398 | =item nfmark = integer |
|
|
399 | |
|
|
400 | This advanced option, when set to a nonzero value (default: C<0>), tries |
|
|
401 | to set the netfilter mark (or fwmark) value on all sockets gvpe uses to |
|
|
402 | send packets. |
|
|
403 | |
|
|
404 | This can be used to make gvpe use a different set of routing rules. For |
|
|
405 | example, on GNU/Linux, the C<if-up> could set C<nfmark> to 1000 and then |
|
|
406 | put all routing rules into table C<99> and then use an ip rule to make |
|
|
407 | gvpe traffic avoid that routing table, in effect routing normal traffic |
|
|
408 | via gvpe and gvpe traffic via the normal system routing tables: |
|
|
409 | |
|
|
410 | ip rule add not fwmark 1000 lookup 99 |
370 | |
411 | |
371 | =back |
412 | =back |
372 | |
413 | |
373 | =head2 NODE SPECIFIC SETTINGS |
414 | =head2 NODE SPECIFIC SETTINGS |
374 | |
415 | |
375 | The following settings are node-specific, that is, every node can have |
416 | The following settings are node-specific, that is, every node can have |
376 | different settings, even within the same gvpe instance. Settings that are |
417 | different settings, even within the same gvpe instance. Settings that are |
377 | executed before the first node section set the defaults, settings that are |
418 | set before the first node section set the defaults, settings that are |
378 | executed within a node section only apply to the given node. |
419 | set within a node section only apply to the given node. |
379 | |
420 | |
380 | =over 4 |
421 | =over 4 |
381 | |
422 | |
|
|
423 | =item allow-direct = nodename |
|
|
424 | |
|
|
425 | Allow direct connections to this node. See C<deny-direct> for more info. |
|
|
426 | |
382 | =item compress = yes|true|on | no|false|off |
427 | =item compress = yes|true|on | no|false|off |
383 | |
428 | |
384 | Wether to compress data packets sent to this host (default: C<yes>). |
429 | Wether to compress data packets sent to this node (default: C<yes>). |
385 | Compression is really cheap even on slow computers and has no size |
430 | Compression is really cheap even on slow computers and has no size |
386 | overhead at all, so enabling this is a good idea. |
431 | overhead at all, so enabling this is often a good idea. |
387 | |
432 | |
388 | =item connect = ondemand | never | always | disabled |
433 | =item connect = ondemand | never | always | disabled |
389 | |
434 | |
390 | Sets the connect mode (default: C<always>). It can be C<always> (always |
435 | Sets the connect mode (default: C<always>). It can be C<always> (always |
391 | try to establish and keep a connection to the given host), C<never> |
436 | try to establish and keep a connection to the given node), C<never> |
392 | (never initiate a connection to the given host, but accept connections), |
437 | (never initiate a connection to the given host, but accept connections), |
393 | C<ondemand> (try to establish a connection on the first packet sent, and |
438 | C<ondemand> (try to establish a connection when there are outstanding |
394 | take it down after the keepalive interval) or C<disabled> (node is bad, |
439 | packets in the queue and take it down after the keepalive interval) or |
395 | don't talk to it). |
440 | C<disabled> (node is bad, don't talk to it). |
|
|
441 | |
|
|
442 | Routers will automatically be forced to C<always> unless they are |
|
|
443 | C<disabled>, to ensure all nodes can talk to each other. |
|
|
444 | |
|
|
445 | =item deny-direct = nodename | * |
|
|
446 | |
|
|
447 | Deny direct connections to the specified node (or all nodes when C<*> |
|
|
448 | is given). Only one node can be specified, but you can use multiple |
|
|
449 | C<allow-direct> and C<deny-direct> statements. This only makes sense in |
|
|
450 | networks with routers, as routers are required for indirect connections. |
|
|
451 | |
|
|
452 | Sometimes, a node cannot reach some other nodes for reasons of network |
|
|
453 | connectivity. For example, a node behind a firewall that only allows |
|
|
454 | connections to/from a single other node in the network. In this case one |
|
|
455 | should specify C<deny-direct = *> and C<allow-direct = othernodename> (the other |
|
|
456 | node I<must> be a router for this to work). |
|
|
457 | |
|
|
458 | The algorithm to check whether a connection may be direct is as follows: |
|
|
459 | |
|
|
460 | 1. Other node mentioned in an C<allow-direct>? If yes, allow the connection. |
|
|
461 | |
|
|
462 | 2. Other node mentioned in a C<deny-direct>? If yes, deny direct connections. |
|
|
463 | |
|
|
464 | 3. Allow the connection. |
|
|
465 | |
|
|
466 | That is, C<allow-direct> takes precedence over C<deny-direct>. |
|
|
467 | |
|
|
468 | The check is done in both directions, i.e. both nodes must allow a direct |
|
|
469 | connection before one is attempted, so you only need to specify connect |
|
|
470 | limitations on one node. |
396 | |
471 | |
397 | =item dns-domain = domain-suffix |
472 | =item dns-domain = domain-suffix |
398 | |
473 | |
399 | The DNS domain suffix that points to the DNS tunnel server for this node. |
474 | The DNS domain suffix that points to the DNS tunnel server for this node. |
400 | |
475 | |
… | |
… | |
430 | |
505 | |
431 | =item enable-icmp = yes|true|on | no|false|off |
506 | =item enable-icmp = yes|true|on | no|false|off |
432 | |
507 | |
433 | See gvpe.protocol(7) for a description of the ICMP transport protocol. |
508 | See gvpe.protocol(7) for a description of the ICMP transport protocol. |
434 | |
509 | |
435 | Enable the ICMP transport using icmp packets of type C<icmp-type> on this |
510 | Enable the ICMP transport using ICMP packets of type C<icmp-type> on this |
436 | node. |
511 | node. |
437 | |
512 | |
438 | =item enable-rawip = yes|true|on | no|false|off |
513 | =item enable-rawip = yes|true|on | no|false|off |
439 | |
514 | |
440 | See gvpe.protocol(7) for a description of the RAW IP transport protocol. |
515 | See gvpe.protocol(7) for a description of the RAW IP transport protocol. |
… | |
… | |
456 | |
531 | |
457 | Enable the UDPv4 transport using the C<udp-port> port (default: C<no>, |
532 | Enable the UDPv4 transport using the C<udp-port> port (default: C<no>, |
458 | unless no other protocol is enabled for a node, in which case this |
533 | unless no other protocol is enabled for a node, in which case this |
459 | protocol is enabled automatically). |
534 | protocol is enabled automatically). |
460 | |
535 | |
461 | NOTE: Please specify C<enable-udp = yes> if you want t use it even though |
536 | NOTE: Please specify C<enable-udp = yes> if you want to use it even though |
462 | it might get switched on automatically, as some future version might |
537 | it might get switched on automatically, as some future version might |
463 | default to another default protocol. |
538 | default to another default protocol. |
464 | |
539 | |
|
|
540 | =item hostname = hostname | ip [can not be defaulted] |
|
|
541 | |
|
|
542 | Forces the address of this node to be set to the given DNS hostname or IP |
|
|
543 | address. It will be resolved before each connect request, so dyndns should |
|
|
544 | work fine. If this setting is not specified and a router is available, |
|
|
545 | then the router will be queried for the address of this node. Otherwise, |
|
|
546 | the connection attempt will fail. |
|
|
547 | |
|
|
548 | Note that DNS resolving is done synchronously, pausing the daemon. If that |
|
|
549 | is an issue you need to specify IP addresses. |
|
|
550 | |
465 | =item icmp-type = integer |
551 | =item icmp-type = integer |
466 | |
552 | |
467 | Sets the type value to be used for outgoing (and incoming) packets sent |
553 | Sets the type value to be used for outgoing (and incoming) packets sent |
468 | via the ICMP transport. |
554 | via the ICMP transport. |
469 | |
555 | |
470 | The default is C<0> (which is C<echo-reply>, also known as |
556 | The default is C<0> (which is C<echo-reply>, also known as |
471 | "ping-replies"). Other useful values include C<8> (C<echo-request>, a.k.a. |
557 | "ping-reply"). Other useful values include C<8> (C<echo-request>, a.k.a. |
472 | "ping") and C<11> (C<time-exceeded>), but any 8-bit value can be used. |
558 | "ping") and C<11> (C<time-exceeded>), but any 8-bit value can be used. |
473 | |
559 | |
474 | =item if-up-data = value |
560 | =item if-up-data = value |
475 | |
561 | |
476 | The value specified using this directive will be passed to the C<if-up> |
562 | The value specified using this directive will be passed to the C<if-up> |
… | |
… | |
485 | |
571 | |
486 | =item max-retry = positive-number |
572 | =item max-retry = positive-number |
487 | |
573 | |
488 | The maximum interval in seconds (default: C<3600>, one hour) between |
574 | The maximum interval in seconds (default: C<3600>, one hour) between |
489 | retries to establish a connection to this node. When a connection cannot |
575 | retries to establish a connection to this node. When a connection cannot |
490 | be established, gvpe uses exponential backoff capped at this value. It's |
576 | be established, gvpe uses exponential back-off capped at this value. It's |
491 | sometimes useful to set this to a much lower value (e.g. C<120>) on |
577 | sometimes useful to set this to a much lower value (e.g. C<120>) on |
492 | connections to routers that usually are stable but sometimes are down, to |
578 | connections to routers that usually are stable but sometimes are down, to |
493 | assure quick reconnections even after longer downtimes. |
579 | assure quick reconnections even after longer downtimes. |
494 | |
580 | |
|
|
581 | =item max-ttl = seconds |
|
|
582 | |
|
|
583 | Expire packets that couldn't be sent after this many seconds |
|
|
584 | (default: C<60>). Gvpe will normally queue packets for a node without an |
|
|
585 | active connection, in the hope of establishing a connection soon. This |
|
|
586 | value specifies the maximum lifetime a packet will stay in the queue, if a |
|
|
587 | packet gets older, it will be thrown away. |
|
|
588 | |
|
|
589 | =item max-queue = positive-number>=1 |
|
|
590 | |
|
|
591 | The maximum number of packets that will be queued (default: C<512>) |
|
|
592 | for this node. If more packets are sent then earlier packets will be |
|
|
593 | expired. See C<max-ttl>, above. |
|
|
594 | |
495 | =item router-priority = 0 | 1 | positive-number>=2 |
595 | =item router-priority = 0 | 1 | positive-number>=2 |
496 | |
596 | |
497 | Sets the router priority of the given host (default: C<0>, disabled). If |
597 | Sets the router priority of the given node (default: C<0>, disabled). |
498 | some host tries to connect to another host without a hostname, it asks |
|
|
499 | the router host for it's IP address. The router host is the one with the |
|
|
500 | highest priority larger than C<1> that is currently reachable. |
|
|
501 | |
598 | |
502 | Make sure all hosts always connect (C<connect = always>) to the router |
599 | If some node tries to connect to another node but it doesn't have a |
503 | hosts, otherwise connecting to them might be impossible. |
600 | hostname, it asks a router node for it's IP address. The router node |
|
|
601 | chosen is the one with the highest priority larger than C<1> that is |
|
|
602 | currently reachable. This is called a I<mediated> connection, as the |
|
|
603 | connection itself will still be direct, but it uses another node to |
|
|
604 | mediate between the two nodes. |
|
|
605 | |
|
|
606 | The value C<0> disables routing, that means if the node receives a packet |
|
|
607 | not for itself it will not forward it but instead drop it. |
504 | |
608 | |
505 | The special value C<1> allows other hosts to route through the router |
609 | The special value C<1> allows other hosts to route through the router |
506 | host, but they will never route through it by default. The value C<0> |
610 | host, but they will never route through it by default (i.e. the config |
507 | disables routing. The idea behind this is that some hosts can, if |
611 | file of another node needs to specify a router priority higher than one |
|
|
612 | to choose such a node for routing). |
|
|
613 | |
|
|
614 | The idea behind this is that some hosts can, if required, bump the |
508 | required, bump the C<router-priority> setting to higher than C<1> in their |
615 | C<router-priority> setting to higher than C<1> in their local config to |
509 | local config to route through specific hosts. If C<router-priority> is |
616 | route through specific hosts. If C<router-priority> is C<0>, then routing |
510 | C<0>, then routing will be refused, so C<1> serves as a "enable, but do |
617 | will be refused, so C<1> serves as a "enable, but do not use by default" |
511 | not use by default" switch. |
618 | switch. |
|
|
619 | |
|
|
620 | Nodes with C<router-priority> set to C<2> or higher will always be forced |
|
|
621 | to C<connect> = C<always> (unless they are C<disabled>). |
512 | |
622 | |
513 | =item tcp-port = port-number |
623 | =item tcp-port = port-number |
514 | |
624 | |
515 | Similar to C<udp-port> (default: C<655>), but sets the TCP port number. |
625 | Similar to C<udp-port> (default: C<655>), but sets the TCP port number. |
516 | |
626 | |
… | |
… | |
525 | |
635 | |
526 | The default (or recommended) directory layout for the config directory is: |
636 | The default (or recommended) directory layout for the config directory is: |
527 | |
637 | |
528 | =over 4 |
638 | =over 4 |
529 | |
639 | |
530 | =item X<gvpe.conf> |
640 | =item gvpe.conf |
531 | |
641 | |
532 | The config file. |
642 | The config file. |
533 | |
643 | |
534 | =item X<if-up> |
644 | =item if-up |
535 | |
645 | |
536 | The if-up script |
646 | The if-up script |
537 | |
647 | |
538 | =item X<node-up>, X<node-down> |
648 | =item node-up, node-down |
539 | |
649 | |
540 | If used the node up or node-down scripts. |
650 | If used the node up or node-down scripts. |
541 | |
651 | |
542 | =item X<hostkey> |
652 | =item hostkey |
543 | |
653 | |
544 | The private key (taken from C<hostkeys/nodename>) of the current host. |
654 | The private key (taken from C<hostkeys/nodename>) of the current host. |
545 | |
655 | |
546 | =item X<pubkey/nodename> |
656 | =item pubkey/nodename |
547 | |
657 | |
548 | The public keys of the other nodes, one file per node. |
658 | The public keys of the other nodes, one file per node. |
549 | |
659 | |
550 | =back |
660 | =back |
551 | |
661 | |