1. Home
    2. /
  2. Manuals
    3. /
  3. NETGEAR
    4. /
  4. FVG318
    5. /
  5. 33
Page 161 / 176 Scroll up to view Page 156 - 160
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
VPN Configuration of NETGEAR FVG318
C-5
v1.0, September 2007
–
Subnet Mask:
255.255.255.0
(in this example)
3.
Log in to the FVG318 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 FVG318 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 FVG318 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-6
).
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.
•
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.
Note:
Based on the network addresses used in this example, you would log in to the
LAN IP address of
at Gateway B
Page 162 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
C-6
VPN Configuration of NETGEAR FVG318
v1.0, September 2007
Initiating and Checking the VPN Connections
You can test connectivity and view VPN status information on the FVG318 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 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 FVG318.
d.
At this point the gateway-to-gateway connection is verified.
3.
Test 3: View VPN Tunnel Status: To view the FVG318 event log and status of Security
Associations, follow these steps:
a.
Go to the FVG318 main menu VPN section and click the
VPN Status
link.
b.
The log screen displays a history of the VPN connections, and the IPSec SA and IKE SA
tables report the status and data transmission statistics of the VPN tunnels for each policy.
Page 163 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
VPN Configuration of NETGEAR FVG318
C-7
v1.0, September 2007
The FVG318-to-FVS318v2 Case
Configuring the VPN Tunnel
This scenario assumes all ports are open on the FVG318 and FVS318v2.
Use this scenario illustration and configuration screens as a model to build your configuration.
1.
Log in to the FVG318 labeled Gateway A as in the illustration (
Figure C-4
).
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.
Table C-2. Policy Summary
VPN Consortium Scenario:
Scenario 1
Type of VPN
LAN-to-LAN or Gateway-to-Gateway
Security Scheme:
IKE with Preshared Secret/Key
Date Tested:
November 2004
IP Addressing:
NETGEAR-Gateway A
Static IP address
NETGEAR-Gateway B
Static IP address
Figure C-4
Note:
Based on the network addresses used in this example, you would log in to the
LAN IP address of
at Gateway A.
Note:
FVG318
FVG318
Page 164 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
C-8
VPN Configuration of NETGEAR FVG318
v1.0, September 2007
•
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:
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 FVS318v2 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 FVS318v2 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 FVG318 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-9
).
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 165 / 176
ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
VPN Configuration of NETGEAR FVG318
C-9
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 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 FVS318v2 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 FVS318v2.
d.
At this point the gateway-to-gateway connection is verified.
3.
Test 3: View VPN Tunnel Status: To view the FVG318 VPN event logs, go to Monitoring >
VPN Logs; to view the status of Security Associations, go to the FVG318 VPN > Connection
Status. For the FVS318v2, click Show VPN Status from the Router Status screen.

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