Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configuring VPN on a Device Running Junos OS

This section describes sample configurations of an IPsec VPN on a Junos OS device using the following IKE authentication methods:

Figure 1 illustrates the VPN topology used in all the examples described in this section. Here, H0 and H1 are the host PCs, R0 and R2 are the two endpoints of the IPsec VPN tunnel, and R1 is a router to route traffic between the two different networks.

Note:

The router R1 can be a Linux-based router, a Juniper Networks device, or any other vendor router.
Figure 1: VPN Topology VPN Topology

Table 1 provides a complete list of the supported IKE protocols, tunnel modes, Phase 1 negotiation mode, authentication method or algorithm, encryption algorithm, DH groups supported for the IKE authentication and encryption (Phase1, IKE Proposal), and for IPsec authentication and encryption (Phase2, IPsec Proposal). The listed protocols, modes, and algorithms are supported and required for 24.4R1 Common Criteria.

Table 1: VPN Combination Matrix

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 1 Proposal (P1, IKE)

Authentication Method

Authentication Algorithm

DH Group

Encryption Algorithm

IKEv2

Main

Route

pre-shared-keys

sha-256

group14

        group15  
        group16  
   

rsa-signatures-2048

sha-384

group19

aes-128-cbc
   

ecdsa-signatures-256

  

group20

aes-128-gcm
        group21  
   

ecdsa-signatures-384

    

aes-192-cbc
         

aes-256-cbc
         

aes-256-gcm

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 2 Proposal (P2, IPsec)

Authentication Algorithm

DH Group (PFS)

Encryption Method

Encryption Algorithm

IKEv2

Main

Route

  

group14

ESP

      group15    
      group16    
   

hmac-sha-256-128

group19

  

aes-128-cbc
    hmac-sha-512

group20

  

aes-128-gcm
     

group21

  

aes-192-cbc
         

aes-192-gcm
         

aes-256-cbc
         

aes-256-gcm
Note:

The following sections provide sample configurations of IKEv2 IPsec VPN examples for selected algorithms. Authentication algorithms can be replaced in the configurations to accomplish the user’s desired configurations. Use set security ike gateway <gw-name> version v2-only command for IKEv2 IPsec VPN.

Validation using X.509 Certificates

The following extendedKeyUsage rules for certificates are not required for any of the validation use cases claimed by the TOE, and are therefore not supported.

  • Certificates used for trusted updates and executable code integrity verification shall have the Code Signing purpose (id-kp 3 with OID 1.3.6.1.5.5.7.3.3) in the extendedKeyUsage field.

  • Server certificates presented for DTLS/TLS shall have the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1) in the extendedKeyUsage field.

  • Client certificates presented for DTLS/TLS shall have the Client Authentication purpose (id-kp 2 with OID 1.3.6.1.5.5.7.3.2) in the extendedKeyUsage field.

  • OCSP certificates presented for OCSP responses shall have the OCSP Signing purpose (id-kp 9 with OID 1.3.6.1.5.5.7.3.9) in the extendedKeyUsage field.

Configuring an IPsec VPN with an RSA Signature for IKE Authentication

The following section provides an example to configure Junos OS devices for IPsec VPN using RSA Signature as IKE Authentication method, whereas, the algorithms used in IKE/IPsec authentication/encryption is as shown in the following table. In this section, you configure devices running Junos OS for IPsec VPN using an RSA signature as the IKE authentication method. The algorithms used in IKE or IPsec authentication or encryption is shown in Table 2.

Table 2: IKE/IPsec Authentication and Encryption

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 1 Proposal (P1, IKE)

Authentication Method

Authentication Algorithm

DH Group

Encryption Algorithm

IKEv2

Main

Route

rsa-signatures-2048

sha-256

group19

aes-128-cbc

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 2 Proposal (P2, IPsec)

Authentication Algorithm

DH Group (PFS)

Encryption Method

Encryption Algorithm

IKEv2

Main

Route

hmac-sha-256-128

group19

ESP

aes-128-cbc

Configuring IPsec VPN with RSA Signature as IKE Authentication on the Initiator or Responder

