Figure 207 Ike Sa: Main Negotiation Mode, Steps 5 - 6: Authentication; Table 100 Vpn Example: Matching Id Type And Content - ZyXEL Communications ZYWALL 35 User Manual

Figure 207 IKE SA: Main Negotiation Mode, Steps 5 - 6: Authentication

The ZyWALL and remote IPSec router use a pre-shared key in the authentication process,
though it is not actually transmitted or exchanged.
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 100 VPN Example: Matching ID Type and Content

ZYWALL
Local ID type: E-mail
Local ID content: tom@yourcompany.com
Peer ID type: IP
Peer ID content: 1.1.1.2
ZyWALL 5/35/70 Series User's Guide
Chapter 18 IPSec VPN
REMOTE IPSEC ROUTER
Local ID type: IP
Local ID content: 1.1.1.2
Peer ID type: E-mail
Peer ID content: tom@yourcompany.com
357