Netgear FVS338 FVS338 Reference Manual - Page 99

VPN Policies, Local ID, Remote ID, Enable Dead Peer Detection, Manual

Page 99 highlights

FVS338 ProSafe VPN Firewall 50 Reference Manual • 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. If the Policy is a Client Policy, it will be prepended by an "*". • Mode. Two modes are available: either "Main" or "Aggressive". - Main Mode is slower but more secure. - Aggressive mode is faster but less secure. (If specifying either a FQDN or a User FQDN name as the Local ID/Remote ID, aggressive mode is automatically selected.) • 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".) • 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.) • Enable Dead Peer Detection: Dead Peer Detection is used to detect whether the peer is alive or not. If the peer is detected as dead, the IPSec and IKE Security Association are deleted. To gain a more complete understanding of the encryption, authentication and DH algorithm technologies, see Appendix C, "Related Documents". 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). Virtual Private Networking 5-5 v1.0, March 2008

  • 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
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198

FVS338 ProSafe VPN Firewall 50 Reference Manual
Virtual Private Networking
5-5
v1.0, March 2008
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. If the Policy is
a Client Policy, it will be prepended by an “*”.
Mode
. Two modes are available: either “Main” or “Aggressive”.
Main Mode is slower but more secure.
Aggressive mode is faster but less secure. (If specifying either a FQDN or a User FQDN
name as the Local ID/Remote ID, aggressive mode is automatically selected.)
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”.)
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.)
Enable Dead Peer Detection
: Dead Peer Detection is used to detect whether the peer is alive
or not. If the peer is detected as dead, the IPSec and IKE Security Association are deleted.
To gain a more complete understanding of the encryption, authentication and DH algorithm
technologies, see
Appendix C, “Related Documents”
.
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).