beautypg.com

1 id type and content examples – ZyXEL Communications P-2802H(W)(L)-I Series User Manual

Page 192

background image

Chapter 14 VPN Screens

P-2802H(W)(L)-I Series User’s Guide

192

14.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 73 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.

E-mail

Type an e-mail address (up to 31 characters) by which to identify this ZyXEL

Device.

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.

Table 74 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 Address field.

DNS

Type a domain name (up to 31 characters) by which to identify the remote IPSec

router.

E-mail

Type an e-mail address (up to 31 characters) by which to identify the remote IPSec

router.

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 Address field below.

Table 75 Matching ID Type and Content Configuration Example

ZYXEL DEVICE A

ZYXEL DEVICE B

Local ID type: E-mail

Local ID type: IP

Local ID content: [email protected]

Local ID content: 1.1.1.2

Peer ID type: IP

Peer ID type: E-mail

Peer ID content: 1.1.1.2

Peer ID content: [email protected]