G
ATEWAY
C
ONTROLLER
S
ERIES
U
SER
M
ANUAL
VALUEPOINT NETWORKS, INC. ALL RIGHTS RESERVED
P
AGE
89
OF
135
configuration. You must build the advanced functionality you want into your server
at the other end of the tunnel.
Walled garden, DNS, and IP pass-through traffic will not be routed through the tunnel,
and all normal security, redirection, and authentication features will still be in effect
as configured in the Controller. Once authenticated, subscriber traffic goes into the
tunnel.
For more information on GRE, see the Linux man pages for “ip tunnel” or the
wikipedia.org entry for Generic Routing Encapsulation.
Local Tunnel IP Address
The LAN IP Address of the Controller side of the
tunnel
Local Tunnel Subnet Mask
The LAN subnet of the Controller side of the tunnel
Remote Tunnel IP Address
The LAN IP Address of the remote side of the tunnel
GRE Peer IP Address
The WAN IP of the remote router hosting the tunnel
VPN IPSec Tunnels
You can configure up to 10 VPN IPSec tunnels to other VPN gateways. The Controller
does not support termination of VPN client connections, these connections must pass
through to a terminator. To create a tunnel you must map a local secure network to
a remote secure network. These settings, and in general all settings, must match
between the two gateways or the connection will not be made.
Tunnel Network Configuration
Select Tunnel
Select the tunnel you want to edit. You must click OK to
saves changes and restart.
Tunnel
Enable
or
Disable
each tunnel here.