Chapter 20 IPSec VPN
Router identity consists of ID type and content. The ID type can be domain name, IP address, or
The ZyWALL and the remote IPSec router have their own identities, so both of them must store two sets of information, one for themselves and one for the other router. Local ID type and content refers to the ID type and content that applies to the router itself, and peer ID type and content refers to the ID type and content that applies to the other router.
"The ZyWALL’s local and peer ID type and content must match the remote IPSec router’s peer and local ID type and content, respectively.
For example, in Table 123 on page 376, the ZyWALL and the remote IPSec router authenticate each other successfully. In contrast, in Table 124 on page 376, the ZyWALL and the remote IPSec router cannot authenticate each other and, therefore, cannot establish an IKE SA.
Table 123 VPN Example: Matching ID Type and Content
ZYWALL | REMOTE IPSEC ROUTER |
Local ID type: | Local ID type: IP |
|
|
Local ID content: tom@yourcompany.com | Local ID content: 1.1.1.2 |
|
|
Peer ID type: IP | Peer ID type: |
|
|
Peer ID content: 1.1.1.2 | Peer ID content: tom@yourcompany.com |
|
|
Table 124 VPN Example: Mismatching ID Type and Content
ZYWALL | REMOTE IPSEC ROUTER |
Local ID type: | Local ID type: IP |
|
|
Local ID content: tom@yourcompany.com | Local ID content: 1.1.1.2 |
|
|
Peer ID type: IP | Peer ID type: |
|
|
Peer ID content: 1.1.1.20 | 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 less secure, so you should only use this if your ZyWALL provides another way to check the identity of the remote IPSec router (for example, extended authentication) or if you are troubleshooting a VPN tunnel.
Additional Topics for IKE SA
This section provides more information about IKE SA.
Negotiation Mode
There are two negotiation
376 |
| |
ZyWALL USG 100/200 Series User’s Guide |
| |
|
|
|