146
|
Appendix B.
NETGEAR VPN Configuration
N300 Wireless ADSL2+ Modem Router DGN2200
Modem Router with FQDN to Gateway B
This section is a case study on how to configure a VPN tunnel from a NETGEAR modem
router to a gateway using a fully qualified domain name (FQDN) to resolve the public address
of one or both routers. This case study follows the VPN Consortium interoperability profile
guidelines (found at
).
Configuration Profile
The configuration in this section follows the addressing and configuration mechanics defined
by the VPN Consortium. Gather the necessary information before you begin configuration.
Verify that the firmware is up to date, and that you have all the addresses and parameters to
be set on both sides. Check that there are no firewall restrictions.
Gateway A
WAN IP
Internet
10.506.0/24
(DGN2200)
LAN IP
10.5.6.1
example.org
WAN IP
example2.org
Gateway B
LAN IP
172.23.9.1
172.23.9.0/24
(FQDN)
(FQDN)
Figure 29. VPNC Example, Network Interface Addressing
Table 11.
VPN Consortium Scenario
Scenario 1
Type of VPN
LAN-to-LAN or gateway-to-gateway (not PC/client-to-gateway)
Security scheme:
IKE with preshared secret/Key (not certificate based)
IP addressing:
NETGEAR-Gateway A
Fully aualified domain name (FQDN)
NETGEAR-Gateway B
FDQN
Using a Fully Qualified Domain Name (FQDN)
Many ISPs provide connectivity to their customers using dynamic instead of static IP
addressing. This means that a user’s IP address does not remain constant over time, which
presents a challenge for gateways attempting to establish VPN connectivity.
A Dynamic DNS (DDNS) service allows a user whose public IP address is dynamically
assigned to be located by a host or domain name. It provides a central public database where
information (such as e-mail addresses, host names, and IP addresses) can be stored and