To configure the IPsec VPN with RSA signature IKE authentication on the initiator:

  1. Configure the PKI. See Example: Configuring PKI.

  2. Generate the RSA key pair. See Example: Generating a Public-Private Key Pair.

  3. Generate and load the CA certificate. See Example: Loading CA and Local Certificates Manually.

  4. Load the CRL. See Example: Manually Loading a CRL onto the Device.

  5. Generate and load a local certificate. See Example: Loading CA and Local Certificates Manually.

  6. Generate a certificate signing request (CSR). See request security pki generate-certificate-request.

  7. Configure the IKE proposal.

    Note:

    Here, ike-proposal1 is the name given by the authorized administrator.

  8. Configure the IKE policy.

    Note:

    Here, ike-policy1 IKE policy name given by the authorized administrator.

  9. Configure the IPsec proposal.

    Note:

    Here, ipsec-proposal1 is the name given by the authorized administrator.

  10. Configure the IPsec policy.

    Note:

    Here, ipsec-policy1 is the name given by the authorized administrator.

  11. Configure the IKE.

    Note:

    Here, 192.0.2.8 is the peer VPN endpoint IP, 192.0.2.5 is the local VPN endpoint IP, and is the local outbound interface as VPN endpoint. The following configuration is also needed for IKEv2.

  12. Configure VPN.

    Note:

    Here, vpn1 is the VPN tunnel name given by the authorized administrator.

  13. Configure the outbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zone and trustLan and untrustLan are preconfigured network addresses.

  14. Configure the inbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zones and trustLan and untrustLan are preconfigured network addresses.

  15. Commit the configuration.

Configuring an IPsec VPN with an ECDSA Signature for IKE Authentication

In this section, you configure devices running Junos OS for IPsec VPN using an ECDSA signature as the IKE authentication method. The algorithms used in IKE or IPsec authentication or encryption are shown in Table 3.

Table 3: IKE or IPsec Authentication and Encryption

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 1 Proposal (P1, IKE)

Authentication Method

Authentication Algorithm

DH Group

Encryption Algorithm

IKEv2

Main

Route

ecdsa-signatures-256

sha-384

group14

aes-256-cbc

IKE Protocol

Tunnel Mode

Phase1 Negotiation Mode

Phase 2 Proposal (P2, IPsec)

Authentication Algorithm

DH Group (PFS)

Encryption Method

Encryption Algorithm

IKEv2

Main

Route

No Algorithm

group14

ESP

aes-256-gcm

Configuring IPsec VPN with ECDSA signature IKE authentication on the Initiator

To configure the IPsec VPN with ECDSA signature IKE authentication on the initiator:

  1. Configure the PKI and generate the ECDSA key pair. See, Example: Configuring PKI.

  2. Generate and load CA certificate. See Example: Loading CA and Local Certificates Manually.

  3. Load CRL. See Example: Manually Loading a CRL onto the Device.

  4. Generate and load a local certificate. See Example: Loading CA and Local Certificates Manually.

  5. Generate a certificate signing request (CSR). See request security pki generate-certificate-request.

  6. Configure the IKE proposal.

    Note:

    Here, ike-proposal1 is the IKE proposal name given by the authorized administrator.

  7. Configure the IKE policy.

  8. Configure the IPsec proposal.

    Note:

    Here, ipsec-proposal1 is the IPsec proposal name given by the authorized administrator.

  9. Configure the IPsec policy.

    Note:

    Here, ipsec-policy1 is the IPsec policy name and ipsec-proposal1 is the IPsec proposal name given by the authorized administrator.

  10. Configure IKE.

    Note:

    Here, gw1 is an IKE gateway name, 192.0.2.8 is the peer VPN endpoint IP, 192.0.2.5 is the local VPN endpoint IP, and is a local outbound interface as the VPN endpoint. The following configuration is also needed for IKEv2.

  11. Configure the VPN.

    Note:

    Here, vpn1 is the VPN tunnel name given by the authorized administrator.

  12. Configure the outbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zones and trustLan and untrustLan are preconfigured network addresses.

  13. Configure the inbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zones and trustLan and untrustLan are preconfigured network addresses.

  14. Commit your configuration.

Configuring IPsec VPN with ECDSA signature IKE authentication on the Responder

