| … | |
… | |
| 158 | consistently on all hosts), but this is usually ineffective. |
158 | consistently on all hosts), but this is usually ineffective. |
| 159 | |
159 | |
| 160 | =item MAC=fe:fd:80:00:00:01 |
160 | =item MAC=fe:fd:80:00:00:01 |
| 161 | |
161 | |
| 162 | The MAC address to set the interface to. The script *must* set the |
162 | The MAC address to set the interface to. The script *must* set the |
| 163 | interface MAC to this value. On GNU/Linux you will most likely use this: |
163 | interface MAC to this value. You will most likely use one of these: |
| 164 | |
164 | |
| 165 | ip link set $IFNAME address $MAC mtu $MTU up |
165 | ip link set $IFNAME address $MAC mtu $MTU up # GNU/Linux |
|
|
166 | ifconfig $IFNAME ether $MAC mtu $MTU up # FreeBSD |
|
|
167 | |
|
|
168 | =item IFTYPE=native |
|
|
169 | |
|
|
170 | =item IFSUBTYPE=linux # or freebsd, darwin etc.. |
|
|
171 | |
|
|
172 | The interface type (C<native> or C<tincd>) and the subtype (usually the os |
|
|
173 | name in lowercase) that this vpe was configured for. Can be used to select |
|
|
174 | the correct syntax to use for network-related commands. |
| 166 | |
175 | |
| 167 | =item NODENAME=branch1 |
176 | =item NODENAME=branch1 |
| 168 | |
177 | |
| 169 | The nickname of the current node, as passed to the vped daemon. |
178 | The nickname of the current node, as passed to the vped daemon. |
| 170 | |
179 | |
| … | |
… | |
| 231 | |
240 | |
| 232 | =item node-down = relative-or-absolute-path |
241 | =item node-down = relative-or-absolute-path |
| 233 | |
242 | |
| 234 | Same as C<node-up>, but gets called whenever a connection is lost. |
243 | Same as C<node-up>, but gets called whenever a connection is lost. |
| 235 | |
244 | |
|
|
245 | =item http-proxy-host = hostname/ip |
|
|
246 | |
|
|
247 | The C<http-proxy-*> family of options are only available if vpe was |
|
|
248 | compiled with the C<--enable-http-proxy> option and enable tunneling of |
|
|
249 | tcp connections through a http proxy server. |
|
|
250 | |
|
|
251 | C<http-proxy-host> and C<http-proxy-port> should specify the hostname and |
|
|
252 | port number of the proxy server. See C<http-proxy-loginpw> if your proxy |
|
|
253 | requires authentication. |
|
|
254 | |
|
|
255 | Please note that vpe will still try to resolve all hostnames in the |
|
|
256 | configuration file, so if you are behind a proxy without access to a dns |
|
|
257 | server better use numerical IP addresses. |
|
|
258 | |
|
|
259 | To make best use of this option disable all protocols except tcp in your |
|
|
260 | config file and make sure your routers (or all other hosts) are listening |
|
|
261 | on a port that the proxy allows (443, https, is a common choice). |
|
|
262 | |
|
|
263 | If you have a router, connecting to it will suffice. Otherwise tcp must be |
|
|
264 | enabled on all hosts. |
|
|
265 | |
|
|
266 | Example: |
|
|
267 | |
|
|
268 | http-proxy-host = proxy.example.com |
|
|
269 | http-proxy-port = 3128 # 8080 is another common choice |
|
|
270 | http-proxy-auth = schmorp:grumbeere |
|
|
271 | |
|
|
272 | =item http-proxy-port = proxy-tcp-port |
|
|
273 | |
|
|
274 | The port where your proxy server listens. |
|
|
275 | |
|
|
276 | =item http-proxy-auth = login:password |
|
|
277 | |
|
|
278 | The optional login and password used to authenticate to the proxy server, |
|
|
279 | seperated by a literal colon (C<:>). Only basic authentication is |
|
|
280 | currently supported. |
|
|
281 | |
| 236 | =back |
282 | =back |
| 237 | |
283 | |
| 238 | =head2 NODE SPECIFIC SETTINGS |
284 | =head2 NODE SPECIFIC SETTINGS |
| 239 | |
285 | |
| 240 | The following settings are node-specific, that is, every node can have |
286 | The following settings are node-specific, that is, every node can have |
