NETGEAR FVS318N

Virtual Private Networking Using IPv4 IPSec and L2TP Connections
159
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 o
n page 215.
Tip: For DHCP W
AN 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.
3. Click App
ly to save your settings. The IPSec VPN policy is now added to the List of VPN
Policies table on the VPN Policies screen. By default, the VPN policy is enabled.
Figure 85.
4. Configure a VPN policy on the remote gateway that allows connection to the wireless VPN
firewall.
5. Activate
the IPSec VPN connection:
a. Select VPN >
Connection Status > IPSec VPN Connection Status. The IPSec VPN
Connection Status screen displays:
Secure Connection Remote Accessibility
What is the remote LAN IP
Address?
Enter the LAN IP address of the remote gateway.
Note: The remote LAN IP address needs to be in a different subnet than
the loca
l LAN IP address. For example, if the local subnet is 192.168.1.x,
then the remote subnet could be 192.168.10.x. but could not be
192.168.1.x. If this information is incorrect, the tunnel will fail to connect.
What is the remote LAN
Su
bnet Mask?
Enter the LAN subnet mask of 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 35. IPSec VPN Wizard settings for a gateway-to-gateway tunnel (continued)
Setting Description