1. Home
    2. /
  2. Manuals
    3. /
  3. NETGEAR
    4. /
  4. FVG318
    5. /
  5. 34
Page 166 / 176 Scroll up to view Page 161 - 165
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
C-10
VPN Configuration of NETGEAR FVG318
v1.0, September 2007
The FVG318-to-FVL328 Case
Configuring the VPN Tunnel
This scenario assumes all ports are open on the FVG318 and FVL328.
Use this scenario illustration and configuration screens as a model to build your configuration.
1.
Log in to the FVG318 labeled Gateway A.
Log in at the default address of
with the default user name of
admin
and
default password of
password
(or using whatever password and LAN address you have
chosen).
2.
Use the VPN Wizard to configure the FVG318 at Gateway A.
•
Connection Name:
Scenario_1
(in this example)
Table C-3. Policy Summary
VPN Consortium Scenario:
Scenario 1
Type of VPN
LAN-to-LAN or Gateway-to-Gateway
Security Scheme:
IKE with Preshared Secret/Key
IP Addressing:
NETGEAR-Gateway A
Static IP address
NETGEAR-Gateway B
Static IP address
Figure C-5
Note:
Based on the network addresses used in this example, you would log in to the
LAN IP address of
at Gateway A.
FVG318
Page 167 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
VPN Configuration of NETGEAR FVG318
C-11
v1.0, September 2007
•
Pre-Shared Key:
12345678
(in this example), must be the same at both VPN tunnel
endpoints
•
Remote WAN IP address:
22.23.24.25
(in this example), must be unique at each VPN
tunnel endpoint
•
Remote LAN IP Subnet
–
IP Address:
172.23.9.1
(in this example), must be unique at each VPN tunnel endpoint
–
Subnet Mask:
255.255.255.0
(in this example)
3.
Log in to the FVL328 labeled Gateway B.
Log in at the default address of
with the default user name of
admin
and
default password of
password
(or using whatever password and LAN address you have
chosen).
4.
Repeat the process using the VPN Wizard to configure the FVL328 at Gateway B.
•
Connection Name:
Scenario_1
(in this example)
•
Pre-Shared Key:
12345678
(in this example), must be the same at both VPN tunnel
endpoints
•
Remote WAN IP address:
14.15.16.17
(in this example), must be unique at each VPN
tunnel endpoint
•
Remote LAN IP Subnet
–
IP Address:
10.5.6.1
(in this example), must be unique at each VPN tunnel endpoint
–
Subnet Mask:
255.255.255.0
(in this example)
All traffic from the range of LAN IP addresses specified on FVG318 A and FVL328 B will now
flow over a secure VPN tunnel once the VPN tunnel is initiated (see
“Initiating and Checking the
VPN Connections” on page C-12
).
Viewing and Editing the VPN Parameters
The VPN Wizard sets up a VPN tunnel using the default parameters from the VPN Consortium
(VPNC).
•
The Pre-Shared Key must be the same at both VPN tunnel endpoints.
Note:
Based on the network addresses used in this example, you would log in to the
LAN IP address of
at Gateway B.
Page 168 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
C-12
VPN Configuration of NETGEAR FVG318
v1.0, September 2007
•
The remote WAN and LAN IP addresses for one VPN tunnel endpoint will be the local WAN
and LAN IP addresses for the other VPN tunnel endpoint.
•
The VPN Wizard ensures the other VPN parameters are the same at both VPN tunnel
endpoints.
Initiating and Checking the VPN Connections
You can test connectivity and view VPN status information on the FVG318 and FVL328
according to the testing flowchart shown in
Figure C-2
. To test the VPN tunnel from the Gateway
A LAN, do the following:
1.
Test 1: Ping Remote LAN IP Address: To establish the connection between the FVG318
Gateway A and FVL328 Gateway B tunnel endpoints, perform these steps at Gateway A:
a.
From a Windows PC attached to the FVG318 on LAN A, click the
Start
button on the task
bar and then click
Run
.
b.
Type
ping -t 172.23.9.1
, and then click
OK
(you would type
ping -t 10.5.6.1
if testing
from Gateway B).
c.
This will cause a continuous ping to be sent to the LAN interface of Gateway B. Within
two minutes, the ping response should change from timed out to reply.
At this point the VPN-tunnel-endpoint-to-VPN-tunnel-endpoint connection is established.
2.
Test 2: Ping Remote WAN IP Address (if Test 1 fails): To test connectivity between the
Gateway A and Gateway B WAN ports, follow these steps:
a.
Log in to the router on LAN A, go to the main menu Maintenance section, and click the
Diagnostics
link.
b.
To test connectivity to the WAN port of Gateway B, enter
22.23.24.25
, and then click
Ping
(you would enter
14.15.16.17
if testing from Gateway B).
c.
This causes a ping to be sent to the WAN interface of Gateway B. Within two minutes, the
ping response should change from timed out to reply. You may have to run this test several
times before you get the reply message back from the target FVL328.
d.
At this point the gateway-to-gateway connection is verified.
3.
Test 3: View VPN Tunnel Status: To view the FVG318 and FVL328 event log and status of
Security Associations; go to the FVG318 main menu and select VPN > Connection Status. For
the FVL328, click VPN Status on the VPN Status/Log screen.
Page 169 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
VPN Configuration of NETGEAR FVG318
C-13
v1.0, September 2007
The FVG318-to-VPN Client Case
Client-to-Gateway VPN Tunnel Overview
The operational differences between gateway-to-gateway and client-to-gateway VPN tunnels are
summarized as follows:
Table C-4. Policy Summary
VPN Consortium Scenario:
Scenario 1
Type of VPN
PC/Client-to-Gateway
Security Scheme:
IKE with Preshared Secret/Key
Date Tested:
November 2004
IP Addressing:
NETGEAR-Gateway A
Static IP address
NETGEAR-Client B
Dynamic IP address
Table C-5. Differences between VPN tunnel types
Operation
Gateway-to-Gateway VPN Tunnels
Client-to-Gateway VPN Tunnels
Exchange Mode
Main Mode
—The IP addresses of both
gateways are known (especially when
FQDN is used), so each gateway can
use the Internet source of the traffic for
validation purposes.
Aggressive Mode
—The IP address of
the client is not known in advance, so the
gateway is programmed to accept valid
traffic sourced from any Internet location
(i.e., less secure).
Direction/Type
Both Directions
—Either end of the VPN
tunnel may initiate traffic (usually).
Remote Access
—The client end of the
VPN tunnel must initiate traffic because
its IP address is not know in advance,
which prevents the gateway end of the
VPN tunnel from initiating traffic.
Page 170 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
C-14
VPN Configuration of NETGEAR FVG318
v1.0, September 2007
Configuring the VPN Tunnel
This scenario assumes all ports are open on the FVG318.
Use this scenario illustration and configuration screens as a model to build your configuration.
1.
Log in to the FVG318 labeled Gateway A
Log in at the default address of
with the default user name of
admin
and
default password of
password
(or using whatever password and LAN address you have
chosen).
2.
Use the VPN Wizard to configure the FVG318 at Gateway A.:
•
Connection Name:
Scenario_1
(in this example)
•
Pre-Shared Key:
12345678
(in this example), must be the same at both VPN tunnel
endpoints
•
Connection Type:
A Remote VPN Client
3.
Set up the VPN Client at Gateway B.
a.
Right-mouse-click the ProSafe icon (
) in the system tray and select the Security Policy
Editor. If you need to install the NETGEAR ProSafe VPN Client on your PC, consult the
documentation that came with your software.
Figure C-6
Note:
Based on the network addresses used in this example, you would log in to the
LAN IP address of
at Gateway A

Rate

4 / 5 based on 1 vote.

Popular NETGEAR Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

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

Share
Top