Netgear DGFV338 DGFV338 Reference Manual - Page 114

Managing IKE Policies, IKE Policy Table, Auto Policy Parameters, Local ID, Remote ID

Get Netgear DGFV338 - ProSafe Wireless ADSL Modem VPN Firewall Router PDF manuals and user guides View all Netgear DGFV338 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 114 highlights

DGFV338 ProSafe Wireless ADSL Modem VPN Firewall Router Reference Manual 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".) 5-6 Virtual Private Networking v1.0, April 2007

  • 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
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 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”.)