|Tunnels [main menu]|
|Lock to this Gateway||
If you want a wireless node to always connect to the same gateway node (in a multiple gateway environment), then set this to the 1.x.x.x address of the gateway. This is required in multiple-gateway camera or server hostmapping situations, because the mapping occurs using the virtual tunnel created between these 2 nodes.
This will prevent the auto discover feature from locking to the next available gateway (if the primary gateway fails this node will no longer be able to pass traffic to the Internet).
|Preferred Gateway(s)||If you want to specify a preference of gateways to use then adjust this in the order you want the system to try to make gateway connections. This is only used in multiple gateway systems.|
|Inter-Mesh Tunnel (Wormhole)||
If you want to connect two or more geographically-distant gateways together through their respective ethernet ports (usually over the internet) set this to Yes.
One gateway will be designated as the wormhole server and the remaining gateway(s) as wormhole clients. See next item for details.
|Server Public IP||If this node will be used as the wormhole server then you MUST leave this blank, otherwise put in the ethernet IP (public IP if applicable) of the remote wormhole server to which you want to have this gateway connect. The connection, when established, will appear as a 10.253.253.x address in the mesh node reporter, and on the main status page under the br5 interface. You should also be able to surf to the remote nodes just as if they were on your local network.|
|Security Key||This must be an alphanumeric password (at least one letter and one number) for the virtual tunnel system to work properly.|
Back to Top ++