Virtual Private Networking Using IPSec and L2TP Connections
202
ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N
Tip: To ensure that tunnels stay active, after completing the wizard, manually
edit the VPN policy to enable keep-alives, which periodically sends ping
packets to the host on the peer side of the network to keep the tunnel
alive. For more information, see Configure Keep-Alives on page 260.
Tip: For DHCP WAN configurations, first set up the tunnel with IP addresses.
After you have validated the connection, you can use the wizard to
create new policies using the FQDN for the WAN addresses.
4. Click Apply to save your settings. The IPSec VPN policy is now added to the List of VPN
Policies table on the VPN Policies screen for IPv6. By default, the VPN policy is enabled.
Figure 114.
5. Configure a VPN policy on the remote gateway that allows connection to the wireless VPN
firewall.
6. Activate the IPSec VPN connection:
a. Select VPN > Connection Status. The Connection Status submenu tabs display with
the IPSec VPN Connection Status screen in view:
Secure Connection Remote Accessibility
What is the remote LAN IP
Address? Enter the LAN IPv6 address of the remote gateway.
Note: The remote LAN IPv6 address needs to be different from the local
LAN IPv6 address. For example, if the local LAN IPv6 address is FEC0::1,
then the remote LAN IPv6 address could be FEC0:1::1 but could not be
FEC0::1. If this information is incorrect, the tunnel fails to connect.
IPv6 Prefix Length Enter the prefix length for the remote gateway.
a. Both local and remote endpoints should be defined as either FQDNs or IP addresses. A combination of
an IP address and an FQDN is not supported.
Table 43. IPSec VPN Wizard settings for an IPv6 gateway-to-gateway tunnel (continued)
Setting Description