Netgear FVS318G FVS318G User Manual - Page 102

Managing VPN Policies, The VPN Policies Tab the Local ID Endpoint and the Remote ID Endpoint. - ike could not find configuration for

Get Netgear FVS318G - ProSafe Gigabit VPN Firewall Data Sheet Router PDF manuals and user guides
UPC - 606449064827
View all Netgear FVS318G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 102 highlights

ProSafe Gigabit 8 Port VPN Firewall FVS318G Reference Manual • DH. The Diffie-Hellman (DH) group 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. Managing VPN Policies 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 Certificate Authority (CA) can also be used to perform authentication (see "Managing Certificates" on page 6-7). 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 by any sender to encrypt data intended for the receiver (the key owner). The receiver then uses its private key to decrypt the data (without the private key, decryption is impossible). The use of certificates for authentication reduces the amount of data entry required on each VPN endpoint. The VPN Policies Tab Page 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). 4. The remote VPN Endpoint must have a matching SA, or it will refuse the connection. Only one Client Policy may configured at a time (noted by an "*" next to the policy name). The Policy Table contains the following fields: 5-16 Virtual Private Networking Using IPsec 1.1 November, 2009

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
ProSafe Gigabit 8 Port VPN Firewall FVS318G Reference Manual
5-16
Virtual Private Networking Using IPsec
1.1 November, 2009
•
DH
. The Diffie-Hellman (DH) group 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.
Managing VPN Policies
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 Certificate Authority (CA) can also be used to perform authentication (see
“Managing Certificates” on page 6-7
). 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 by any sender to encrypt data intended for the receiver (the key
owner). The receiver then uses its private key to decrypt the data (without the private key,
decryption is impossible). The use of certificates for authentication reduces the amount of data
entry required on each VPN endpoint.
The VPN Policies Tab Page
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).
4.
The remote VPN Endpoint must have a matching SA, or it will refuse the connection.
Only one Client Policy may configured at a time (noted by an “*” next to the policy name). The
Policy Table contains the following fields: