| … | |
… | |
| 127 | .\} |
127 | .\} |
| 128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
| 129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
| 130 | .\" |
130 | .\" |
| 131 | .IX Title "GVPE.CONF 5" |
131 | .IX Title "GVPE.CONF 5" |
| 132 | .TH GVPE.CONF 5 "2005-03-17" "1.8" "GNU Virtual Private Ethernet" |
132 | .TH GVPE.CONF 5 "2005-03-23" "1.8" "GNU Virtual Private Ethernet" |
| 133 | .SH "NAME" |
133 | .SH "NAME" |
| 134 | gvpe.conf \- configuration file for the GNU VPE daemon |
134 | gvpe.conf \- configuration file for the GNU VPE daemon |
| 135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
| 136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
| 137 | .Vb 3 |
137 | .Vb 3 |
| … | |
… | |
| 202 | (default: \f(CW127.0.0.1\fR, changing it is highly recommended). |
202 | (default: \f(CW127.0.0.1\fR, changing it is highly recommended). |
| 203 | .IP "dns-forw-port = port-number" 4 |
203 | .IP "dns-forw-port = port-number" 4 |
| 204 | .IX Item "dns-forw-port = port-number" |
204 | .IX Item "dns-forw-port = port-number" |
| 205 | The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR, |
205 | The port where the \f(CW\*(C`dns\-forw\-host\*(C'\fR is to be contacted (default: \f(CW53\fR, |
| 206 | which is fine in most cases). |
206 | which is fine in most cases). |
|
|
207 | .IP "dns-max-outstanding = integer-number-of-requests" 4 |
|
|
208 | .IX Item "dns-max-outstanding = integer-number-of-requests" |
|
|
209 | The maximum number of outstanding \s-1DNS\s0 transport requests |
|
|
210 | (default: \f(CW100\fR). \s-1GVPE\s0 will never issue more requests then the given |
|
|
211 | limit without receiving replies. In heavily overloaded situations it might |
|
|
212 | help to set this to a low number (e.g. \f(CW3\fR or even \f(CW1\fR) to limit the |
|
|
213 | number of parallel requests. |
|
|
214 | .Sp |
|
|
215 | The default should be working ok for most links. |
|
|
216 | .IP "dns-overlap-factor = float" 4 |
|
|
217 | .IX Item "dns-overlap-factor = float" |
|
|
218 | The \s-1DNS\s0 transport uses the minimum request latency (\fBmin_latency\fR) seen |
|
|
219 | during a connection as it's timing base. This factor (default: \f(CW0.5\fR, |
|
|
220 | must be > 0) is multiplied by \fBmin_latency\fR to get the maximum sending |
|
|
221 | rate (= minimum send interval), i.e. a factor of \f(CW1\fR means that a new |
|
|
222 | request might be generated every \fBmin_latency\fR seconds, which means on |
|
|
223 | average there should only ever be one outstanding request. A factor of |
|
|
224 | \&\f(CW0.5\fR means that \s-1GVPE\s0 will send requests twice as often as the minimum |
|
|
225 | latency measured. |
|
|
226 | .Sp |
|
|
227 | For congested or picky dns forwarders you could use a value nearer to or |
|
|
228 | exceeding \f(CW1\fR. |
|
|
229 | .Sp |
|
|
230 | The default should be working ok for most links. |
|
|
231 | .IP "dns-send-interval = send-interval-in-seconds" 4 |
|
|
232 | .IX Item "dns-send-interval = send-interval-in-seconds" |
|
|
233 | The minimum send interval (= maximum rate) that the \s-1DNS\s0 transport will |
|
|
234 | use to send new \s-1DNS\s0 requests. \s-1GVPE\s0 will not exceed this rate even when |
|
|
235 | the latency is very low. The default is \f(CW0.01\fR, which means \s-1GVPE\s0 will |
|
|
236 | not send more than 100 \s-1DNS\s0 requests per connection per second. For |
|
|
237 | high-bandwidth links you could go lower, e.g. to \f(CW0.001\fR or so. For |
|
|
238 | congested or rate-limited links, you might want to go higher, say \f(CW0.1\fR, |
|
|
239 | \&\f(CW0.2\fR or even higher. |
|
|
240 | .Sp |
|
|
241 | The default should be working ok for most links. |
|
|
242 | .IP "dns-timeout-factor = float" 4 |
|
|
243 | .IX Item "dns-timeout-factor = float" |
|
|
244 | Factor to multiply the \f(CW\*(C`min_latency\*(C'\fR (see \f(CW\*(C`dns\-overlap\-factor\*(C'\fR) by to |
|
|
245 | get request timeouts. The default of \f(CW8\fR means that the \s-1DNS\s0 transport |
|
|
246 | will resend the request when no reply has been received for longer than |
|
|
247 | eight times the minimum (= expected) latency, assuming the request or |
|
|
248 | reply has been lost. |
|
|
249 | .Sp |
|
|
250 | For congested links a higher value might be necessary (e.g. \f(CW30\fR). If the |
|
|
251 | link is very stable lower values (e.g. \f(CW2\fR) might work nicely. Values |
|
|
252 | near or below \f(CW1\fR makes no sense whatsoever. |
|
|
253 | .Sp |
|
|
254 | The default should be working ok for most links. |
| 207 | .IP "if-up = relative-or-absolute-path" 4 |
255 | .IP "if-up = relative-or-absolute-path" 4 |
| 208 | .IX Item "if-up = relative-or-absolute-path" |
256 | .IX Item "if-up = relative-or-absolute-path" |
| 209 | Sets the path of a script that should be called immediately after the |
257 | Sets the path of a script that should be called immediately after the |
| 210 | network interface is initialized (but not neccessarily up). The following |
258 | network interface is initialized (but not neccessarily up). The following |
| 211 | environment variables are passed to it (the values are just examples): |
259 | environment variables are passed to it (the values are just examples): |
