Prestige 334 User’s Guide
163
Chapter 15 VPN Screens
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
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
. An “ID mismatched”
message displays in the IPSEC LOG.
15.9 Pre-Shared Key
A pre-shared key identifies a communicating party during a phase 1 IKE negotiation (see
for more on IKE phases). It is called “pre-shared” because you have to
share it with another party before you can communicate with them over a secure connection.
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 Address
field below.
Table 49
Peer ID Type and Content Fields
PEER ID TYPE CONTENT
Table 50
Matching ID Type and Content Configuration Example
PRESTIGE A
PRESTIGE B
Local ID type: E-mail
Local ID type: IP
Local ID content: tom@yourcompany.com
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: tom@yourcompany.com
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: E-mail
Peer ID type: IP
Peer ID content: aa@yahoo.com
Peer ID content: N/A