Prestige 334 User’s Guide
Table 49 Peer ID Type and Content Fields
PEER ID TYPE | CONTENT |
|
|
Type an | |
| router. |
The domain name or
15.8.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 Prestiges in this example can complete negotiation and establish a VPN tunnel
Table 50 Matching ID Type and Content Configuration Example
PRESTIGE A | PRESTIGE B |
|
|
Local ID type: | Local ID type: IP |
|
|
Local ID content: tom@yourcompany.com | Local ID content: 1.1.1.2 |
|
|
Peer ID type: IP | Peer ID type: |
|
|
Peer ID content: 1.1.1.2 | Peer ID content: tom@yourcompany.com |
|
|
The two Prestiges in this example cannot complete their negotiation because Prestige B’s Local ID type is IP, but Prestige A’s Peer ID type is set to
Figure 63 Mismatching ID Type and Content Configuration Example
PRESTIGE A | PRESTIGE B |
|
|
Local ID type: IP | Local ID type: IP |
|
|
Local ID content: 1.1.1.10 | Local ID content: 1.1.1.10 |
|
|
Peer ID type: | Peer ID type: IP |
|
|
Peer ID content: aa@yahoo.com | Peer ID content: N/A |
|
|
15.9 Pre-Shared Key
A
163 | Chapter 15 VPN Screens |