Merge pull request #288 from ab7pa/tunweight
add tunnel weight description
This commit is contained in:
commit
0ea4dc1ee0
Binary file not shown.
Before Width: | Height: | Size: 113 KiB After Width: | Height: | Size: 62 KiB |
|
@ -542,6 +542,9 @@ Tunnel Server *maxclients* and Tunnel Client *maxservers*
|
||||||
|
|
||||||
Use caution when increasing the *maxclients* or *maxservers* values. Enter only *zero* or positive integers up to a maximum value for the number of active connections your node hardware can handle, since each active tunnel connection consumes system resources that the node may need for normal operation.
|
Use caution when increasing the *maxclients* or *maxservers* values. Enter only *zero* or positive integers up to a maximum value for the number of active connections your node hardware can handle, since each active tunnel connection consumes system resources that the node may need for normal operation.
|
||||||
|
|
||||||
|
Tunnel Weight
|
||||||
|
This specifies the OLSR route cost of using a tunnel, with the default value set to ``1``. The higher the route cost weight, the less likely a tunnel will be chosen for routing traffic.
|
||||||
|
|
||||||
Tunnel WAN Only Setting
|
Tunnel WAN Only Setting
|
||||||
This setting is enabled by default and it prevents tunnel traffic from being routed over the Mesh RF network. It limits tunnels to using the WAN interface, which is typically the intended route. If in your situation you need tunnel traffic to be routed over RF to a node with WAN access, then you can disable this setting to allow that traffic to pass.
|
This setting is enabled by default and it prevents tunnel traffic from being routed over the Mesh RF network. It limits tunnels to using the WAN interface, which is typically the intended route. If in your situation you need tunnel traffic to be routed over RF to a node with WAN access, then you can disable this setting to allow that traffic to pass.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue