Quick Reference Guide

ProSafe VPN Firewall 200 FVX538 Reference Manual
Virtual Private Networking 5-5
v1.0, March 2009
• Both the remote WAN address and your local WAN address are required.
• The remote WAN IP address must be a public address or the Internet name of the remote
gateway. The Internet name is the Fully Qualified Domain Name (FQDN) as registered in
a Dynamic DNS service. Both local and remote endpoints should be defined as either
FQDN or IP addresses. A combination of IP address and FQDN is not allowed.
7. Enter the local LAN IP and Subnet Mask of the remote gateway in the Remote LAN IP
Address and Subnet Mask fields.
8. Click Apply to save your settings: the VPN Policies page shows the policy is now enabled.
9. If you are connecting to another NETGEAR VPN firewall, use the VPN Wizard to configure
the second VPN firewall to connect to the one you just configured.
Tip: To assure tunnels stay active, after completing the wizard, manually edit the
VPN policy to enable keepalive which periodically sends ping packets to
the host on the peer side of the network to keep the tunnel alive.
Tip: For DHCP WAN configurations, first, set up the tunnel with IP addresses.
Once you validate the connection, use the wizard to create new policies
using FQDN for the WAN addresses.
Note: The Remote LAN IP address must be in a different subnet than the Local 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.
Figure 5-5