Page 271 / 296 Scroll up to view Page 266 - 270
NETGEAR VPN Configuration FVS318 or FVM318 with FQDN to FVS328
H-1
201-10301-02, May 2005
Appendix H
NETGEAR VPN Configuration
FVS318 or FVM318 with FQDN to FVS328
This appendix provides a case study on how to configure a VPN tunnel between a NETGEAR
FVS318 or FVM318 to a FWG114P v2 using a Fully Qualified Domain Name (FQDN) to resolve
the public address of one or both routers. The configurations screens and settings for the FVS318
and FVM318 are the same.
Configuration Template
The configuration in this document follows the addressing and configuration mechanics defined
by the VPN Consortium. Gather all the necessary information before you begin the configuration
process. Verify whether the firmware is up to date, all of the addresses that will be necessary, and
all of the parameters that need to be set on both sides. Check that there are no firewall restrictions.
Table H-1.
Summary
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)
Date Tested:
December 2003
Model/Firmware Tested:
NETGEAR-Gateway A
FVS318 firmware version A1.4 or 2.0; FVM318 firmware version 1.1
NETGEAR-Gateway B
FVS328 with firmware version 1.0 Release 00
IP Addressing:
NETGEAR-Gateway A
Fully Qualified Domain Name (FQDN)
NETGEAR-Gateway B
Static IP address
Page 272 / 296
Reference Manual for the ProSafe Wireless 802.11g
Firewall/Print Server Model FWG114P v2
H-2
NETGEAR VPN Configuration FVS318 or FVM318 with FQDN to FVS328
201-10301-02, May 2005
Figure H-1:
Addressing and Subnet Used for Examples
Using DDNS and Fully Qualified Domain Names (FQDN)
Many ISPs (Internet Service Providers) 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 retrieved. Now, a
gateway can be configured to use a 3
rd
party service in lieu of a permanent and unchanging IP
address to establish bi-directional VPN connectivity.
To use DDNS, you must register with a DDNS service provider. Example DDNS Service
Providers include:
Table H-1.
Example DDNS Service Providers
In this example, Gateway A is configured using an example FQDN provided by a DDNS Service
provider. In this case we established the hostname
netgear.dyndns.org
for Gateway A using the
DynDNS
www.dyndns.org
TZO.com
netgear.tzo.com
ngDDNS
ngddns.iego.net
Gateway A
22.23.24.25
FQDN
netgear.dydns.org
10.5.6.0/24
172.23.9.0/24
172.23.9.1
10.5.6.1
WAN IP
WAN IP
LAN IP
LAN IP
Gateway B
VPNC Example
Network Interface Addressing
Page 273 / 296
Reference Manual for the ProSafe Wireless 802.11g
Firewall/Print Server Model FWG114P v2
NETGEAR VPN Configuration FVS318 or FVM318 with FQDN to FVS328
H-3
201-10301-02, May 2005
DynDNS service. Gateway B will use the DDNS Service Provider when establishing a VPN
tunnel.
In order to establish VPN connectivity Gateway A must be configured to use Dynamic DNS, and
Gateway B must be configured to use a DNS hostname to find Gateway A provided by a DDNS
Service Provider. Again, the following step-by-step procedures assume that you have already
registered with a DDNS Service Provider and have the configuration information necessary to set
up the gateways.
Step-By-Step Configuration of FVS318 or FVM318 Gateway A
1.
Log in to the FVS318 or FVM318 labeled Gateway A as in the illustration.
Out of the box, the FVS318 or FVM318 is set for its default LAN address of
with its default user name of
admin
and default password of
password
.
For this example we will assume you have set the local LAN address as 10.5.6.1 for Gateway
A and have set your own password.
2.
Click
Dynamic DNS
on the left side of the Settings management GUI.
3.
Access the Web site of one of the dynamic DNS service providers whose names appear in the
‘Use a dynamic DNS service’ list, and register for an account.
For example, for dyndns.org, click the link or go to www.dyndns.org.
Figure H-2:
Dynamic DNS Setup menu
Page 274 / 296
Reference Manual for the ProSafe Wireless 802.11g
Firewall/Print Server Model FWG114P v2
H-4
NETGEAR VPN Configuration FVS318 or FVM318 with FQDN to FVS328
201-10301-02, May 2005
4.
Select the
Use a dynamic DNS service
radio button for the service you are using. In this
example we are using www.DynDNS.org as the service provider.
Type the Host Name that your dynamic DNS service provider gave you.
The dynamic DNS service provider may call this the domain name. In this example we are
using dyndns.org as the domain suffix.
Type the User Name for your dynamic DNS account. In this example we used netgear as
the Host Name. This means that the complete FQDN we are using is netgear.dyndns.org
and the Host Name is “netgear.”
Type the Password (or key) for your dynamic DNS account.
5.
Click
Apply
to save your configuration.
6.
Click
VPN Settings
on the left side of the Settings management GUI.
Figure H-3:
NETGEAR FVS318 VPN Settings Pre-Configuration
7.
Click the radio button of first available VPN leg (all 8 links are available in the example).
Click
Edit
. This will take you to the VPN Settings – Main Mode Menu.
Note:
The router supports only basic DDNS and the login and password may not be
secure. If your ISP assigns a private WAN IP address, such as 192.168.x.x or 10.x.x.x,
the dynamic DNS service will not work because private addresses will not be routed on
the Internet.
Page 275 / 296
Reference Manual for the ProSafe Wireless 802.11g
Firewall/Print Server Model FWG114P v2
NETGEAR VPN Configuration FVS318 or FVM318 with FQDN to FVS328
H-5
201-10301-02, May 2005
Figure H-4:
NETGEAR FVS318 VPN Settings (part 1) – Main Mode
In the Connection Name box, enter in a unique name for the VPN tunnel to be configured
between the NETGEAR devices. For this example we have used
toFVS328
.
Enter a Local IPSec Identifier
name for the NETGEAR FVS318 Gateway A. This name
must be entered in the other endpoint as Remote IPSec Identifier. In this example we used
netgear.dyndns.org
(the FQDN) as the local identifier.
Enter a Remote IPSec Identifier
name for the remote NETGEAR FVS328 Gateway B.
This name must be entered in the other endpoint as Local IPSec Identifier. In this example
we used
22.23.24.25
as the remote identifier.
Choose a subnet from local address from the “Tunnel can be accessed” from pull-down
menu.
Type the starting LAN IP Address of Gateway A (
10.5.6.1
in our example) in the Local IP
Local LAN start IP Address field.
Type the finishing LAN IP Address of Gateway A (
0.0.0.0
in our example) in the Local IP
Local LAN finish IP Address field.
Type the LAN Subnet Mask of Gateway A (
255.255.255.0
in our example) in the
Local
LAN IP Subnetmask field.
Choose a subnet from local address from the “Tunnel can access”
pull-down menu.
Type the starting LAN IP Address of Gateway B (
172.23.9.1
in our example) in the Local
IP Remote LAN Start IP Address field.

Rate

4 / 5 based on 1 vote.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top