ZyXEL P-202H User Guide - Page 122

ID Type and Content Examples

Page 122 highlights

P-202H Plus v2 User's Guide Table 34 Local ID Type and Content Fields LOCAL ID TYPE CONTENT E-mail Type an e-mail address (up to 31 characters) by which to identify this ZyXEL Device. The domain name or e-mail address that you use in the Content field is used for identification purposes only and does not need to be a real domain name or e-mail address. Table 35 Peer ID Type and Content Fields PEER ID TYPE CONTENT IP Type the IP address of the computer with which you will make the VPN connection or leave the field blank to have the ZyXEL Device automatically use the address in the Secure Gateway Address field. DNS Type a domain name (up to 31 characters) by which to identify the remote IPSec router. E-mail Type an e-mail address (up to 31 characters) by which to identify the remote IPSec router. The domain name or e-mail address that you use in the Content field is used for identification purposes only and does not need to be a real domain name or e-mail address. The domain name also does not have to match the remote router's IP address or what you configure in the Secure Gateway IP Address field below. 11.7.1 ID Type and Content Examples Two IPSec routers must have matching ID type and content configuration in order to set up a VPN tunnel. The two ZyXEL Devices in this example can complete negotiation and establish a VPN tunnel Table 36 Matching ID Type and Content Configuration Example ZYXEL DEVICE A Local ID type: E-mail Local ID content: [email protected] Peer ID type: IP Peer ID content: 1.1.1.2 ZYXEL DEVICE B Local ID type: IP Local ID content: 1.1.1.2 Peer ID type: E-mail Peer ID content: [email protected] The two ZyXEL Devices in this example cannot complete their negotiation because ZyXEL Device B's Local ID type is IP, but ZyXEL Device A's Peer ID type is set to E-mail. An "ID mismatched" message displays in the IPSEC LOG. Figure 51 Mismatching ID Type and Content Configuration Example ZYXEL DEVICE A Local ID type: IP Local ID content: 1.1.1.10 ZYXEL DEVICE B Local ID type: IP Local ID content: 1.1.1.10 121 Chapter 11 VPN Screens

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375

P-202H Plus v2 User’s Guide
121
Chapter 11 VPN Screens
11.7.1
ID Type and Content Examples
Two IPSec routers must have matching ID type and content configuration in order to set up a
VPN tunnel.
The two ZyXEL Devices in this example can complete negotiation and establish a VPN tunnel
The two ZyXEL Devices in this example cannot complete their negotiation because ZyXEL
Device
B
’s
Local ID type
is
IP
, but ZyXEL Device
A
’s
Peer ID type
is set to
E-mail
. An “ID
mismatched” message displays in the IPSEC LOG.
E-mail
Type an e-mail address (up to 31 characters) by which to identify this ZyXEL
Device.
The domain name or e-mail address that you use in the
Content
field is used for identification purposes
only and does not need to be a real domain name or e-mail address.
Table 35
Peer ID Type and Content Fields
PEER ID TYPE
CONTENT
IP
Type the IP address of the computer with which you will make the VPN connection or
leave the field blank to have the ZyXEL Device automatically use the address in the
Secure Gateway Address
field.
DNS
Type a domain name (up to 31 characters) by which to identify the remote IPSec
router.
E-mail
Type an e-mail address (up to 31 characters) by which to identify the remote IPSec
router.
The domain name or e-mail address that you use in the
Content
field is used for identification purposes
only and does not need to be a real domain name or e-mail address. The domain name also does not
have to match the remote router’s IP address or what you configure in the
Secure Gateway IP
Address
field below.
Table 34
Local ID Type and Content Fields
LOCAL ID TYPE
CONTENT
Table 36
Matching ID Type and Content Configuration Example
ZYXEL DEVICE A
ZYXEL DEVICE B
Local ID type: E-mail
Local ID type: IP
Local ID content: [email protected]
Local ID content: 1.1.1.2
Peer ID type: IP
Peer ID type: E-mail
Peer ID content: 1.1.1.2
Peer ID content: [email protected]
Figure 51
Mismatching ID Type and Content Configuration Example
ZYXEL DEVICE A
ZYXEL DEVICE B
Local ID type: IP
Local ID type: IP
Local ID content: 1.1.1.10
Local ID content: 1.1.1.10