17.9.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 ZyXEL Devices in this example can complete negotiation and establish a VPN
tunnel.
Table 85 Matching ID Type and Content Configuration Example
ZYXEL DEVICE A
Local ID type: E-mail
Local ID content: tom@yourcompany.com
Peer ID type: IP
Peer ID content: 1.1.1.2
The two ZyXEL Devices in this example cannot complete their negotiation because ZyXEL
Device B's Local ID type is IP, but ZyXEL Device A's Peer ID type is set to E-mail. An "ID
mismatched" message displays in the IPSEC LOG.
Table 86 Mismatching ID Type and Content Configuration Example
ZYXEL DEVICE A
Local ID type: IP
Local ID content: 1.1.1.10
Peer ID type: E-mail
Peer ID content: aa@yahoo.com
17.10 Pre-Shared Key
A pre-shared key identifies a communicating party during a phase 1 IKE negotiation
(seeSection 17.12 on page
have to share it with another party before you can communicate with them over a secure
connection.
17.11 Editing VPN Policies
Click an Edit icon in the
Chapter 17 VPN Screens
ZYXEL DEVICE B
Local ID type: IP
Local ID content: 1.1.1.2
Peer ID type: E-mail
Peer ID content: tom@yourcompany.com
ZYXEL DEVICE B
Local ID type: IP
Local ID content: 1.1.1.10
Peer ID type: IP
Peer ID content: N/A
234for more on IKE phases). It is called "pre-shared" because you
VPN Setup Screen
to edit VPN policies.
P-2602H(W)(L)-DxA Series User's Guide
229