Chapter 13 VPN

distinguish different incoming SAs and you can select between different encryption algorithms, authentication algorithms and key groups when you configure a VPN rule. 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.

Table 41 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 LTE Device.

 

 

E-mail

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

 

Device.

 

 

 

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.

13.3.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.

The two LTE Devices in this example can complete negotiation and establish a VPN tunnel.

Table 42 Matching ID Type and Content Configuration Example

LTE Device A

LTE Device 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

 

 

The two LTE Devices in this example cannot complete their negotiation because LTE Device B’s Local ID type is IP, but LTE Device A’s Remote ID type is set to E-mail. An “ID mismatched” message displays in the IPSEC LOG.

Table 43 Mismatching ID Type and Content Configuration Example

LTE DEVICE ALTE DEVICE 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

 

 

13.3.8 Pre-Shared Key

A pre-shared key identifies a communicating party during a phase 1 IKE negotiation (see Section

13.3.3on page 94 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.

 

97

LTE6100 User’s Guide