Chapter 14 IPSec VPN

"The ZyWALL and the remote IPSec router must use the same pre-shared key.

Router identity consists of ID type and ID content. The ID type can be IP address, domain name, or e-mail address, and the ID content is a specific IP address, domain name, or e-mail address. The ID content is only used for identification; the IP address, domain name, or e-mail address that you enter does not have to actually exist.

The ZyWALL and the remote IPSec router each has its own identity, so each one must store two sets of information, one for itself and one for the other router. Local ID type and ID content refers to the ID type and ID content that applies to the router itself, and peer ID type and ID content refers to the ID type and ID content that applies to the other router in the IKE SA.

"The ZyWALL’s local and peer ID type and ID content must match the remote IPSec router’s peer and local ID type and ID content, respectively.

In the following example, the ID type and content match so the ZyWALL and the remote IPSec router authenticate each other successfully.

Table 65 VPN Example: Matching ID Type and Content

ZYWALL

REMOTE IPSEC ROUTER

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

 

 

In the following example, the ID type and content do not match so the authentication fails and the ZyWALL and the remote IPSec router cannot establish an IKE SA.

Table 66 VPN Example: Mismatching ID Type and Content

ZYWALL

REMOTE IPSEC ROUTER

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.15

Peer ID content: tom@yourcompany.com

 

 

It is also possible to configure the ZyWALL to ignore the identity of the remote IPSec router. In this case, you usually set the peer ID type to Any. This is not as secure as other peer ID types, however.

14.3.1.2.1Certificates

It is also possible for the ZyWALL and remote IPSec router to authenticate each other with certificates. In this case, the authentication process is different.

 

259

ZyWALL 2 Plus User’s Guide