Netgear SRXN3205 SRXN3205 Reference Manual - Page 114

About IKE, Managing IKE Policies, Auto Policy Parameters

Page 114 highlights

ProSafe Wireless-N VPN Firewall SRXN3205 Reference Manual 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. Note: An IKE policy cannot be edited if it is associated with an enabled VPN policy. About IKE 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 the: • "Auto" generated VPN policies must use the IKE negotiation protocol. • "Manual" generated VPN policies cannot use the IKE negotiation protocol. Managing IKE Policies IKE Policies are activated when the following occur: 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. 6-12 Virtual Private Networking Using IPsec v1.0, October 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
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

ProSafe Wireless-N VPN Firewall SRXN3205 Reference Manual
6-12
Virtual Private Networking Using IPsec
v1.0, October 2008
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.
About IKE
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 the:
“Auto” generated VPN policies must use the IKE negotiation protocol.
“Manual” generated VPN policies cannot use the IKE negotiation protocol.
Managing IKE Policies
IKE Policies are activated when the following occur:
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.
Note:
An IKE policy cannot be edited if it is associated with an enabled VPN policy.