LOCAL ID TYPE=
IP
DNS
E-mail
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 Addr field
below.
Two IPSec routers must have matching ID type and content configuration in order to set up a VPN tunnel.
The two ZyWALLs in this example can complete negotiation and establish a VPN tunnel.
Table 29-4 Matching ID Type and Content Configuration Example
Local ID type: IP
Local ID content: N/A
Local IP address: 1.1.1.1
Peer ID type: IP
Peer ID content: N/A
Peer IP address: 1.1.1.2
The two ZyWALLs in this example cannot complete their negotiation because ZyWALL B's Local ID type
is IP, but ZyWALL A's Peer ID type is set to E-mail. An "ID mismatched" message displays in the IPSEC
LOG.
VPN/IPSec Setup
Table 29-3 Peer Fields
N/A, do not enter anything.
Type a domain name (up to 31 characters) by which to identify the remote
IPSec router.
Type an e-mail address (up to 31 characters) by which to identify the remote
IPSec router.
ZYWALL A
ZyWALL 10~100 Series Internet Security Gateway
CONTENT=
ZYWALL B
Local ID type: IP
Local ID content: N/A
Local IP address: 1.1.1.2
Peer ID type: IP
Peer ID content: N/A
Peer IP address: 1.1.1.1
29-5