ZyXEL nbg-5715 Guia Do Utilizador
Chapter 18 IPSec VPN
NBG5715 User’s Guide
145
addresses. The NBG5715 can distinguish up to 48 incoming SAs because you can select between
three encryption algorithms (DES, 3DES and AES), two authentication algorithms (MD5 and SHA1)
and eight key groups when you configure a VPN rule (see
three encryption algorithms (DES, 3DES and AES), two authentication algorithms (MD5 and SHA1)
and eight key groups when you configure a VPN rule (see
). The ID type
and content act as an extra level of identification for incoming SAs.
The type of ID can be a domain name, an IP address or an e-mail address. The content is the IP
address, domain name, or e-mail address.
address, domain name, or e-mail address.
18.7.7.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.
tunnel.
The two NBG5715s in this example can complete negotiation and establish a VPN tunnel.
The two NBG5715s in this example cannot complete their negotiation because NBG5715 B’s Local
ID type is IP, but NBG5715 A’s Remote ID type is set to E-mail. An “ID mismatched” message
displays in the IPSEC LOG.
ID type is IP, but NBG5715 A’s Remote ID type is set to E-mail. An “ID mismatched” message
displays in the IPSEC LOG.
18.7.8 Pre-Shared Key
A pre-shared key identifies a communicating party during a phase 1 IKE negotiation (see
for more on IKE phases). It is called “pre-shared” because you have to share it
with another party before you can communicate with them over a secure connection.
Table 59
Local ID Type and Content Fields
LOCAL ID TYPE= CONTENT=
IP
Type the IP address of your computer.
DNS
Type a domain name (up to 31 characters) by which to identify this NBG5715.
E-mail
Type an e-mail address (up to 31 characters) by which to identify this NBG5715.
The domain name or e-mail address that you use in the Local ID Content field
is used for identification purposes only and does not need to be a real domain
name or e-mail address.
is used for identification purposes only and does not need to be a real domain
name or e-mail address.
Table 60
Matching ID Type and Content Configuration Example
NBG5715 A
NBG5715 B
Local ID type: E-mail
Local ID type: IP
Local ID content: tom@yourcompany.com
Local ID content: 1.1.1.2
Remote ID type: IP
Remote ID type: E-mail
Remote ID content: 1.1.1.2
Remote ID content: tom@yourcompany.com
Table 61
Mismatching ID Type and Content Configuration Example
NBG5715 A
NBG5715 B
Local ID type: IP
Local ID type: IP
Local ID content: 1.1.1.10
Local ID content: 1.1.1.2
Remote ID type: E-mail
Remote ID type: IP
Remote ID content: aa@yahoo.com
Remote ID content: 1.1.1.0