| … | |
… | |
| 28 | = value> pairs. Empty lines are ignored. Comments start with a C<#> and |
28 | = value> pairs. Empty lines are ignored. Comments start with a C<#> and |
| 29 | extend to the end of the line. They can be used on their own lines, or |
29 | extend to the end of the line. They can be used on their own lines, or |
| 30 | after any directives. Whitespace is allowed around the C<=> sign or after |
30 | after any directives. Whitespace is allowed around the C<=> sign or after |
| 31 | values, but not within the variable names or values themselves. |
31 | values, but not within the variable names or values themselves. |
| 32 | |
32 | |
| 33 | The only exception to the above is the "on" directive that can prefix any |
33 | All settings are applied "in order", that is, later settings of the same |
| 34 | C<name = value> setting and will only "execute" it on the named node, or |
34 | variable overwrite earlier ones. |
| 35 | (if the nodename starts with "!") on all nodes except the named one. |
|
|
| 36 | |
35 | |
|
|
36 | The only exceptions to the above are the "on" and "include" directives: |
|
|
37 | |
|
|
38 | =over 4 |
|
|
39 | |
|
|
40 | =item on nodename ... |
|
|
41 | |
|
|
42 | =item on !nodename ... |
|
|
43 | |
|
|
44 | You can prefix any configuration directive with C<on> and a nodename. GVPE |
|
|
45 | will will only "execute" it on the named node, or (if the nodename starts |
|
|
46 | with C<!>) on all nodes except the named one. |
|
|
47 | |
| 37 | For example, set the MTU to C<1450> everywhere, loglevel to C<noise> on |
48 | Example: set the MTU to C<1450> everywhere, C<loglevel> to C<noise> on |
| 38 | branch1, and connect to C<ondemand> everywhere but on branch2: |
49 | C<branch1>, and C<connect> to C<ondemand> everywhere but on branch2. |
| 39 | |
50 | |
| 40 | mtu = 1450 |
51 | mtu = 1450 |
| 41 | on branch1 loglevel = noise |
52 | on branch1 loglevel = noise |
| 42 | on !branch2 connect = ondemand |
53 | on !branch2 connect = ondemand |
| 43 | |
54 | |
| 44 | All settings are applied "in order", that is, later settings of the same |
55 | =item include relative-or-absolute-path |
| 45 | variable overwrite earlier ones. |
56 | |
|
|
57 | Reads the specified file (the path must not contain whitespace or C<=> |
|
|
58 | characters) and evaluate all config directives in it as if they were |
|
|
59 | spelled out in place of the C<include> directive. |
|
|
60 | |
|
|
61 | The path is a printf format string, that is, you must escape any C<%> |
|
|
62 | by doubling it, and you can have a single C<%s> inside, which will be |
|
|
63 | replaced by the current nodename. |
|
|
64 | |
|
|
65 | Relative paths are interpreted relative to the GVPE config directory. |
|
|
66 | |
|
|
67 | Example: include the file F<local.conf> in the config directory on every |
|
|
68 | node. |
|
|
69 | |
|
|
70 | include local.conf |
|
|
71 | |
|
|
72 | Example: include a file F<conf/>nodenameF<.conf> |
|
|
73 | |
|
|
74 | include conf/%s.conf |
|
|
75 | |
|
|
76 | =back |
| 46 | |
77 | |
| 47 | =head1 ANATOMY OF A CONFIG FILE |
78 | =head1 ANATOMY OF A CONFIG FILE |
| 48 | |
79 | |
| 49 | Usually, a config file starts with a few global settings (like the UDP |
80 | Usually, a config file starts with a few global settings (like the UDP |
| 50 | port to listen on), followed by node-specific sections that begin with a |
81 | port to listen on), followed by node-specific sections that begin with a |
| … | |
… | |
| 76 | |
107 | |
| 77 | =item dns-forw-port = port-number |
108 | =item dns-forw-port = port-number |
| 78 | |
109 | |
| 79 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
110 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
| 80 | which is fine in most cases). |
111 | which is fine in most cases). |
|
|
112 | |
|
|
113 | =item dns-case-preserving = yes|true|on | no|false|off |
|
|
114 | |
|
|
115 | Sets whether the DNS transport forwarding server preserves case (DNS |
|
|
116 | servers have to, but some access systems are even more broken than others) |
|
|
117 | (default: true). |
|
|
118 | |
|
|
119 | Normally, when the forwarding server changes the case of domain names then |
|
|
120 | GVPE will automatically set this to false. |
| 81 | |
121 | |
| 82 | =item dns-max-outstanding = integer-number-of-requests |
122 | =item dns-max-outstanding = integer-number-of-requests |
| 83 | |
123 | |
| 84 | The maximum number of outstanding DNS transport requests |
124 | The maximum number of outstanding DNS transport requests |
| 85 | (default: C<100>). GVPE will never issue more requests then the given |
125 | (default: C<100>). GVPE will never issue more requests then the given |
