| … | |
… | |
| 69 | |
69 | |
| 70 | =item dns-forw-port = port-number |
70 | =item dns-forw-port = port-number |
| 71 | |
71 | |
| 72 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
72 | The port where the C<dns-forw-host> is to be contacted (default: C<53>, |
| 73 | which is fine in most cases). |
73 | which is fine in most cases). |
|
|
74 | |
|
|
75 | =item dns-max-outstanding = integer-number-of-requests |
|
|
76 | |
|
|
77 | The maximum number of outstanding DNS transport requests |
|
|
78 | (default: C<100>). GVPE will never issue more requests then the given |
|
|
79 | 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 |
|
|
81 | number of parallel requests. |
|
|
82 | |
|
|
83 | The default should be working ok for most links. |
|
|
84 | |
|
|
85 | =item dns-overlap-factor = float |
|
|
86 | |
|
|
87 | 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>, |
|
|
89 | must be > 0) is multiplied by B<min_latency> to get the maximum sending |
|
|
90 | rate (= minimum send interval), i.e. a factor of C<1> means that a new |
|
|
91 | 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 |
|
|
93 | C<0.5> means that GVPE will send requests twice as often as the minimum |
|
|
94 | latency measured. |
|
|
95 | |
|
|
96 | For congested or picky dns forwarders you could use a value nearer to or |
|
|
97 | exceeding C<1>. |
|
|
98 | |
|
|
99 | The default should be working ok for most links. |
|
|
100 | |
|
|
101 | =item dns-send-interval = send-interval-in-seconds |
|
|
102 | |
|
|
103 | 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 |
|
|
105 | the latency is very low. The default is C<0.01>, which means GVPE will |
|
|
106 | 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 |
|
|
108 | congested or rate-limited links, you might want to go higher, say C<0.1>, |
|
|
109 | C<0.2> or even higher. |
|
|
110 | |
|
|
111 | The default should be working ok for most links. |
|
|
112 | |
|
|
113 | =item dns-timeout-factor = float |
|
|
114 | |
|
|
115 | 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 |
|
|
117 | will resend the request when no reply has been received for longer than |
|
|
118 | eight times the minimum (= expected) latency, assuming the request or |
|
|
119 | reply has been lost. |
|
|
120 | |
|
|
121 | For congested links a higher value might be necessary (e.g. C<30>). If the |
|
|
122 | link is very stable lower values (e.g. C<2>) might work nicely. Values |
|
|
123 | near or below C<1> makes no sense whatsoever. |
|
|
124 | |
|
|
125 | The default should be working ok for most links. |
| 74 | |
126 | |
| 75 | =item if-up = relative-or-absolute-path |
127 | =item if-up = relative-or-absolute-path |
| 76 | |
128 | |
| 77 | Sets the path of a script that should be called immediately after the |
129 | Sets the path of a script that should be called immediately after the |
| 78 | network interface is initialized (but not neccessarily up). The following |
130 | network interface is initialized (but not neccessarily up). The following |
