Page 111 / 212 Scroll up to view Page 106 - 110
DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual
Virtual Private Networking
5-3
v1.0, April 2007
7.
Enter the
Remote LAN IP Address and Subnet Mask
of the remote gateway.
The information entered here must match the Local LAN IP and Subnet Mask of the remote
gateway; otherwise the secure tunnel will fail to connect.The IP address range used on the
remote LAN must be different from the IP address range used on the local LAN.
8.
Click the
VPN Wizard Default Values
link at the top right of the screen to view the
recommended VPNC parameters (see
Figure 5-1
).
9.
Click
Apply
to save your settings. The
VPN Policies
screen will display showing the policy
“Offsite” as enabled. Click
Edit
in the
Action
column adjacent to the policy to confirm your
policy settings.
Figure 5-1
Page 112 / 212
DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual
5-4
Virtual Private Networking
v1.0, April 2007
You can also view the status of your IKE Policies by clicking the
IKE Policies
tab. The
IKE
Policies screen
will display. Then view or edit the parameters of the “Offsite” policy by
clicking
Edit
in the
Action
column adjacent to the policy. The
Edit IKE Policy
screen will
display.
Figure 5-2
Page 113 / 212
DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual
Virtual Private Networking
5-5
v1.0, April 2007
VPN Tunnel Policies
When you use the VPN Wizard to set up a VPN tunnel, both a VPN Policy and an IKE Policy are
established and populated in both Policy Tables. The name you selected as the VPN Tunnel
connection name during Wizard setup identifies both the VPN Policy and IKE Policy. You can edit
existing policies, or add new VPN and IKE policies directly in the Policy Tables.
IKE Policy
The IKE (Internet Key Exchange) protocol performs negotiations between the two VPN
Gateways, and provides automatic management of the Keys used in IPSec. It is important to
remember that:
“Auto” generated VPN policies must use the IKE negotiation protocol.
“Manual” generated VPN policies cannot use the IKE negotiation protocol.
Figure 5-3
Page 114 / 212
DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual
5-6
Virtual Private Networking
v1.0, April 2007
Managing IKE Policies
IKE Policies are activated when:
1.
The VPN Policy Selector determines that some traffic matches an existing VPN Policy. If the
VPN policy is of type “Auto”, then the
Auto Policy Parameters
defined in the VPN Policy
are accessed which specify which IKE Policy to use.
2.
If the VPN Policy is a “Manual” policy, then the
Manual Policy Parameters
defined in the
VPN Policy are accessed and the first matching IKE Policy is used to start negotiations with
the remote VPN Gateway.
If negotiations fail, the next matching IKE Policy is used.
If none of the matching IKE Policies are acceptable to the remote VPN Gateway, then a
VPN tunnel cannot be established.
3.
An IKE session is established, using the SA (Security Association) parameters specified in a
matching IKE Policy:
Keys and other parameters are exchanged.
An IPSec SA (Security Association) is established, using the parameters in the VPN
Policy.
The VPN tunnel is then available for data transfer.
IKE Policy Table
When you use the VPN Wizard to set up a VPN tunnel, an IKE Policy is established and populated
in the Policy Table and is given the same name as the new VPN connection name. You can also
edit exiting policies or add new IKE policies directly on the Policy Table Screen. Each policy
contains the following data:
Name
. Uniquely identifies each IKE policy. The name is chosen by you and used for the
purpose of managing your policies; it is not supplied to the remote VPN Server.
Mode
. Two modes are available: either “Main” or “Aggressive”.
Main Mode is slower but more secure.
Aggressive mode is faster but less secure.
Local ID
. The IKE/ISAKMP identify of this device. (The remote VPN must have this value as
their “Remote ID”.)
Remote ID
. The IKE/ISAKMP identify of the remote VPN Gateway. (The remote VPN must
have this value as their “Local ID”.)
Page 115 / 212
DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual
Virtual Private Networking
5-7
v1.0, April 2007
Encr
. Encryption Algorithm used for the IKE SA. The default setting using the VPN Wizard is
3DES. (This setting must match the Remote VPN.)
Auth
. Authentication Algorithm used for the IKE SA. The default setting using the VPN
Wizard is SHA1. (This setting must match the Remote VPN.)
DH
. Diffie-Hellman Group. The Diffie-Hellman algorithm is used when exchanging keys. The
DH Group sets the number of bits. The VPN Wizard default setting is Group 2. (This setting
must match the Remote VPN.)
To gain a more complete understanding of the encryption, authentication and DH algorithm
technologies, see
Appendix B, “Related Documents”
for a link to the NETGEAR website.
VPN Policy
You can create two types of VPN Policies. When using the VPN Wizard to create a VPN policy,
only the Auto method is available.
Manual
. All settings (including the keys) for the VPN tunnel are manually input at each end
(both VPN Endpoints). No third party server or organization is involved.
Auto
. Some parameters for the VPN tunnel are generated automatically by using the IKE
(Internet Key Exchange) protocol to perform negotiations between the two VPN Endpoints
(the Local ID Endpoint and the Remote ID Endpoint).
In addition, a CA (Certificate Authority) can also be used to perform authentication (see
“Certificate Authorities” on page 5-22
). To use a CA, each VPN Gateway must have a Certificate
from the CA. For each Certificate, there is both a “Public Key” and a “Private Key”. The “Public
Key” is freely distributed, and is used to encrypt data. The receiver then uses their “Private Key” to
decrypt the data (without the Private Key, decryption is impossible). CAs can be beneficial since
using them reduces the amount of data entry required on each VPN Endpoint.
Managing VPN Policies
The VPN Policies screen allows you to add additional policies—either Auto or Manual—and to
manage the VPN policies already created. You can edit policies, enable or disable policies, or
delete them entirely. The rules for VPN policy use are:
1.
Traffic covered by a policy will automatically be sent via a VPN tunnel.
2.
When traffic is covered by two or more policies, the first matching policy will be used. (In this
situation, the order of the policies is important. However, if you have only one policy for each
remote VPN Endpoint, then the policy order is not important.)
3.
The VPN tunnel is created according to the parameters in the SA (Security Association).

Rate

4 / 5 based on 1 vote.

Bookmark Our Site

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

Share
Top