Prestige 334W User’s Guide

 

 

 

Table 16-4 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 Prestige 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 Address field below.

16.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 16-5 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

 

 

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 E-mail. An “ID mismatched” message displays in the IPSEC LOG.

Table 16-6 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

 

 

VPN Screens

16-9