1 | .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 |
1 | .\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.20) |
2 | .\" |
2 | .\" |
3 | .\" Standard preamble: |
3 | .\" Standard preamble: |
4 | .\" ======================================================================== |
4 | .\" ======================================================================== |
5 | .de Sh \" Subsection heading |
|
|
6 | .br |
|
|
7 | .if t .Sp |
|
|
8 | .ne 5 |
|
|
9 | .PP |
|
|
10 | \fB\\$1\fR |
|
|
11 | .PP |
|
|
12 | .. |
|
|
13 | .de Sp \" Vertical space (when we can't use .PP) |
5 | .de Sp \" Vertical space (when we can't use .PP) |
14 | .if t .sp .5v |
6 | .if t .sp .5v |
15 | .if n .sp |
7 | .if n .sp |
16 | .. |
8 | .. |
17 | .de Vb \" Begin verbatim text |
9 | .de Vb \" Begin verbatim text |
… | |
… | |
23 | .ft R |
15 | .ft R |
24 | .fi |
16 | .fi |
25 | .. |
17 | .. |
26 | .\" Set up some character translations and predefined strings. \*(-- will |
18 | .\" Set up some character translations and predefined strings. \*(-- will |
27 | .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left |
19 | .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left |
28 | .\" double quote, and \*(R" will give a right double quote. | will give a |
20 | .\" double quote, and \*(R" will give a right double quote. \*(C+ will |
29 | .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to |
21 | .\" give a nicer C++. Capital omega is used to do unbreakable dashes and |
30 | .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C' |
22 | .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, |
31 | .\" expand to `' in nroff, nothing in troff, for use with C<>. |
23 | .\" nothing in troff, for use with C<>. |
32 | .tr \(*W-|\(bv\*(Tr |
24 | .tr \(*W- |
33 | .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' |
25 | .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' |
34 | .ie n \{\ |
26 | .ie n \{\ |
35 | . ds -- \(*W- |
27 | . ds -- \(*W- |
36 | . ds PI pi |
28 | . ds PI pi |
37 | . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch |
29 | . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch |
… | |
… | |
46 | . ds PI \(*p |
38 | . ds PI \(*p |
47 | . ds L" `` |
39 | . ds L" `` |
48 | . ds R" '' |
40 | . ds R" '' |
49 | 'br\} |
41 | 'br\} |
50 | .\" |
42 | .\" |
|
|
43 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
|
|
44 | .ie \n(.g .ds Aq \(aq |
|
|
45 | .el .ds Aq ' |
|
|
46 | .\" |
51 | .\" If the F register is turned on, we'll generate index entries on stderr for |
47 | .\" If the F register is turned on, we'll generate index entries on stderr for |
52 | .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index |
48 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
53 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
49 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
54 | .\" output yourself in some meaningful fashion. |
50 | .\" output yourself in some meaningful fashion. |
55 | .if \nF \{\ |
51 | .ie \nF \{\ |
56 | . de IX |
52 | . de IX |
57 | . tm Index:\\$1\t\\n%\t"\\$2" |
53 | . tm Index:\\$1\t\\n%\t"\\$2" |
58 | .. |
54 | .. |
59 | . nr % 0 |
55 | . nr % 0 |
60 | . rr F |
56 | . rr F |
61 | .\} |
57 | .\} |
62 | .\" |
58 | .el \{\ |
63 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
59 | . de IX |
64 | .\" way too many mistakes in technical documents. |
60 | .. |
65 | .hy 0 |
61 | .\} |
66 | .if n .na |
|
|
67 | .\" |
62 | .\" |
68 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
63 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
69 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
64 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
70 | . \" fudge factors for nroff and troff |
65 | . \" fudge factors for nroff and troff |
71 | .if n \{\ |
66 | .if n \{\ |
… | |
… | |
127 | .\} |
122 | .\} |
128 | .rm #[ #] #H #V #F C |
123 | .rm #[ #] #H #V #F C |
129 | .\" ======================================================================== |
124 | .\" ======================================================================== |
130 | .\" |
125 | .\" |
131 | .IX Title "GVPE.CONF 5" |
126 | .IX Title "GVPE.CONF 5" |
132 | .TH GVPE.CONF 5 "2004-12-04" "1.7" "GNU Virtual Private Ethernet" |
127 | .TH GVPE.CONF 5 "2013-10-11" "2.25" "GNU Virtual Private Ethernet" |
|
|
128 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
|
|
129 | .\" way too many mistakes in technical documents. |
|
|
130 | .if n .ad l |
|
|
131 | .nh |
133 | .SH "NAME" |
132 | .SH "NAME" |
134 | gvpe.conf \- configuration file for the GNU VPE daemon |
133 | gvpe.conf \- configuration file for the GNU VPE daemon |
135 | .SH "SYNOPSIS" |
134 | .SH "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
135 | .IX Header "SYNOPSIS" |
137 | .Vb 4 |
136 | .Vb 4 |
138 | \& enable-udp = yes |
137 | \& # global options for all nodes |
139 | \& udp-port = 407 |
138 | \& udp\-port = 407 |
140 | \& mtu = 1492 |
139 | \& mtu = 1492 |
141 | \& ifname = vpn0 |
140 | \& ifname = vpn0 |
142 | .Ve |
141 | \& |
143 | .PP |
142 | \& # first node is named branch1 and is at 1.2.3.4 |
144 | .Vb 2 |
|
|
145 | \& node = branch1 |
143 | \& node = branch1 |
146 | \& hostname = 1.2.3.4 |
144 | \& hostname = 1.2.3.4 |
147 | .Ve |
145 | \& |
148 | .PP |
146 | \& # second node uses dns to resolve the address |
149 | .Vb 3 |
|
|
150 | \& node = branch2 |
147 | \& node = branch2 |
151 | \& hostname = www.example.net |
148 | \& hostname = www.example.net |
152 | \& udp-port = 500 # this host uses a different udp-port |
149 | \& udp\-port = 500 # this host uses a different udp\-port |
153 | .Ve |
150 | \& |
154 | .PP |
151 | \& # third node has no fixed ip address |
155 | .Vb 2 |
|
|
156 | \& node = branch3 |
152 | \& node = branch3 |
157 | \& connect = ondemand |
153 | \& connect = ondemand |
158 | .Ve |
154 | .Ve |
159 | .SH "DESCRIPTION" |
155 | .SH "DESCRIPTION" |
160 | .IX Header "DESCRIPTION" |
156 | .IX Header "DESCRIPTION" |
161 | The gvpe config file consists of a series of lines that contain \f(CW\*(C`variable |
157 | The gvpe config file consists of a series of lines that contain \f(CW\*(C`variable |
162 | = value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and |
158 | = value\*(C'\fR pairs. Empty lines are ignored. Comments start with a \f(CW\*(C`#\*(C'\fR and |
163 | extend to the end of the line. They can be used on their own lines, or |
159 | extend to the end of the line. They can be used on their own lines, or |
164 | after any directives. Spaces are allowed before or after the \f(CW\*(C`=\*(C'\fR sign or |
160 | after any directives. Whitespace is allowed around the \f(CW\*(C`=\*(C'\fR sign or after |
165 | after values, but not within the variable names or values themselves. |
161 | values, but not within the variable names or values themselves. |
166 | .PP |
162 | .PP |
167 | The only exception to the above is the \*(L"on\*(R" directive that can prefix any |
163 | All settings are applied \*(L"in order\*(R", that is, later settings of the same |
168 | \&\f(CW\*(C`name = value\*(C'\fR setting and will only \*(L"execute\*(R" it on the named node, or |
164 | variable overwrite earlier ones. |
169 | (if the nodename starts with \*(L"!\*(R") on all nodes except the named one. |
|
|
170 | .PP |
165 | .PP |
|
|
166 | The only exceptions to the above are the following directives: |
|
|
167 | .IP "node nodename" 4 |
|
|
168 | .IX Item "node nodename" |
|
|
169 | Introduces a node section. The nodename is used to select the right |
|
|
170 | configuration section and is the same string as is passed as an argument |
|
|
171 | to the gvpe daemon. |
|
|
172 | .Sp |
|
|
173 | Multiple \f(CW\*(C`node\*(C'\fR statements with the same node name are supported and will |
|
|
174 | be merged together. |
|
|
175 | .IP "global" 4 |
|
|
176 | .IX Item "global" |
|
|
177 | This statement switches back to the global section, which is mainly |
|
|
178 | useful if you want to include a second config file, e..g for local |
|
|
179 | customisations. To do that, simply include this at the very end of your |
|
|
180 | config file: |
|
|
181 | .Sp |
|
|
182 | .Vb 2 |
|
|
183 | \& global |
|
|
184 | \& include local.conf |
|
|
185 | .Ve |
|
|
186 | .IP "on nodename ..." 4 |
|
|
187 | .IX Item "on nodename ..." |
|
|
188 | .PD 0 |
|
|
189 | .IP "on !nodename ..." 4 |
|
|
190 | .IX Item "on !nodename ..." |
|
|
191 | .PD |
|
|
192 | You can prefix any configuration directive with \f(CW\*(C`on\*(C'\fR and a nodename. \s-1GVPE\s0 |
|
|
193 | will will only \*(L"execute\*(R" it on the named node, or (if the nodename starts |
|
|
194 | with \f(CW\*(C`!\*(C'\fR) on all nodes except the named one. |
|
|
195 | .Sp |
|
|
196 | Example: set the \s-1MTU\s0 to \f(CW1450\fR everywhere, \f(CW\*(C`loglevel\*(C'\fR to \f(CW\*(C`noise\*(C'\fR on |
|
|
197 | \&\f(CW\*(C`branch1\*(C'\fR, and \f(CW\*(C`connect\*(C'\fR to \f(CW\*(C`ondemand\*(C'\fR everywhere but on branch2. |
|
|
198 | .Sp |
171 | .Vb 3 |
199 | .Vb 3 |
172 | \& name = value |
200 | \& mtu = 1450 |
173 | \& on branch1 loglevel = noise |
201 | \& on branch1 loglevel = noise |
174 | \& on !branch2 connect = ondemand |
202 | \& on !branch2 connect = ondemand |
175 | .Ve |
203 | .Ve |
176 | .PP |
204 | .IP "include relative-or-absolute-path" 4 |
177 | All settings are executed \*(L"in order\*(R", that is, later settings of the same |
205 | .IX Item "include relative-or-absolute-path" |
178 | variable overwrite earlier ones. |
206 | Reads the specified file (the path must not contain whitespace or \f(CW\*(C`=\*(C'\fR |
|
|
207 | characters) and evaluate all config directives in it as if they were |
|
|
208 | spelled out in place of the \f(CW\*(C`include\*(C'\fR directive. |
|
|
209 | .Sp |
|
|
210 | The path is a printf format string, that is, you must escape any \f(CW\*(C`%\*(C'\fR |
|
|
211 | by doubling it, and you can have a single \f(CW%s\fR inside, which will be |
|
|
212 | replaced by the current nodename. |
|
|
213 | .Sp |
|
|
214 | Relative paths are interpreted relative to the \s-1GVPE\s0 config directory. |
|
|
215 | .Sp |
|
|
216 | Example: include the file \fIlocal.conf\fR in the config directory on every |
|
|
217 | node. |
|
|
218 | .Sp |
|
|
219 | .Vb 1 |
|
|
220 | \& include local.conf |
|
|
221 | .Ve |
|
|
222 | .Sp |
|
|
223 | Example: include a file \fIconf/\fRnodename\fI.conf\fR |
|
|
224 | .Sp |
|
|
225 | .Vb 1 |
|
|
226 | \& include conf/%s.conf |
|
|
227 | .Ve |
179 | .SH "ANATOMY OF A CONFIG FILE" |
228 | .SH "ANATOMY OF A CONFIG FILE" |
180 | .IX Header "ANATOMY OF A CONFIG FILE" |
229 | .IX Header "ANATOMY OF A CONFIG FILE" |
181 | Usually, a config file starts with global settings (like the udp port to |
230 | Usually, a config file starts with a few global settings (like the \s-1UDP\s0 |
182 | listen on), followed by node-specific sections that begin with a \f(CW\*(C`node = |
231 | port to listen on), followed by node-specific sections that begin with a |
183 | nickname\*(C'\fR line. |
232 | \&\f(CW\*(C`node = nickname\*(C'\fR line. |
184 | .PP |
233 | .PP |
185 | Every node that is part of the network must have a section that starts |
234 | Every node that is part of the network must have a section that starts |
186 | with \f(CW\*(C`node = nickname\*(C'\fR. The number and order of the nodes is important |
235 | with \f(CW\*(C`node = nickname\*(C'\fR. The number and order of the nodes is important |
187 | and must be the same on all hosts. It is not uncommon for node sections to |
236 | and must be the same on all nodes. It is not uncommon for node sections to |
188 | be completely empty \- if the default values are right. |
237 | be completely empty \- if the default values are right. |
189 | .PP |
238 | .PP |
190 | Node-specific settings can be used at any time. If used before the first |
239 | Node-specific settings can be used at any time. If used before the first |
191 | node section they will set the default values for all following nodes. |
240 | node section they will set the default values for all following nodes. |
192 | .SH "CONFIG VARIABLES" |
241 | .SH "CONFIG VARIABLES" |
193 | .IX Header "CONFIG VARIABLES" |
242 | .IX Header "CONFIG VARIABLES" |
194 | .Sh "\s-1GLOBAL\s0 \s-1SETTINGS\s0" |
243 | .SS "\s-1GLOBAL\s0 \s-1SETTINGS\s0" |
195 | .IX Subsection "GLOBAL SETTINGS" |
244 | .IX Subsection "GLOBAL SETTINGS" |
196 | Global settings will affect the behaviour of the running gvpe daemon, that |
245 | Global settings will affect the behaviour of the running gvpe daemon, that |
197 | is, they are in some sense node-specific (config files can set different |
246 | is, they are in some sense node-specific (config files can set different |
198 | values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of |
247 | values on different nodes using \f(CW\*(C`on\*(C'\fR), but will affect the behaviour of |
199 | the gvpe daemon and all connections it creates. |
248 | the gvpe daemon and all connections it creates. |
200 | .IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4 |
249 | .IP "chroot = path or /" 4 |
201 | .IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical" |
250 | .IX Item "chroot = path or /" |
202 | Set the logging level. Connection established messages are logged at level |
251 | Tells \s-1GVPE\s0 to \fIchroot\fR\|(2) to the specified path after reading all necessary |
203 | \&\f(CW\*(C`info\*(C'\fR, notable errors are logged with \f(CW\*(C`error\*(C'\fR. Default is \f(CW\*(C`info\*(C'\fR. |
252 | files, binding to sockets and running the \f(CW\*(C`if\-up\*(C'\fR script, but before |
204 | .IP "node = nickname" 4 |
253 | running \f(CW\*(C`node\-up\*(C'\fR or any other scripts. |
205 | .IX Item "node = nickname" |
|
|
206 | Not really a config setting but introduces a node section. The nickname is |
|
|
207 | used to select the right configuration section and must be passed as an |
|
|
208 | argument to the gvpe daemon. |
|
|
209 | .IP "private-key = relative-path-to-key" 4 |
|
|
210 | .IX Item "private-key = relative-path-to-key" |
|
|
211 | Sets the path (relative to the config directory) to the private key |
|
|
212 | (default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must |
|
|
213 | be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could |
|
|
214 | use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where |
|
|
215 | \&\f(CW\*(C`gvpectrl\*(C'\fR puts them. |
|
|
216 | .Sp |
254 | .Sp |
217 | Since only the private key file of the current node is used and the |
255 | The special path \fI/\fR instructs \s-1GVPE\s0 to create (and remove) an empty |
218 | private key file should be kept secret per-host to avoid spoofings, it is |
256 | temporary directory to use as new root. This is most secure, but makes it |
219 | not recommended to use this feature. |
257 | impossible to use any scripts other than the \f(CW\*(C`if\-up\*(C'\fR one. |
|
|
258 | .IP "chuid = numerical-uid" 4 |
|
|
259 | .IX Item "chuid = numerical-uid" |
|
|
260 | .PD 0 |
|
|
261 | .IP "chgid = numerical-gid" 4 |
|
|
262 | .IX Item "chgid = numerical-gid" |
|
|
263 | .PD |
|
|
264 | These two options tell \s-1GVPE\s0 to change to the given user and/or group id |
|
|
265 | after reading all necessary files, binding to sockets and running the |
|
|
266 | \&\f(CW\*(C`if\-up\*(C'\fR script. |
|
|
267 | .Sp |
|
|
268 | Other scripts, such as \f(CW\*(C`node\-up\*(C'\fR, are run with the new user id or group id. |
|
|
269 | .IP "chuser = username" 4 |
|
|
270 | .IX Item "chuser = username" |
|
|
271 | Alternative to \f(CW\*(C`chuid\*(C'\fR and \f(CW\*(C`chgid\*(C'\fR: Sets both \f(CW\*(C`chuid\*(C'\fR and \f(CW\*(C`chgid\*(C'\fR |
|
|
272 | to the user and (primary) group ids of the specified user (for example, |
|
|
273 | \&\f(CW\*(C`nobody\*(C'\fR). |
|
|
274 | .IP "dns-forw-host = hostname/ip" 4 |
|
|
275 | .IX Item "dns-forw-host = hostname/ip" |
|
|
276 | The \s-1DNS\s0 server to forward \s-1DNS\s0 requests to for the \s-1DNS\s0 tunnel protocol |
|
|
277 | (default: \f(CW127.0.0.1\fR, changing it is highly recommended). |
|
|
278 | .IP "dns-forw-port = port-number" 4 |
|
|
279 | .IX Item "dns-forw-port = port-number" |
|
|
280 | The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR, |
|
|
281 | which is fine in most cases). |
|
|
282 | .IP "dns-case-preserving = yes|true|on | no|false|off" 4 |
|
|
283 | .IX Item "dns-case-preserving = yes|true|on | no|false|off" |
|
|
284 | Sets whether the \s-1DNS\s0 transport forwarding server preserves case (\s-1DNS\s0 |
|
|
285 | servers have to, but some access systems are even more broken than others) |
|
|
286 | (default: true). |
|
|
287 | .Sp |
|
|
288 | Normally, when the forwarding server changes the case of domain names then |
|
|
289 | \&\s-1GVPE\s0 will automatically set this to false. |
|
|
290 | .IP "dns-max-outstanding = integer-number-of-requests" 4 |
|
|
291 | .IX Item "dns-max-outstanding = integer-number-of-requests" |
|
|
292 | The maximum number of outstanding \s-1DNS\s0 transport requests |
|
|
293 | (default: \f(CW100\fR). \s-1GVPE\s0 will never issue more requests then the given |
|
|
294 | limit without receiving replies. In heavily overloaded situations it might |
|
|
295 | help to set this to a low number (e.g. \f(CW3\fR or even \f(CW1\fR) to limit the |
|
|
296 | number of parallel requests. |
|
|
297 | .Sp |
|
|
298 | The default should be working \s-1OK\s0 for most links. |
|
|
299 | .IP "dns-overlap-factor = float" 4 |
|
|
300 | .IX Item "dns-overlap-factor = float" |
|
|
301 | The \s-1DNS\s0 transport uses the minimum request latency (\fBmin_latency\fR) seen |
|
|
302 | during a connection as it's timing base. This factor (default: \f(CW0.5\fR, |
|
|
303 | must be > 0) is multiplied by \fBmin_latency\fR to get the maximum sending |
|
|
304 | rate (= minimum send interval), i.e. a factor of \f(CW1\fR means that a new |
|
|
305 | request might be generated every \fBmin_latency\fR seconds, which means on |
|
|
306 | average there should only ever be one outstanding request. A factor of |
|
|
307 | \&\f(CW0.5\fR means that \s-1GVPE\s0 will send requests twice as often as the minimum |
|
|
308 | latency measured. |
|
|
309 | .Sp |
|
|
310 | For congested or picky \s-1DNS\s0 forwarders you could use a value nearer to or |
|
|
311 | exceeding \f(CW1\fR. |
|
|
312 | .Sp |
|
|
313 | The default should be working \s-1OK\s0 for most links. |
|
|
314 | .IP "dns-send-interval = send-interval-in-seconds" 4 |
|
|
315 | .IX Item "dns-send-interval = send-interval-in-seconds" |
|
|
316 | The minimum send interval (= maximum rate) that the \s-1DNS\s0 transport will |
|
|
317 | use to send new \s-1DNS\s0 requests. \s-1GVPE\s0 will not exceed this rate even when |
|
|
318 | the latency is very low. The default is \f(CW0.01\fR, which means \s-1GVPE\s0 will |
|
|
319 | not send more than 100 \s-1DNS\s0 requests per connection per second. For |
|
|
320 | high-bandwidth links you could go lower, e.g. to \f(CW0.001\fR or so. For |
|
|
321 | congested or rate-limited links, you might want to go higher, say \f(CW0.1\fR, |
|
|
322 | \&\f(CW0.2\fR or even higher. |
|
|
323 | .Sp |
|
|
324 | The default should be working \s-1OK\s0 for most links. |
|
|
325 | .IP "dns-timeout-factor = float" 4 |
|
|
326 | .IX Item "dns-timeout-factor = float" |
|
|
327 | Factor to multiply the \f(CW\*(C`min_latency\*(C'\fR (see \f(CW\*(C`dns\-overlap\-factor\*(C'\fR) by to |
|
|
328 | get request timeouts. The default of \f(CW8\fR means that the \s-1DNS\s0 transport |
|
|
329 | will resend the request when no reply has been received for longer than |
|
|
330 | eight times the minimum (= expected) latency, assuming the request or |
|
|
331 | reply has been lost. |
|
|
332 | .Sp |
|
|
333 | For congested links a higher value might be necessary (e.g. \f(CW30\fR). If |
|
|
334 | the link is very stable lower values (e.g. \f(CW2\fR) might work |
|
|
335 | nicely. Values near or below \f(CW1\fR makes no sense whatsoever. |
|
|
336 | .Sp |
|
|
337 | The default should be working \s-1OK\s0 for most links but will result in low |
|
|
338 | throughput if packet loss is high. |
|
|
339 | .IP "if-up = relative-or-absolute-path" 4 |
|
|
340 | .IX Item "if-up = relative-or-absolute-path" |
|
|
341 | Sets the path of a script that should be called immediately after the |
|
|
342 | network interface is initialized (but not necessarily up). The following |
|
|
343 | environment variables are passed to it (the values are just examples). |
|
|
344 | .Sp |
|
|
345 | Variables that have the same value on all nodes: |
|
|
346 | .RS 4 |
|
|
347 | .IP "CONFBASE=/etc/gvpe" 4 |
|
|
348 | .IX Item "CONFBASE=/etc/gvpe" |
|
|
349 | The configuration base directory. |
|
|
350 | .IP "IFNAME=vpn0" 4 |
|
|
351 | .IX Item "IFNAME=vpn0" |
|
|
352 | The network interface to initialize. |
|
|
353 | .IP "IFTYPE=native # or tincd" 4 |
|
|
354 | .IX Item "IFTYPE=native # or tincd" |
|
|
355 | .PD 0 |
|
|
356 | .IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4 |
|
|
357 | .IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.." |
|
|
358 | .PD |
|
|
359 | The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the |
|
|
360 | \&\s-1OS\s0 name in lowercase) that this \s-1GVPE\s0 was configured for. Can be used to |
|
|
361 | select the correct syntax to use for network-related commands. |
|
|
362 | .IP "MTU=1436" 4 |
|
|
363 | .IX Item "MTU=1436" |
|
|
364 | The \s-1MTU\s0 to set the interface to. You can use lower values (if done |
|
|
365 | consistently on all nodes), but this is usually either inefficient or |
|
|
366 | simply ineffective. |
|
|
367 | .IP "NODES=5" 4 |
|
|
368 | .IX Item "NODES=5" |
|
|
369 | The number of nodes in this \s-1GVPE\s0 network. |
|
|
370 | .RE |
|
|
371 | .RS 4 |
|
|
372 | .Sp |
|
|
373 | Variables that are node-specific and with values pertaining to the node |
|
|
374 | running this \s-1GVPE:\s0 |
|
|
375 | .IP "IFUPDATA=string" 4 |
|
|
376 | .IX Item "IFUPDATA=string" |
|
|
377 | The value of the configuration directive \f(CW\*(C`if\-up\-data\*(C'\fR. |
|
|
378 | .IP "MAC=fe:fd:80:00:00:01" 4 |
|
|
379 | .IX Item "MAC=fe:fd:80:00:00:01" |
|
|
380 | The \s-1MAC\s0 address the network interface has to use. |
|
|
381 | .Sp |
|
|
382 | Might be used to initialize interfaces on platforms where \s-1GVPE\s0 does not |
|
|
383 | do this automatically. Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR man page for |
|
|
384 | platform-specific information. |
|
|
385 | .IP "NODENAME=branch1" 4 |
|
|
386 | .IX Item "NODENAME=branch1" |
|
|
387 | The nickname of the node. |
|
|
388 | .IP "NODEID=1" 4 |
|
|
389 | .IX Item "NODEID=1" |
|
|
390 | The numerical node \s-1ID\s0 of the node running this instance of \s-1GVPE\s0. The first |
|
|
391 | node mentioned in the config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on. |
|
|
392 | .RE |
|
|
393 | .RS 4 |
|
|
394 | .Sp |
|
|
395 | In addition, all node-specific variables (except \f(CW\*(C`NODEID\*(C'\fR) will be |
|
|
396 | available with a postfix of \f(CW\*(C`_nodeid\*(C'\fR, which contains the value for that |
|
|
397 | node, e.g. the \f(CW\*(C`MAC_1\*(C'\fR variable contains the \s-1MAC\s0 address of node #1, while |
|
|
398 | the \f(CW\*(C`NODENAME_22\*(C'\fR variable contains the name of node #22. |
|
|
399 | .Sp |
|
|
400 | Here is a simple if-up script: |
|
|
401 | .Sp |
|
|
402 | .Vb 5 |
|
|
403 | \& #!/bin/sh |
|
|
404 | \& ip link set $IFNAME up |
|
|
405 | \& [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME |
|
|
406 | \& [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME |
|
|
407 | \& ip route add 10.0.0.0/8 dev $IFNAME |
|
|
408 | .Ve |
|
|
409 | .Sp |
|
|
410 | More complicated examples (using routing to reduce \s-1ARP\s0 traffic) can be |
|
|
411 | found in the \fIetc/\fR subdirectory of the distribution. |
|
|
412 | .RE |
|
|
413 | .IP "ifname = devname" 4 |
|
|
414 | .IX Item "ifname = devname" |
|
|
415 | Sets the tun interface name to the given name. The default is OS-specific |
|
|
416 | and most probably something like \f(CW\*(C`tun0\*(C'\fR. |
220 | .IP "ifpersist = yes|true|on | no|false|off" 4 |
417 | .IP "ifpersist = yes|true|on | no|false|off" 4 |
221 | .IX Item "ifpersist = yes|true|on | no|false|off" |
418 | .IX Item "ifpersist = yes|true|on | no|false|off" |
222 | Should the tun/tap device be made persistent, that is, should the device |
419 | Should the tun/tap device be made persistent, that is, should the device |
223 | stay up even when gvpe exits? Some versions of the tunnel device have |
420 | stay up even when gvpe exits? Some versions of the tunnel device have |
224 | problems sending packets when gvpe is restarted in persistent mode, so |
421 | problems sending packets when gvpe is restarted in persistent mode, so |
225 | if the connections can be established but you cannot send packets from |
422 | if the connections can be established but you cannot send packets from |
226 | the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the |
423 | the local node, try to set this to \f(CW\*(C`off\*(C'\fR and do an ifconfig down on the |
227 | device. |
424 | device. |
228 | .IP "ifname = devname" 4 |
425 | .IP "ip-proto = numerical-ip-protocol" 4 |
229 | .IX Item "ifname = devname" |
426 | .IX Item "ip-proto = numerical-ip-protocol" |
230 | Sets the tun interface name to the given name. The default is OS-specific |
427 | Sets the protocol number to be used for the rawip protocol. This is a |
231 | and most probably something like \f(CW\*(C`tun0\*(C'\fR. |
428 | global option because all nodes must use the same protocol, and since |
232 | .IP "rekey = seconds" 4 |
429 | there are no port numbers, you cannot easily run more than one gvpe |
233 | .IX Item "rekey = seconds" |
430 | instance using the same protocol, nor can you share the protocol with |
234 | Sets the rekeying interval in seconds (default: \f(CW3600\fR). Connections are |
431 | other programs. |
235 | reestablished every \f(CW\*(C`rekey\*(C'\fR seconds. |
432 | .Sp |
|
|
433 | The default is 47 (\s-1GRE\s0), which has a good chance of tunneling |
|
|
434 | through firewalls (but note that gvpe's rawip protocol is not \s-1GRE\s0 |
|
|
435 | compatible). Other common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 |
|
|
436 | (\s-1IPIP\s0 tunnels) or 98 (\s-1ENCAP\s0, rfc1241). |
|
|
437 | .Sp |
|
|
438 | Many versions of Linux seem to have a bug that causes them to reorder |
|
|
439 | packets for some ip protocols (\s-1GRE\s0, \s-1ESP\s0) but not for others (\s-1AH\s0), so |
|
|
440 | choose wisely (that is, use 51, \s-1AH\s0). |
|
|
441 | .IP "http-proxy-host = hostname/ip" 4 |
|
|
442 | .IX Item "http-proxy-host = hostname/ip" |
|
|
443 | The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was |
|
|
444 | compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of |
|
|
445 | tcp connections through a http proxy server. |
|
|
446 | .Sp |
|
|
447 | \&\f(CW\*(C`http\-proxy\-host\*(C'\fR and \f(CW\*(C`http\-proxy\-port\*(C'\fR should specify the hostname and |
|
|
448 | port number of the proxy server. See \f(CW\*(C`http\-proxy\-loginpw\*(C'\fR if your proxy |
|
|
449 | requires authentication. |
|
|
450 | .Sp |
|
|
451 | Please note that gvpe will still try to resolve all hostnames in the |
|
|
452 | configuration file, so if you are behind a proxy without access to a \s-1DNS\s0 |
|
|
453 | server better use numerical \s-1IP\s0 addresses. |
|
|
454 | .Sp |
|
|
455 | To make best use of this option disable all protocols except \s-1TCP\s0 in your |
|
|
456 | config file and make sure your routers (or all other nodes) are listening |
|
|
457 | on a port that the proxy allows (443, https, is a common choice). |
|
|
458 | .Sp |
|
|
459 | If you have a router, connecting to it will suffice. Otherwise \s-1TCP\s0 must be |
|
|
460 | enabled on all nodes. |
|
|
461 | .Sp |
|
|
462 | Example: |
|
|
463 | .Sp |
|
|
464 | .Vb 3 |
|
|
465 | \& http\-proxy\-host = proxy.example.com |
|
|
466 | \& http\-proxy\-port = 3128 # 8080 is another common choice |
|
|
467 | \& http\-proxy\-auth = schmorp:grumbeere |
|
|
468 | .Ve |
|
|
469 | .IP "http-proxy-port = proxy-tcp-port" 4 |
|
|
470 | .IX Item "http-proxy-port = proxy-tcp-port" |
|
|
471 | The port where your proxy server listens. |
|
|
472 | .IP "http-proxy-auth = login:password" 4 |
|
|
473 | .IX Item "http-proxy-auth = login:password" |
|
|
474 | The optional login and password used to authenticate to the proxy server, |
|
|
475 | separated by a literal colon (\f(CW\*(C`:\*(C'\fR). Only basic authentication is |
|
|
476 | currently supported. |
236 | .IP "keepalive = seconds" 4 |
477 | .IP "keepalive = seconds" 4 |
237 | .IX Item "keepalive = seconds" |
478 | .IX Item "keepalive = seconds" |
238 | Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this |
479 | Sets the keepalive probe interval in seconds (default: \f(CW60\fR). After this |
239 | many seconds of inactivity the daemon will start to send keepalive probe |
480 | many seconds of inactivity the daemon will start to send keepalive probe |
240 | every 5 seconds until it receives a reply from the other end. If no reply |
481 | every 3 seconds until it receives a reply from the other end. If no reply |
241 | is received within 30 seconds, the peer is considered unreachable and the |
482 | is received within 15 seconds, the peer is considered unreachable and the |
242 | connection is closed. |
483 | connection is closed. |
|
|
484 | .IP "loglevel = noise|trace|debug|info|notice|warn|error|critical" 4 |
|
|
485 | .IX Item "loglevel = noise|trace|debug|info|notice|warn|error|critical" |
|
|
486 | Set the logging level. Connection established messages are logged at level |
|
|
487 | \&\f(CW\*(C`info\*(C'\fR, notable errors are logged with \f(CW\*(C`error\*(C'\fR. Default is \f(CW\*(C`info\*(C'\fR. |
243 | .IP "mtu = bytes" 4 |
488 | .IP "mtu = bytes" 4 |
244 | .IX Item "mtu = bytes" |
489 | .IX Item "mtu = bytes" |
245 | Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically |
490 | Sets the maximum \s-1MTU\s0 that should be used on outgoing packets (basically |
246 | the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate |
491 | the \s-1MTU\s0 of the outgoing interface) The daemon will automatically calculate |
247 | maximum overhead (e.g. udp header size, encryption blocksize...) and pass |
492 | maximum overhead (e.g. \s-1UDP\s0 header size, encryption blocksize...) and pass |
248 | this information to the \f(CW\*(C`if\-up\*(C'\fR script. |
493 | this information to the \f(CW\*(C`if\-up\*(C'\fR script. |
249 | .Sp |
494 | .Sp |
250 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
495 | Recommended values are 1500 (ethernet), 1492 (pppoe), 1472 (pptp). |
251 | .Sp |
496 | .Sp |
252 | This value must be the minimum of the mtu values of all hosts. |
497 | This value must be the minimum of the \s-1MTU\s0 values of all nodes. |
253 | .IP "ip-proto = numerical-ip-protocol" 4 |
498 | .IP "nfmark = integer" 4 |
254 | .IX Item "ip-proto = numerical-ip-protocol" |
499 | .IX Item "nfmark = integer" |
255 | Sets the protocol number to be used for the rawip protocol. This is a |
500 | This advanced option, when set to a nonzero value (default: \f(CW0\fR), tries |
256 | global option because all hosts must use the same protocol, and since |
501 | to set the netfilter mark (or fwmark) value on all sockets gvpe uses to |
257 | there are no port numbers, you cannot easily run more than one gvpe |
502 | send packets. |
258 | instance using the same protocol, nor can you share the protocol with |
|
|
259 | other programs. |
|
|
260 | .Sp |
503 | .Sp |
261 | The default is 47 (\s-1GRE\s0), which has a good chance of tunneling through |
504 | This can be used to make gvpe use a different set of routing rules. For |
262 | firewalls (but note that the rawip protocol is not \s-1GRE\s0 compatible). Other |
505 | example, on GNU/Linux, the \f(CW\*(C`if\-up\*(C'\fR could set \f(CW\*(C`nfmark\*(C'\fR to 1000 and then |
263 | common choices are 50 (\s-1IPSEC\s0, \s-1ESP\s0), 51 (\s-1IPSEC\s0, \s-1AH\s0), 4 (\s-1IPIP\s0 tunnels) or 98 |
506 | put all routing rules into table \f(CW99\fR and then use an ip rule to make |
264 | (\s-1ENCAP\s0, rfc1241) |
507 | gvpe traffic avoid that routing table, in effect routing normal traffic |
265 | .IP "if-up = relative-or-absolute-path" 4 |
508 | via gvpe and gvpe traffic via the normal system routing tables: |
266 | .IX Item "if-up = relative-or-absolute-path" |
|
|
267 | Sets the path of a script that should be called immediately after the |
|
|
268 | network interface is initialized (but not neccessarily up). The following |
|
|
269 | environment variables are passed to it (the values are just examples): |
|
|
270 | .RS 4 |
|
|
271 | .IP "CONFBASE=/etc/gvpe" 4 |
|
|
272 | .IX Item "CONFBASE=/etc/gvpe" |
|
|
273 | The configuration base directory. |
|
|
274 | .IP "IFNAME=vpn0" 4 |
|
|
275 | .IX Item "IFNAME=vpn0" |
|
|
276 | The interface to initialize. |
|
|
277 | .IP "MTU=1436" 4 |
|
|
278 | .IX Item "MTU=1436" |
|
|
279 | The \s-1MTU\s0 to set the interface to. You can use lower values (if done |
|
|
280 | consistently on all hosts), but this is usually ineffective. |
|
|
281 | .IP "MAC=fe:fd:80:00:00:01" 4 |
|
|
282 | .IX Item "MAC=fe:fd:80:00:00:01" |
|
|
283 | The \s-1MAC\s0 address to set the interface to. The script *must* set the |
|
|
284 | interface \s-1MAC\s0 to this value. You will most likely use one of these: |
|
|
285 | .Sp |
509 | .Sp |
286 | .Vb 2 |
510 | .Vb 1 |
287 | \& ip link set $IFNAME address $MAC mtu $MTU up # GNU/Linux |
511 | \& ip rule add not fwmark 1000 lookup 99 |
288 | \& ifconfig $IFNAME ether $MAC mtu $MTU up # FreeBSD |
|
|
289 | .Ve |
512 | .Ve |
290 | .Sp |
|
|
291 | Please see the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for platform-specific information. |
|
|
292 | .IP "IFTYPE=native # or tincd" 4 |
|
|
293 | .IX Item "IFTYPE=native # or tincd" |
|
|
294 | .PD 0 |
|
|
295 | .IP "IFSUBTYPE=linux # or freebsd, darwin etc.." 4 |
|
|
296 | .IX Item "IFSUBTYPE=linux # or freebsd, darwin etc.." |
|
|
297 | .PD |
|
|
298 | The interface type (\f(CW\*(C`native\*(C'\fR or \f(CW\*(C`tincd\*(C'\fR) and the subtype (usually the os |
|
|
299 | name in lowercase) that this gvpe was configured for. Can be used to select |
|
|
300 | the correct syntax to use for network-related commands. |
|
|
301 | .IP "NODENAME=branch1" 4 |
|
|
302 | .IX Item "NODENAME=branch1" |
|
|
303 | The nickname of the current node, as passed to the gvpe daemon. |
|
|
304 | .IP "NODEID=1" 4 |
|
|
305 | .IX Item "NODEID=1" |
|
|
306 | The numerical node id of the current node. The first node mentioned in the |
|
|
307 | config file gets \s-1ID\s0 1, the second \s-1ID\s0 2 and so on. |
|
|
308 | .RE |
|
|
309 | .RS 4 |
|
|
310 | .Sp |
|
|
311 | Here is a simple if-up script: |
|
|
312 | .Sp |
|
|
313 | .Vb 5 |
|
|
314 | \& #!/bin/sh |
|
|
315 | \& ip link set $IFNAME address $MAC mtu $MTU up |
|
|
316 | \& [ $NODENAME = branch1 ] && ip addr add 10.0.0.1 dev $IFNAME |
|
|
317 | \& [ $NODENAME = branch2 ] && ip addr add 10.1.0.1 dev $IFNAME |
|
|
318 | \& ip route add 10.0.0.0/8 dev $IFNAME |
|
|
319 | .Ve |
|
|
320 | .Sp |
|
|
321 | More complicated examples (using routing to reduce arp traffic) can be |
|
|
322 | found in the etc/ subdirectory of the distribution. |
|
|
323 | .RE |
|
|
324 | .IP "node-up = relative-or-absolute-path" 4 |
513 | .IP "node-up = relative-or-absolute-path" 4 |
325 | .IX Item "node-up = relative-or-absolute-path" |
514 | .IX Item "node-up = relative-or-absolute-path" |
326 | Sets a command (default: no script) that should be called whenever a |
515 | Sets a command (default: none) that should be called whenever a connection |
327 | connection is established (even on rekeying operations). In addition |
516 | is established (even on rekeying operations). Note that node\-up/down |
|
|
517 | scripts will be run asynchronously, but execution is serialised, so there |
|
|
518 | will only ever be one such script running. |
|
|
519 | .Sp |
328 | to the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following environment |
520 | In addition to all the variables passed to \f(CW\*(C`if\-up\*(C'\fR scripts, the following |
329 | variables will be set: |
521 | environment variables will be set (values are just examples): |
330 | .RS 4 |
522 | .RS 4 |
331 | .IP "DESTNODE=branch2" 4 |
523 | .IP "DESTNODE=branch2" 4 |
332 | .IX Item "DESTNODE=branch2" |
524 | .IX Item "DESTNODE=branch2" |
333 | The name of the remote node. |
525 | The name of the remote node. |
334 | .IP "DESTID=2" 4 |
526 | .IP "DESTID=2" 4 |
335 | .IX Item "DESTID=2" |
527 | .IX Item "DESTID=2" |
336 | The node id of the remote node. |
528 | The node id of the remote node. |
|
|
529 | .IP "DESTSI=rawip/88.99.77.55:0" 4 |
|
|
530 | .IX Item "DESTSI=rawip/88.99.77.55:0" |
|
|
531 | The \*(L"socket info\*(R" of the target node, protocol dependent but usually in |
|
|
532 | the format protocol/ip:port. |
337 | .IP "DESTIP=188.13.66.8" 4 |
533 | .IP "DESTIP=188.13.66.8" 4 |
338 | .IX Item "DESTIP=188.13.66.8" |
534 | .IX Item "DESTIP=188.13.66.8" |
339 | The numerical \s-1IP\s0 address of the remote host (gvpe accepts connections from |
535 | The numerical \s-1IP\s0 address of the remote node (gvpe accepts connections from |
340 | everywhere, as long as the other host can authenticate itself). |
536 | everywhere, as long as the other node can authenticate itself). |
341 | .IP "DESTPORT=655 # deprecated" 4 |
537 | .IP "DESTPORT=655 # deprecated" 4 |
342 | .IX Item "DESTPORT=655 # deprecated" |
538 | .IX Item "DESTPORT=655 # deprecated" |
343 | The \s-1UDP\s0 port used by the other side. |
539 | The protocol port used by the other side, if applicable. |
344 | .IP "STATE=UP" 4 |
540 | .IP "STATE=up" 4 |
345 | .IX Item "STATE=UP" |
541 | .IX Item "STATE=up" |
346 | Node-up scripts get called with STATE=UP, node-down scripts get called |
542 | Node-up scripts get called with STATE=up, node-change scripts get called |
347 | with STATE=DOWN. |
543 | with STATE=change and node-down scripts get called with STATE=down. |
348 | .RE |
544 | .RE |
349 | .RS 4 |
545 | .RS 4 |
350 | .Sp |
546 | .Sp |
351 | Here is a nontrivial example that uses nsupdate to update the name => ip |
547 | Here is a nontrivial example that uses nsupdate to update the name => ip |
352 | mapping in some dns zone: |
548 | mapping in some \s-1DNS\s0 zone: |
353 | .Sp |
549 | .Sp |
354 | .Vb 6 |
550 | .Vb 6 |
355 | \& #!/bin/sh |
551 | \& #!/bin/sh |
356 | \& { |
552 | \& { |
357 | \& echo update delete $DESTNODE.lowttl.example.net. a |
553 | \& echo update delete $DESTNODE.lowttl.example.net. a |
358 | \& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
554 | \& echo update add $DESTNODE.lowttl.example.net. 1 in a $DESTIP |
359 | \& echo |
555 | \& echo |
360 | \& } | nsupdate -d -k $CONFBASE:key.example.net. |
556 | \& } | nsupdate \-d \-k $CONFBASE:key.example.net. |
361 | .Ve |
557 | .Ve |
362 | .RE |
558 | .RE |
|
|
559 | .IP "node-change = relative-or-absolute-path" 4 |
|
|
560 | .IX Item "node-change = relative-or-absolute-path" |
|
|
561 | Same as \f(CW\*(C`node\-change\*(C'\fR, but gets called whenever something about a |
|
|
562 | connection changes (such as the source \s-1IP\s0 address). |
363 | .IP "node-down = relative-or-absolute-path" 4 |
563 | .IP "node-down = relative-or-absolute-path" 4 |
364 | .IX Item "node-down = relative-or-absolute-path" |
564 | .IX Item "node-down = relative-or-absolute-path" |
365 | Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost. |
565 | Same as \f(CW\*(C`node\-up\*(C'\fR, but gets called whenever a connection is lost. |
366 | .IP "http-proxy-host = hostname/ip" 4 |
|
|
367 | .IX Item "http-proxy-host = hostname/ip" |
|
|
368 | The \f(CW\*(C`http\-proxy\-*\*(C'\fR family of options are only available if gvpe was |
|
|
369 | compiled with the \f(CW\*(C`\-\-enable\-http\-proxy\*(C'\fR option and enable tunneling of |
|
|
370 | tcp connections through a http proxy server. |
|
|
371 | .Sp |
|
|
372 | \&\f(CW\*(C`http\-proxy\-host\*(C'\fR and \f(CW\*(C`http\-proxy\-port\*(C'\fR should specify the hostname and |
|
|
373 | port number of the proxy server. See \f(CW\*(C`http\-proxy\-loginpw\*(C'\fR if your proxy |
|
|
374 | requires authentication. |
|
|
375 | .Sp |
|
|
376 | Please note that gvpe will still try to resolve all hostnames in the |
|
|
377 | configuration file, so if you are behind a proxy without access to a dns |
|
|
378 | server better use numerical \s-1IP\s0 addresses. |
|
|
379 | .Sp |
|
|
380 | To make best use of this option disable all protocols except tcp in your |
|
|
381 | config file and make sure your routers (or all other hosts) are listening |
|
|
382 | on a port that the proxy allows (443, https, is a common choice). |
|
|
383 | .Sp |
|
|
384 | If you have a router, connecting to it will suffice. Otherwise tcp must be |
|
|
385 | enabled on all hosts. |
|
|
386 | .Sp |
|
|
387 | Example: |
|
|
388 | .Sp |
|
|
389 | .Vb 3 |
|
|
390 | \& http-proxy-host = proxy.example.com |
|
|
391 | \& http-proxy-port = 3128 # 8080 is another common choice |
|
|
392 | \& http-proxy-auth = schmorp:grumbeere |
|
|
393 | .Ve |
|
|
394 | .IP "http-proxy-port = proxy-tcp-port" 4 |
|
|
395 | .IX Item "http-proxy-port = proxy-tcp-port" |
|
|
396 | The port where your proxy server listens. |
|
|
397 | .IP "http-proxy-auth = login:password" 4 |
|
|
398 | .IX Item "http-proxy-auth = login:password" |
|
|
399 | The optional login and password used to authenticate to the proxy server, |
|
|
400 | seperated by a literal colon (\f(CW\*(C`:\*(C'\fR). Only basic authentication is |
|
|
401 | currently supported. |
|
|
402 | .IP "pid-file = path" 4 |
566 | .IP "pid-file = path" 4 |
403 | .IX Item "pid-file = path" |
567 | .IX Item "pid-file = path" |
404 | The path to the pid file to check and create (Default: |
568 | The path to the pid file to check and create |
|
|
569 | (default: \f(CW\*(C`LOCALSTATEDIR/run/gvpe.pid\*(C'\fR). The first \f(CW%s\fR is replaced by |
|
|
570 | the nodename \- any other use of \f(CW\*(C`%\*(C'\fR must be written as \f(CW\*(C`%%\*(C'\fR. |
|
|
571 | .IP "private-key = relative-path-to-key" 4 |
|
|
572 | .IX Item "private-key = relative-path-to-key" |
|
|
573 | Sets the path (relative to the config directory) to the private key |
|
|
574 | (default: \f(CW\*(C`hostkey\*(C'\fR). This is a printf format string so every \f(CW\*(C`%\*(C'\fR must |
|
|
575 | be doubled. A single \f(CW%s\fR is replaced by the hostname, so you could |
|
|
576 | use paths like \f(CW\*(C`hostkeys/%s\*(C'\fR to fetch the files at the location where |
|
|
577 | \&\f(CW\*(C`gvpectrl\*(C'\fR puts them. |
|
|
578 | .Sp |
|
|
579 | Since only the private key file of the current node is used and the |
|
|
580 | private key file should be kept secret per-node to avoid spoofing, it is |
|
|
581 | not recommended to use this feature. |
|
|
582 | .IP "rekey = seconds" 4 |
|
|
583 | .IX Item "rekey = seconds" |
|
|
584 | Sets the rekeying interval in seconds (default: \f(CW3607\fR). Connections are |
|
|
585 | reestablished every \f(CW\*(C`rekey\*(C'\fR seconds, making them use a new encryption |
|
|
586 | key. |
|
|
587 | .IP "seed-device = path" 4 |
|
|
588 | .IX Item "seed-device = path" |
|
|
589 | The random device used to initially and regularly seed the random |
|
|
590 | number generator (default: \fI/dev/urandom\fR). Randomness is of paramount |
|
|
591 | importance to the security of the algorithms used in gvpe. |
|
|
592 | .Sp |
|
|
593 | On program start and every seed-interval, gvpe will read 64 octets. |
|
|
594 | .Sp |
|
|
595 | Setting this path to the empty string will disable this functionality |
|
|
596 | completely (the underlying crypto library will likely look for entropy |
|
|
597 | sources on it's own though, so not all is lost). |
|
|
598 | .IP "seed-interval = seconds" 4 |
|
|
599 | .IX Item "seed-interval = seconds" |
|
|
600 | The number of seconds between reseeds of the random number generator |
|
|
601 | (default: \f(CW3613\fR). A value of \f(CW0\fR disables this regular reseeding. |
|
|
602 | .IP "serial = string" 4 |
|
|
603 | .IX Item "serial = string" |
|
|
604 | The configuration serial number. This can be any string up to 16 bytes |
|
|
605 | length. Only when the serial matches on both sides of a conenction will |
|
|
606 | the connection succeed. This is \fInot\fR a security mechanism and eay to |
|
|
607 | spoof, this mechanism exists to alert users that their config is outdated. |
|
|
608 | .Sp |
|
|
609 | It's recommended to specify this is a date string such as \f(CW\*(C`2013\-05\-05\*(C'\fR or |
|
|
610 | \&\f(CW\*(C`20121205084417).\*(C'\fR |
|
|
611 | .Sp |
|
|
612 | The exact algorithm is as this: if a connection request is received form a |
|
|
613 | node with an identical serial, then it succeeds normally. |
|
|
614 | .Sp |
|
|
615 | If the remote serial is lower than the local serial, it is ignored. |
|
|
616 | .Sp |
|
|
617 | If the remote serial is higher than the local serial, a warning message is |
|
|
618 | logged. |
405 | .Sh "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0" |
619 | .SS "\s-1NODE\s0 \s-1SPECIFIC\s0 \s-1SETTINGS\s0" |
406 | .IX Subsection "NODE SPECIFIC SETTINGS" |
620 | .IX Subsection "NODE SPECIFIC SETTINGS" |
407 | The following settings are node\-specific, that is, every node can have |
621 | The following settings are node-specific, that is, every node can have |
408 | different settings, even within the same gvpe instance. Settings that are |
622 | different settings, even within the same gvpe instance. Settings that are |
409 | executed before the first node section set the defaults, settings that are |
623 | set before the first node section set the defaults, settings that are |
410 | executed within a node section only apply to the given node. |
624 | set within a node section only apply to the given node. |
|
|
625 | .IP "allow-direct = nodename" 4 |
|
|
626 | .IX Item "allow-direct = nodename" |
|
|
627 | Allow direct connections to this node. See \f(CW\*(C`deny\-direct\*(C'\fR for more info. |
|
|
628 | .IP "compress = yes|true|on | no|false|off" 4 |
|
|
629 | .IX Item "compress = yes|true|on | no|false|off" |
|
|
630 | For the current node, this specified whether it will accept compressed |
|
|
631 | packets, and for all other nodes, this specifies whether to try to |
|
|
632 | compress data packets sent to this node (default: \f(CW\*(C`yes\*(C'\fR). Compression is |
|
|
633 | really cheap even on slow computers, has no size overhead at all and will |
|
|
634 | only be used when the other side supports compression, so enabling this is |
|
|
635 | often a good idea. |
|
|
636 | .IP "connect = ondemand | never | always | disabled" 4 |
|
|
637 | .IX Item "connect = ondemand | never | always | disabled" |
|
|
638 | Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always |
|
|
639 | try to establish and keep a connection to the given node), \f(CW\*(C`never\*(C'\fR |
|
|
640 | (never initiate a connection to the given host, but accept connections), |
|
|
641 | \&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection when there are outstanding |
|
|
642 | packets in the queue and take it down after the keepalive interval) or |
|
|
643 | \&\f(CW\*(C`disabled\*(C'\fR (node is bad, don't talk to it). |
|
|
644 | .Sp |
|
|
645 | Routers will automatically be forced to \f(CW\*(C`always\*(C'\fR unless they are |
|
|
646 | \&\f(CW\*(C`disabled\*(C'\fR, to ensure all nodes can talk to each other. |
|
|
647 | .IP "deny-direct = nodename | *" 4 |
|
|
648 | .IX Item "deny-direct = nodename | *" |
|
|
649 | Deny direct connections to the specified node (or all nodes when \f(CW\*(C`*\*(C'\fR |
|
|
650 | is given). Only one node can be specified, but you can use multiple |
|
|
651 | \&\f(CW\*(C`allow\-direct\*(C'\fR and \f(CW\*(C`deny\-direct\*(C'\fR statements. This only makes sense in |
|
|
652 | networks with routers, as routers are required for indirect connections. |
|
|
653 | .Sp |
|
|
654 | Sometimes, a node cannot reach some other nodes for reasons of network |
|
|
655 | connectivity. For example, a node behind a firewall that only allows |
|
|
656 | connections to/from a single other node in the network. In this case one |
|
|
657 | should specify \f(CW\*(C`deny\-direct = *\*(C'\fR and \f(CW\*(C`allow\-direct = othernodename\*(C'\fR (the other |
|
|
658 | node \fImust\fR be a router for this to work). |
|
|
659 | .Sp |
|
|
660 | The algorithm to check whether a connection may be direct is as follows: |
|
|
661 | .Sp |
|
|
662 | 1. Other node mentioned in an \f(CW\*(C`allow\-direct\*(C'\fR? If yes, allow the connection. |
|
|
663 | .Sp |
|
|
664 | 2. Other node mentioned in a \f(CW\*(C`deny\-direct\*(C'\fR? If yes, deny direct connections. |
|
|
665 | .Sp |
|
|
666 | 3. Allow the connection. |
|
|
667 | .Sp |
|
|
668 | That is, \f(CW\*(C`allow\-direct\*(C'\fR takes precedence over \f(CW\*(C`deny\-direct\*(C'\fR. |
|
|
669 | .Sp |
|
|
670 | The check is done in both directions, i.e. both nodes must allow a direct |
|
|
671 | connection before one is attempted, so you only need to specify connect |
|
|
672 | limitations on one node. |
|
|
673 | .IP "dns-domain = domain-suffix" 4 |
|
|
674 | .IX Item "dns-domain = domain-suffix" |
|
|
675 | The \s-1DNS\s0 domain suffix that points to the \s-1DNS\s0 tunnel server for this node. |
|
|
676 | .Sp |
|
|
677 | The domain must point to a \s-1NS\s0 record that points to the \fIdns-hostname\fR, |
|
|
678 | i.e. |
|
|
679 | .Sp |
|
|
680 | .Vb 2 |
|
|
681 | \& dns\-domainname = tunnel.example.net |
|
|
682 | \& dns\-hostname = tunnel\-server.example.net |
|
|
683 | .Ve |
|
|
684 | .Sp |
|
|
685 | Corresponds to the following \s-1DNS\s0 entries in the \f(CW\*(C`example.net\*(C'\fR domain: |
|
|
686 | .Sp |
|
|
687 | .Vb 2 |
|
|
688 | \& tunnel.example.net. NS tunnel\-server.example.net. |
|
|
689 | \& tunnel\-server.example.net. A 13.13.13.13 |
|
|
690 | .Ve |
|
|
691 | .IP "dns-hostname = hostname/ip" 4 |
|
|
692 | .IX Item "dns-hostname = hostname/ip" |
|
|
693 | The address to bind the \s-1DNS\s0 tunnel socket to, similar to the \f(CW\*(C`hostname\*(C'\fR, |
|
|
694 | but for the \s-1DNS\s0 tunnel protocol only. Default: \f(CW0.0.0.0\fR, but that might |
|
|
695 | change. |
|
|
696 | .IP "dns-port = port-number" 4 |
|
|
697 | .IX Item "dns-port = port-number" |
|
|
698 | The port to bind the \s-1DNS\s0 tunnel socket to. Must be \f(CW53\fR on \s-1DNS\s0 tunnel servers. |
|
|
699 | .IP "enable-dns = yes|true|on | no|false|off" 4 |
|
|
700 | .IX Item "enable-dns = yes|true|on | no|false|off" |
|
|
701 | See \fIgvpe.protocol\fR\|(7) for a description of the \s-1DNS\s0 transport |
|
|
702 | protocol. Avoid this protocol if you can. |
|
|
703 | .Sp |
|
|
704 | Enable the \s-1DNS\s0 tunneling protocol on this node, either as server or as |
|
|
705 | client. Support for this transport protocol is only available when gvpe |
|
|
706 | was compiled using the \f(CW\*(C`\-\-enable\-dns\*(C'\fR option. |
|
|
707 | .IP "enable-icmp = yes|true|on | no|false|off" 4 |
|
|
708 | .IX Item "enable-icmp = yes|true|on | no|false|off" |
|
|
709 | See \fIgvpe.protocol\fR\|(7) for a description of the \s-1ICMP\s0 transport protocol. |
|
|
710 | .Sp |
|
|
711 | Enable the \s-1ICMP\s0 transport using \s-1ICMP\s0 packets of type \f(CW\*(C`icmp\-type\*(C'\fR on this |
|
|
712 | node. |
|
|
713 | .IP "enable-rawip = yes|true|on | no|false|off" 4 |
|
|
714 | .IX Item "enable-rawip = yes|true|on | no|false|off" |
|
|
715 | See \fIgvpe.protocol\fR\|(7) for a description of the \s-1RAW\s0 \s-1IP\s0 transport protocol. |
|
|
716 | .Sp |
|
|
717 | Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol |
|
|
718 | (default: \f(CW\*(C`no\*(C'\fR). |
|
|
719 | .IP "enable-tcp = yes|true|on | no|false|off" 4 |
|
|
720 | .IX Item "enable-tcp = yes|true|on | no|false|off" |
|
|
721 | See \fIgvpe.protocol\fR\|(7) for a description of the \s-1TCP\s0 transport protocol. |
|
|
722 | .Sp |
|
|
723 | Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port |
|
|
724 | (default: \f(CW\*(C`no\*(C'\fR). Support for this transport protocol is only available |
|
|
725 | when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option. |
|
|
726 | .IP "enable-udp = yes|true|on | no|false|off" 4 |
|
|
727 | .IX Item "enable-udp = yes|true|on | no|false|off" |
|
|
728 | See \fIgvpe.protocol\fR\|(7) for a description of the \s-1UDP\s0 transport protocol. |
|
|
729 | .Sp |
|
|
730 | Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`no\*(C'\fR). |
|
|
731 | .IP "hostname = hostname | ip [can not be defaulted]" 4 |
|
|
732 | .IX Item "hostname = hostname | ip [can not be defaulted]" |
|
|
733 | Forces the address of this node to be set to the given \s-1DNS\s0 hostname or \s-1IP\s0 |
|
|
734 | address. It will be resolved before each connect request, so dyndns should |
|
|
735 | work fine. If this setting is not specified and a router is available, |
|
|
736 | then the router will be queried for the address of this node. Otherwise, |
|
|
737 | the connection attempt will fail. |
|
|
738 | .Sp |
|
|
739 | Note that \s-1DNS\s0 resolving is done synchronously, pausing the daemon. If that |
|
|
740 | is an issue you need to specify \s-1IP\s0 addresses. |
|
|
741 | .IP "icmp-type = integer" 4 |
|
|
742 | .IX Item "icmp-type = integer" |
|
|
743 | Sets the type value to be used for outgoing (and incoming) packets sent |
|
|
744 | via the \s-1ICMP\s0 transport. |
|
|
745 | .Sp |
|
|
746 | The default is \f(CW0\fR (which is \f(CW\*(C`echo\-reply\*(C'\fR, also known as |
|
|
747 | \&\*(L"ping-reply\*(R"). Other useful values include \f(CW8\fR (\f(CW\*(C`echo\-request\*(C'\fR, a.k.a. |
|
|
748 | \&\*(L"ping\*(R") and \f(CW11\fR (\f(CW\*(C`time\-exceeded\*(C'\fR), but any 8\-bit value can be used. |
|
|
749 | .IP "if-up-data = value" 4 |
|
|
750 | .IX Item "if-up-data = value" |
|
|
751 | The value specified using this directive will be passed to the \f(CW\*(C`if\-up\*(C'\fR |
|
|
752 | script in the environment variable \f(CW\*(C`IFUPDATA\*(C'\fR. |
|
|
753 | .IP "inherit-tos = yes|true|on | no|false|off" 4 |
|
|
754 | .IX Item "inherit-tos = yes|true|on | no|false|off" |
|
|
755 | Whether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when |
|
|
756 | sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then |
|
|
757 | outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent |
|
|
758 | to the tunnel device, which is usually what you want. |
|
|
759 | .IP "low-power = yes|true|on | no|false|off" 4 |
|
|
760 | .IX Item "low-power = yes|true|on | no|false|off" |
|
|
761 | If true, designates a node as a low-power node. Low-power nodes use |
|
|
762 | larger timeouts and try to reduce cpu time. Other nodes talking to a |
|
|
763 | low-power node will also use larger timeouts, and will use less aggressive |
|
|
764 | optimisations, in the hope of reducing load. Security is not compromised. |
|
|
765 | .Sp |
|
|
766 | The typical low-power node would be a mobile phone, where wakeups and |
|
|
767 | encryption can significantly increase power drain. |
|
|
768 | .IP "max-retry = positive-number" 4 |
|
|
769 | .IX Item "max-retry = positive-number" |
|
|
770 | The maximum interval in seconds (default: \f(CW3600\fR, one hour) between |
|
|
771 | retries to establish a connection to this node. When a connection cannot |
|
|
772 | be established, gvpe uses exponential back-off capped at this value. It's |
|
|
773 | sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on |
|
|
774 | connections to routers that usually are stable but sometimes are down, to |
|
|
775 | assure quick reconnections even after longer downtimes. |
|
|
776 | .IP "max-ttl = seconds" 4 |
|
|
777 | .IX Item "max-ttl = seconds" |
|
|
778 | Expire packets that couldn't be sent after this many seconds |
|
|
779 | (default: \f(CW60\fR). Gvpe will normally queue packets for a node without an |
|
|
780 | active connection, in the hope of establishing a connection soon. This |
|
|
781 | value specifies the maximum lifetime a packet will stay in the queue, if a |
|
|
782 | packet gets older, it will be thrown away. |
|
|
783 | .IP "max-queue = positive\-number>=1" 4 |
|
|
784 | .IX Item "max-queue = positive-number>=1" |
|
|
785 | The maximum number of packets that will be queued (default: \f(CW512\fR) |
|
|
786 | for this node. If more packets are sent then earlier packets will be |
|
|
787 | expired. See \f(CW\*(C`max\-ttl\*(C'\fR, above. |
|
|
788 | .IP "router-priority = 0 | 1 | positive\-number>=2" 4 |
|
|
789 | .IX Item "router-priority = 0 | 1 | positive-number>=2" |
|
|
790 | Sets the router priority of the given node (default: \f(CW0\fR, disabled). |
|
|
791 | .Sp |
|
|
792 | If some node tries to connect to another node but it doesn't have a |
|
|
793 | hostname, it asks a router node for it's \s-1IP\s0 address. The router node |
|
|
794 | chosen is the one with the highest priority larger than \f(CW1\fR that is |
|
|
795 | currently reachable. This is called a \fImediated\fR connection, as the |
|
|
796 | connection itself will still be direct, but it uses another node to |
|
|
797 | mediate between the two nodes. |
|
|
798 | .Sp |
|
|
799 | The value \f(CW0\fR disables routing, that means if the node receives a packet |
|
|
800 | not for itself it will not forward it but instead drop it. |
|
|
801 | .Sp |
|
|
802 | The special value \f(CW1\fR allows other hosts to route through the router |
|
|
803 | host, but they will never route through it by default (i.e. the config |
|
|
804 | file of another node needs to specify a router priority higher than one |
|
|
805 | to choose such a node for routing). |
|
|
806 | .Sp |
|
|
807 | The idea behind this is that some hosts can, if required, bump the |
|
|
808 | \&\f(CW\*(C`router\-priority\*(C'\fR setting to higher than \f(CW1\fR in their local config to |
|
|
809 | route through specific hosts. If \f(CW\*(C`router\-priority\*(C'\fR is \f(CW0\fR, then routing |
|
|
810 | will be refused, so \f(CW1\fR serves as a \*(L"enable, but do not use by default\*(R" |
|
|
811 | switch. |
|
|
812 | .Sp |
|
|
813 | Nodes with \f(CW\*(C`router\-priority\*(C'\fR set to \f(CW2\fR or higher will always be forced |
|
|
814 | to \f(CW\*(C`connect\*(C'\fR = \f(CW\*(C`always\*(C'\fR (unless they are \f(CW\*(C`disabled\*(C'\fR). |
|
|
815 | .IP "tcp-port = port-number" 4 |
|
|
816 | .IX Item "tcp-port = port-number" |
|
|
817 | Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number. |
411 | .IP "udp-port = port-number" 4 |
818 | .IP "udp-port = port-number" 4 |
412 | .IX Item "udp-port = port-number" |
819 | .IX Item "udp-port = port-number" |
413 | Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not |
820 | Sets the port number used by the \s-1UDP\s0 protocol (default: \f(CW655\fR, not |
414 | officially assigned by \s-1IANA\s0!). |
821 | officially assigned by \s-1IANA\s0!). |
415 | .IP "tcp-port = port-number" 4 |
|
|
416 | .IX Item "tcp-port = port-number" |
|
|
417 | Similar to \f(CW\*(C`udp\-port\*(C'\fR (default: \f(CW655\fR), but sets the \s-1TCP\s0 port number. |
|
|
418 | .IP "enable-rawip = yes|true|on | no|false|off" 4 |
|
|
419 | .IX Item "enable-rawip = yes|true|on | no|false|off" |
|
|
420 | Enable the \s-1RAW\s0 IPv4 transport using the \f(CW\*(C`ip\-proto\*(C'\fR protocol |
|
|
421 | (default: \f(CW\*(C`no\*(C'\fR). This is the best choice, since the overhead per packet |
|
|
422 | is only 38 bytes, as opposed to \s-1UDP\s0's 58 (or \s-1TCP\s0's 60+). |
|
|
423 | .IP "enable-udp = yes|true|on | no|false|off" 4 |
|
|
424 | .IX Item "enable-udp = yes|true|on | no|false|off" |
|
|
425 | Enable the UDPv4 transport using the \f(CW\*(C`udp\-port\*(C'\fR port (default: \f(CW\*(C`yes\*(C'\fR, |
|
|
426 | but this will change!). This is a good general choice since \s-1UDP\s0 tunnels |
|
|
427 | well through many firewalls. |
|
|
428 | .Sp |
|
|
429 | \&\s-1NOTE:\s0 Please specify \f(CW\*(C`enable\-udp = yes\*(C'\fR even though it is the default, as |
|
|
430 | some future version will have all protocols disabled by default. |
|
|
431 | .IP "enable-tcp = yes|true|on | no|false|off" 4 |
|
|
432 | .IX Item "enable-tcp = yes|true|on | no|false|off" |
|
|
433 | Enable the TCPv4 transport using the \f(CW\*(C`tcp\-port\*(C'\fR port |
|
|
434 | (default: \f(CW\*(C`no\*(C'\fR). Support for this horribly unsuitable protocol is only |
|
|
435 | available when gvpe was compiled using the \f(CW\*(C`\-\-enable\-tcp\*(C'\fR option. Never |
|
|
436 | use this transport unless you really must, it is horribly ineffiecent and |
|
|
437 | resource-intensive compared to the other transports. |
|
|
438 | .IP "router-priority = 0 | 1 | positive\-number>2" 4 |
|
|
439 | .IX Item "router-priority = 0 | 1 | positive-number>2" |
|
|
440 | Sets the router priority of the given host (default: \f(CW0\fR, disabled). If |
|
|
441 | some host tries to connect to another host without a hostname, it asks |
|
|
442 | the router host for it's \s-1IP\s0 address. The router host is the one with the |
|
|
443 | highest priority larger than \f(CW1\fR that is currently reachable. |
|
|
444 | .Sp |
|
|
445 | Make sure all hosts always connect (\f(CW\*(C`connect = always\*(C'\fR) to the router |
|
|
446 | hosts, otherwise connecting to them might be impossible. |
|
|
447 | .Sp |
|
|
448 | The special value \f(CW1\fR allows other hosts to route through the router |
|
|
449 | host, but they will never route through it by default. The value \f(CW0\fR |
|
|
450 | disables routing. The idea behind this is that some hosts can, if |
|
|
451 | required, bump the \f(CW\*(C`router\-priority\*(C'\fR setting to higher than \f(CW1\fR in their |
|
|
452 | local config to route through specific hosts. If \f(CW\*(C`router\-priority\*(C'\fR is |
|
|
453 | \&\f(CW0\fR, then routing will be refused, so \f(CW1\fR serves as a \*(L"enable, but do |
|
|
454 | not use by default\*(R" switch. |
|
|
455 | .IP "connect = ondemand | never | always | disabled" 4 |
|
|
456 | .IX Item "connect = ondemand | never | always | disabled" |
|
|
457 | Sets the connect mode (default: \f(CW\*(C`always\*(C'\fR). It can be \f(CW\*(C`always\*(C'\fR (always |
|
|
458 | try to establish and keep a connection to the given host), \f(CW\*(C`never\*(C'\fR |
|
|
459 | (never initiate a connection to the given host, but accept connections), |
|
|
460 | \&\f(CW\*(C`ondemand\*(C'\fR (try to establish a connection on the first packet sent, and |
|
|
461 | take it down after the keepalive interval) or \f(CW\*(C`disabled\*(C'\fR (node is bad, |
|
|
462 | don't talk to it). |
|
|
463 | .IP "inherit-tos = yes|true|on | no|false|off" 4 |
|
|
464 | .IX Item "inherit-tos = yes|true|on | no|false|off" |
|
|
465 | Wether to inherit the \s-1TOS\s0 settings of packets sent to the tunnel when |
|
|
466 | sending packets to this node (default: \f(CW\*(C`yes\*(C'\fR). If set to \f(CW\*(C`yes\*(C'\fR then |
|
|
467 | outgoing tunnel packets will have the same \s-1TOS\s0 setting as the packets sent |
|
|
468 | to the tunnel device, which is usually what you want. |
|
|
469 | .IP "compress = yes|true|on | no|false|off" 4 |
|
|
470 | .IX Item "compress = yes|true|on | no|false|off" |
|
|
471 | Wether to compress data packets sent to this host (default: \f(CW\*(C`yes\*(C'\fR). |
|
|
472 | Compression is really cheap even on slow computers and has no size |
|
|
473 | overhead at all, so enabling this is a good idea. |
|
|
474 | .IP "max-retry = positive-number" 4 |
|
|
475 | .IX Item "max-retry = positive-number" |
|
|
476 | The maximum interval in seconds (default: \f(CW28800\fR, 8 hours) between |
|
|
477 | retries to establish a connection to this node. When a connection cannot |
|
|
478 | be established, gvpe uses exponential backoff capped at this value. It's |
|
|
479 | sometimes useful to set this to a much lower value (e.g. \f(CW120\fR) on |
|
|
480 | connections to routers that usually are stable but sometimes are down, to |
|
|
481 | assure quick reconnections. |
|
|
482 | .SH "CONFIG DIRECTORY LAYOUT" |
822 | .SH "CONFIG DIRECTORY LAYOUT" |
483 | .IX Header "CONFIG DIRECTORY LAYOUT" |
823 | .IX Header "CONFIG DIRECTORY LAYOUT" |
484 | The default (or recommended) directory layout for the config directory is: |
824 | The default (or recommended) directory layout for the config directory is: |
485 | .IP "gvpe.conf" 4 |
825 | .IP "gvpe.conf" 4 |
486 | .IX Item "gvpe.conf" |
826 | .IX Item "gvpe.conf" |
487 | The config file. |
827 | The config file. |
488 | .IP "if-up" 4 |
828 | .IP "if-up" 4 |
489 | .IX Item "if-up" |
829 | .IX Item "if-up" |
490 | The if-up script |
830 | The if-up script |
491 | .IP "node\-up, node-down" 4 |
831 | .IP "node-up, node-down" 4 |
492 | .IX Item "node-up, node-down" |
832 | .IX Item "node-up, node-down" |
493 | If used the node up or node-down scripts. |
833 | If used the node up or node-down scripts. |
494 | .IP "hostkey" 4 |
834 | .IP "hostkey" 4 |
495 | .IX Item "hostkey" |
835 | .IX Item "hostkey" |
496 | The private key (taken from \f(CW\*(C`hostkeys/nodename\*(C'\fR) of the current host. |
836 | The (default path of the) private key of the current host. |
497 | .IP "pubkey/nodename" 4 |
837 | .IP "pubkey/nodename" 4 |
498 | .IX Item "pubkey/nodename" |
838 | .IX Item "pubkey/nodename" |
499 | The public keys of the other nodes, one file per node. |
839 | The public keys of the other nodes, one file per node. |
500 | .SH "SEE ALSO" |
840 | .SH "SEE ALSO" |
501 | .IX Header "SEE ALSO" |
841 | .IX Header "SEE ALSO" |
502 | \&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8). |
842 | \&\fIgvpe\fR\|(5), \fIgvpe\fR\|(8), \fIgvpectrl\fR\|(8). |
503 | .SH "AUTHOR" |
843 | .SH "AUTHOR" |
504 | .IX Header "AUTHOR" |
844 | .IX Header "AUTHOR" |
505 | Marc Lehmann <gvpe@plan9.de> |
845 | Marc Lehmann <gvpe@schmorp.de> |
|
|
846 | .SH "POD ERRORS" |
|
|
847 | .IX Header "POD ERRORS" |
|
|
848 | Hey! \fBThe above document had some coding errors, which are explained below:\fR |
|
|
849 | .IP "Around line 516:" 4 |
|
|
850 | .IX Item "Around line 516:" |
|
|
851 | Unterminated C<...> sequence |