Chapter 18 VPN Screens
Table 92 Local ID Type and Content Fields
LOCAL ID TYPE= | CONTENT= |
IP | Type the IP address of your computer or leave the field blank to have the ZyXEL |
| Device automatically use its own IP address. |
|
|
DNS | Type a domain name (up to 31 characters) by which to identify this ZyXEL Device. |
|
|
Type an | |
| Device. |
|
|
| The domain name or |
| identification purposes only and does not need to be a real domain name or |
| address. |
|
|
Table 93 Peer ID Type and Content Fields
PEER ID TYPE= | CONTENT= |
IP | Type the IP address of the computer with which you will make the VPN connection |
| or leave the field blank to have the ZyXEL Device automatically use the address in |
| the Secure Gateway field. |
|
|
DNS | Type a domain name (up to 31 characters) by which to identify the remote IPSec |
| router. |
|
|
Type an | |
| router. |
|
|
| The domain name or |
| identification purposes only and does not need to be a real domain name or |
| 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 ZyXEL Devices in this example can complete negotiation and establish a VPN tunnel.
Table 94 Matching ID Type and Content Configuration Example
ZYXEL DEVICE A | ZYXEL DEVICE B |
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 |
|
|
244 |
| |
| ||
|
|
|