260
VPN
Functionality
The information in this section applies only to setting up IPsec VPN tunnels, not L2TP/IPsec VPN
tunnels.
The IOLAN can be configured as a VPN gateway using the IPsec protocol. You can configure the
VPN connection using two IOLANs as the local and remote VPN gateways or the IOLAN as the
local VPN gateway and a host/server running the VPN software as the remote VPN gateway.
If the VPN tunnel is being configured for an IPv6 network that is going through a router(s), the
router(s) must have manual IPv6 address entry capability, similar to what Windows Vista
®
provides.
VPN servers/clients can support various VPN parameters. However, the following parameters are
REQUIRED to be set to the following values to support a VPN tunnel between the IOLAN and a
VPN server/client:
perfect forward secrecy: no
protocol: ESP
mode: tunnel (not transport)
opportunistic encryption: no
aggressive mode: no
IKE Phase 1 Proposals
The following IKE Phase 1 proposals are supported by the IOLAN VPN gateway:
z Ciphers—3DES, AES
z Hashes—MD5, SHA1
z Diffie-Hellman Groups—2 (MODP1024), 5 (MODP1536), 14 (MODP2048), 15 (MODP3072),
16 (MODP4096), 17 (MODP6144), 18 (MODP8192)
ESP Phase 2 Proposals
The following ESP Phase 2 proposals are supported by the IOLAN VPN gateway:
z Ciphers—3DES, AES
z Authentication Algorithms—MD5, SHA1, SHA2
IPsec
When an IPsec tunnel becomes active, you are requiring that all access to the IOLAN go through the
configured IPsec tunnel(s), so you must configure any exceptions first see (
Exceptions). for more
information on exceptions) or you will not be able to access the IOLAN through the network unless
you are configured to go through the IPsec tunnel (you can still access the IOLAN through the
Console port).
Field Descriptions
The following buttons are available:
To Next Page
Loading...
