User`s guide

Chapter 10 IPSec VPN Config Screens
LAN-Cell 2 User’s Guide
246
" The LAN-Cell’s local and peer ID type and ID content must match the remote
IPSec router’s peer and local ID type and ID content, respectively.
In the following example, the ID type and content match so the LAN-Cell and the remote
IPSec router authenticate each other successfully.
In the following example, the ID type and content do not match so the authentication fails and
the LAN-Cell and the remote IPSec router cannot establish an IKE SA.
It is also possible to configure the LAN-Cell to ignore the identity of the remote IPSec router.
In this case, you usually set the peer ID type to Any. This is not as secure as other peer ID
types, however.
Certificates
It is also possible for the LAN-Cell and remote IPSec router to authenticate each other with
certificates. In this case, the authentication process is different.
• Instead of using the pre-shared key, the LAN-Cell and remote IPSec router check each
other’s certificates.
• The local ID type and ID content come from the certificate. On the LAN-Cell, you simply
select which certificate to use.
• If you set the peer ID type to Any, the LAN-Cell authenticates the remote IPSec router
using the trusted certificates and trusted CAs you have set up. Alternatively, if you want to
use a specific certificate to authenticate the remote IPSec router, you can use the
information in the certificate to specify the peer ID type and ID content.
Table 87 VPN Example: Matching ID Type and Content
LAN-CELL REMOTE IPSEC ROUTER
Local ID type: E-mail Local ID type: IP
Local ID content: [e-mail] 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: [e-mail]
Table 88 VPN Example: Mismatching ID Type and Content
LAN-CELL REMOTE IPSEC ROUTER
Local ID type: E-mail Local ID type: IP
Local ID content: [e-mail] Local ID content: 1.1.1.2
Peer ID type: IP Peer ID type: E-mail
Peer ID content: 1.1.1.15 Peer ID content: [e-mail]