1. Home
    2. /
  2. Manuals
    3. /
  3. NETGEAR
    4. /
  4. FVL328
    5. /
  5. 37
Page 181 / 234 Scroll up to view Page 176 - 180
Model FVL328 ProSafe High-Speed VPN Firewall Reference Manual Revision 2
Virtual Private Networking
E-11
May 2004, 202-10030-02
VPNC IKE Phase II Parameters
The IKE Phase 2 parameters used in Scenario 1 are:
•
TripleDES
•
SHA-1
•
ESP tunnel mode
•
MODP group 1
•
Perfect forward secrecy for rekeying
•
SA lifetime of 28800 seconds (one hour)
Testing and Troubleshooting
Once you have completed the VPN configuration steps you can use PCs, located behind each of
the gateways, to ping various addresses on the LAN side of the other gateway.
You can troubleshoot connections using the VPN status and log details on the NETGEAR gateway
to determine if IKE negotiation is working. Common problems encountered in setting up VPNs
include:
•
Parameters may be configured differently on Gateway A vs. Gateway B.
•
Two LANs set up with similar or overlapping addressing schemes.
•
So many required configuration parameters mean errors such as mistyped information or
mismatched parameter selections on either side are more likely to happen.
Additional Reading
•
Building and Managing Virtual Private Networks
, Dave Kosiur, Wiley & Sons; ISBN:
0471295264
•
Firewalls and Internet Security: Repelling the Wily Hacker
, William R. Cheswick and Steven
M. Bellovin, Addison-Wesley; ISBN: 0201633574
•
VPNs A Beginners Guide
, John Mains, McGraw Hill; ISBN: 0072191813
•
[FF98] Floyd, S., and Fall, K., Promoting the Use of End-to-End Congestion Control in the
Internet. IEEE/ACM Transactions on Networking, August 1999.
Relevant RFCs listed numerically:
Page 182 / 234
Model FVL328 ProSafe High-Speed VPN Firewall Reference Manual Revision 2
E-12
Virtual Private Networking
May 2004, 202-10030-02
•
[RFC 791]
Internet Protocol DARPA Internet Program Protocol Specification
, Information
Sciences Institute, USC, September 1981.
•
[RFC 1058]
Routing Information Protocol
, C Hedrick, Rutgers University, June 1988.
•
[RFC 1483]
Multiprotocol Encapsulation over ATM Adaptation Layer 5
, Juha Heinanen,
Telecom Finland, July 1993.
•
[RFC 2401] S. Kent, R. Atkinson, Security Architecture for the Internet Protocol
, RFC 2401,
November 1998.
•
[RFC 2407] D. Piper, The Internet IP Security Domain of Interpretation for ISAKMP
,
November 1998.
•
[RFC 2474] K. Nichols, S. Blake, F. Baker, D. Black, Definition of the Differentiated Services
Field (DS Field) in the IPv4 and IPv6 Headers
, December 1998.
•
[RFC 2475] S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, and W. Weiss, An
Architecture for Differentiated Services
, December 1998.
•
[RFC 2481] K. Ramakrishnan, S. Floyd, A Proposal to Add Explicit Congestion Notification
(ECN) to IP
, January 1999.
•
[RFC 2408] D. Maughan, M. Schertler, M. Schneider, J. Turner, Internet Security Association
and Key Management Protocol (ISAKMP)
.
•
[RFC 2409] D. Harkins, D.Carrel, Internet Key Exchange
(IKE) protocol.
•
[RFC 2401] S. Kent, R. Atkinson, Security Architecture for the Internet Protocol
.
Page 183 / 234
NETGEAR VPN Configuration FVS318 or FVM318 to FVL328
F-1
May 2004, 202-10030-02
Appendix F
NETGEAR VPN Configuration
FVS318 or FVM318 to FVL328
This appendix provides a case study on how to configure a secure IPSec VPN tunnel between a
NETGEAR FVS318 or FVM318 to a FVL328. The configuration options and screens 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 F-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 FVM318 firmware version 1.1
NETGEAR-Gateway B
FVL328 with firmware version 1.5 Release 07
IP Addressing:
NETGEAR-Gateway A
Static IP address
NETGEAR-Gateway B
Static IP address
Page 184 / 234
Model FVL328 ProSafe High-Speed VPN Firewall Reference Manual Revision 2
F-2
NETGEAR VPN Configuration FVS318 or FVM318 to FVL328
May 2004, 202-10030-02
Figure F-1:
Addressing and Subnet Used for Examples
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.
Figure F-2:
NETGEAR FVS318 VPN Settings Pre-Configuration
Gateway A
22.23.24.25
14.15.16.17
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 185 / 234
Model FVL328 ProSafe High-Speed VPN Firewall Reference Manual Revision 2
NETGEAR VPN Configuration FVS318 or FVM318 to FVL328
F-3
May 2004, 202-10030-02
2.
Click the VPN Settings link on the left side of the Settings management GUI. Click the radio
button of first available VPN leg (all 8 links are available in the example). Click the Edit
button below. This will take you to the VPN Settings – Main Mode Menu.
Figure F-3:
Figure 3 – 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
toFVL328
.
–
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
14.15.16.17
as the local identifier.
–
Enter a Remote IPSec Identifier
name for the remote NETGEAR FVL328 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.

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