To configure IPsec VPN with ECDSA signature IKE authentication on the responder:

  1. Configure the PKI and generate the ECDSA key pair. See, Example: Configuring PKI.

  2. Generate and load CA certificate. See Example: Loading CA and Local Certificates Manually.

  3. Load the CRL. See Example: Manually Loading a CRL onto the Device .

  4. Configure the IKE proposal.

    Note:

    Here, ike-proposal1 is the IKE proposal name given by the authorized administrator.

  5. Configure the IKE policy.

  6. Configure the IPsec proposal.

    Note:

    Here, ipsec-proposal1 is the IPsec proposal name given by the authorized administrator.

  7. Configure the IPsec policy.

    Note:

    Here, ipsec-policy1 is the IPsec policy name and ipsec-proposal1 is the IPsec proposal name given by the authorized administrator.

  8. Configure the IKE.

    Note:

    Here, gw1 is an IKE gateway name, 192.0.2.5 is the peer VPN endpoint IP, 192.0.2.8 is the local VPN endpoint IP, and is a local outbound interface as the VPN endpoint. The following configuration is also needed for IKEv2.

  9. Configure the VPN.

    Note:

    Here, vpn1 is the VPN tunnel name given by the authorized administrator.

  10. Configure the outbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zones and trustLan and untrustLan are preconfigured network addresses.

  11. Configure the inbound flow policies.

    Note:

    Here, trustZone and untrustZone are preconfigured security zones and trustLan and untrustLan are preconfigured network addresses.

  12. Commit your configuration.

For more information on how to troubleshoot an IPSec VPN Connection, see Troubleshoot a VPN Tunnel That is down.

For more information on how to recover SSH connection that is unintentionally broken, see Troubleshoot SSH Issues.

For more information about how to configure NAT-T on SRX Series Firewall, see Route-Based and Policy-Based VPNs with NAT-T.

Configuring the Lifetime for an IKE SA

The IKE lifetime sets the lifetime of an IKE SA. When the IKE SA expires, it is replaced by a new SA (and SPI) or is terminated. The default value IKE lifetime is 3600 seconds.

To configure the IKE lifetime, include the lifetime-seconds statement and specify the number of seconds (180 through 86,400) at the [edit security ike proposal ike-proposal-name] hierarchy level:

Configuring the Lifetime for an IPsec SA

The IPsec lifetime option sets the lifetime of an IPsec SA. When the IPsec SA expires, it is replaced by a new SA (and SPI) or is terminated. A new SA has new authentication and encryption keys, and SPI; however, the algorithms may remain the same if the proposal is not changed. If lifetime is not configured and a lifetime is not sent by a responder, the lifetime is 28,800 seconds.

To configure the IPsec lifetime, include the lifetime-seconds statement and specify the number of seconds (180 through 28,800) at the [edit security ipsec proposal ipsec-proposal-name] hierarchy level:

To configure the IPsec lifetime by number of bytes, include the lifetime-kilobytes and Specify the lifetime (in kilobytes) of an IPsec security association (SA). If this statement is not configured, the number of kilobytes used for the SA lifetime is unlimited.

Range: 64 through 4,294,967,294 kilobytes at the [edit security ipsec proposal ipsec-proposal-name] hierarchy level:

Configuring Remote IKE IDs

By default, the IKE ID received from the peer is validated with the IP address configured for the IKE gateway. In certain network setups, the IKE ID received from the peer (the IKE ID can be an IPv4 or IPv6 address, email id, fully qualified domain name (FQDN), or a distinguished name) does not match the IKE gateway configured on the device. This can lead to a Phase 1 validation failure.

To configure the IKE ID perform the following steps:

  1. Configure the remote-identity statement at the set security ike gateway gateway-name hierarchy

    level to match the IKE ID that is received from the peer. The IKE ID values can be an IPv4 address or an IPv6 address, email id, FQDN, or a distinguished name.

  2. On the peer device, ensure that the IKE ID is the same as the remote-identity configured on the device. If the peer device is a Junos OS device, configure the local-identity statement at the set security ike gateway gateway-name hierarchy level. The IKE ID values can be an IPv4 address or an IPv6 address, email id, FQDN, or a distinguished name.

Configuring an IPsec VPN with Post-quantum Pre-shared Key (PPK) for IKE Authentication

To configure IPsec VPN with Post-quantum Pre-shared Key (PPK) as defined in RFC8784 for IKE Authentication, see Quantum Safe IPsec VPN.

Related Documentation