mirror/setup-ipsec-vpn

Fork 0

mirror of synced 2024-11-28 23:56:04 +03:00

hwdsl2 34ece8bdc4 Update docs

2022-02-13 10:38:49 -06:00

41 KiB

Raw Blame History

Guide: How to Set Up and Use IKEv2 VPN

Read this in other languages: English, 简体中文.

Note: You may also connect using IPsec/L2TP or IPsec/XAuth mode.

Introduction
Set up IKEv2 using helper script
Configure IKEv2 VPN clients
Manage client certificates
Manually set up IKEv2 on the VPN server
Troubleshooting
Remove IKEv2
References

Introduction

Modern operating systems (such as Windows 7 and newer) support the IKEv2 standard. Internet Key Exchange (IKE or IKEv2) is the protocol used to set up a Security Association (SA) in the IPsec protocol suite. Compared to IKE version 1, IKEv2 contains improvements such as Standard Mobility support through MOBIKE, and improved reliability.

Libreswan can authenticate IKEv2 clients on the basis of X.509 Machine Certificates using RSA signatures. This method does not require an IPsec PSK, username or password. It can be used with:

Windows 7, 8, 10 and 11
OS X (macOS)
iOS (iPhone/iPad)
Android 4 and newer (using the strongSwan VPN client)
Linux

After following this guide, you will be able to connect to the VPN using IKEv2 in addition to the existing IPsec/L2TP and IPsec/XAuth ("Cisco IPsec") modes.

Set up IKEv2 using helper script

Important: Before continuing, you should have successfully set up your own VPN server, and (optional but recommended) updated Libreswan. Docker users, see here.

Use this helper script to automatically set up IKEv2 on the VPN server:

# Set up IKEv2 using default options
sudo ikev2.sh --auto
# Alternatively, you may customize IKEv2 options
sudo ikev2.sh

When finished, continue to configure IKEv2 VPN clients. Advanced users can optionally enable IKEv2-only mode.

Error: "sudo: ikev2.sh: command not found".

This is normal if you used an older version of the VPN setup script. First, download the IKEv2 helper script:

wget https://git.io/ikev2setup -qO /opt/src/ikev2.sh
chmod +x /opt/src/ikev2.sh && ln -s /opt/src/ikev2.sh /usr/bin

Then run the script using the instructions above.

You may optionally specify a DNS name, client name and/or custom DNS servers. Click here for details.

When running IKEv2 setup in auto mode, advanced users can optionally specify a DNS name to be used as the VPN server's address. The DNS name must be a fully qualified domain name (FQDN). It will be included in the generated server certificate. Example:

sudo VPN_DNS_NAME='vpn.example.com' ikev2.sh --auto

Similarly, you may optionally specify a name for the first IKEv2 client. The default is vpnclient if not specified.

sudo VPN_CLIENT_NAME='your_client_name' ikev2.sh --auto

By default, IKEv2 clients are set to use Google Public DNS when the VPN is active. When running IKEv2 setup in auto mode, you may optionally specify custom DNS server(s). Example:

sudo VPN_DNS_SRV1=1.1.1.1 VPN_DNS_SRV2=1.0.0.1 ikev2.sh --auto

Learn how to update the IKEv2 helper script on your server.

The IKEv2 helper script is updated from time to time for bug fixes and improvements (commit log). When a newer version is available, you may optionally update the IKEv2 helper script on your server. Note that these commands will overwrite any existing ikev2.sh.

wget https://git.io/ikev2setup -qO /opt/src/ikev2.sh
chmod +x /opt/src/ikev2.sh && ln -s /opt/src/ikev2.sh /usr/bin 2>/dev/null

Click here to view usage information for the IKEv2 script.

Usage: bash ikev2.sh [options]

Options:
  --auto                        run IKEv2 setup in auto mode using default options (for initial setup only)
  --addclient [client name]     add a new client using default options
  --exportclient [client name]  export configuration for an existing client
  --listclients                 list the names of existing clients
  --revokeclient [client name]  revoke a client certificate
  --removeikev2                 remove IKEv2 and delete all certificates and keys from the IPsec database
  -h, --help                    show this help message and exit

To customize IKEv2 or client options, run this script without arguments.

Configure IKEv2 VPN clients

Read this in other languages: English, 简体中文.

Note: If you want to add or export IKEv2 client(s), just run the helper script again. Use option -h to show usage information.

Windows 7, 8, 10 and 11
OS X (macOS)
iOS (iPhone/iPad)
Android
Linux

Windows 7, 8, 10 and 11

Windows 8, 10 and 11 users can automatically import IKEv2 configuration:

Securely transfer the generated .p12 file to your computer.
Right-click on ikev2_config_import.cmd and save this helper script to the same folder as the .p12 file.
Right-click on the saved script, select Properties. Click on Unblock at the bottom, then click on OK.
Right-click on the saved script, select Run as administrator and follow the prompts.

Alternatively, you may manually import IKEv2 configuration. These steps apply to Windows 7, 8, 10 and 11.

Securely transfer the generated .p12 file to your computer, then import it into the "Computer account" certificate store. To import the .p12 file, run the following from an elevated command prompt:
```
# Import .p12 file (replace with your own value)
certutil -f -importpfx "\path\to\your\file.p12" NoExport
```
Note: If there is no password for client config files in the output of the IKEv2 helper script, press Enter to continue, or if manually importing the .p12 file, leave the password field blank.

Alternatively, you can manually import the .p12 file. Click here for instructions. Make sure that the client cert is placed in "Personal -> Certificates", and the CA cert is placed in "Trusted Root Certification Authorities -> Certificates".

On the Windows computer, add a new IKEv2 VPN connection. For Windows 8, 10 and 11, it is recommended to create the VPN connection using the following commands from a command prompt, for improved security and performance. Windows 7 does not support these commands, you may manually create the VPN connection (see below).

# Create VPN connection (replace server address with your own value)
powershell -command "Add-VpnConnection -ServerAddress 'Your VPN Server IP (or DNS name)' -Name 'My IKEv2 VPN' -TunnelType IKEv2 -AuthenticationMethod MachineCertificate -EncryptionLevel Required -PassThru"
# Set IPsec configuration
powershell -command "Set-VpnConnectionIPsecConfiguration -ConnectionName 'My IKEv2 VPN' -AuthenticationTransformConstants GCMAES128 -CipherTransformConstants GCMAES128 -EncryptionMethod AES256 -IntegrityCheckMethod SHA256 -PfsGroup None -DHGroup Group14 -PassThru -Force"

Alternatively, you can manually create the VPN connection. Click here for instructions. If you specified the server's DNS name (instead of its IP address) during IKEv2 setup, you must enter the DNS name in the Internet address field.

(This step is required if you manually created the VPN connection) Enable stronger ciphers for IKEv2 with a one-time registry change. Download and import the .reg file below, or run the following from an elevated command prompt. Read more here.
- For Windows 7, 8, 10 and 11 (download .reg file)
```
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RasMan\Parameters /v NegotiateDH2048_AES256 /t REG_DWORD /d 0x1 /f
```

To connect to the VPN: Click on the wireless/network icon in your system tray, select the new VPN entry, and click Connect. Once successfully connected, you can verify that your traffic is being routed properly by looking up your IP address on Google. It should say "Your public IP address is Your VPN Server IP".

If you get an error when trying to connect, see Troubleshooting.

OS X (macOS)

First, securely transfer the generated .mobileconfig file to your Mac, then double-click and follow the prompts to import as a macOS profile. If your Mac runs macOS Big Sur or newer, open System Preferences and go to the Profiles section to finish importing. When finished, check to make sure "IKEv2 VPN" is listed under System Preferences -> Profiles.

To connect to the VPN:

Open System Preferences and go to the Network section.
Select the VPN connection with Your VPN Server IP (or DNS name).
Check the Show VPN status in menu bar checkbox.
Click Connect.

(Optional feature) You can choose to enable VPN On Demand. This is an "always-on" feature that can automatically connect to the VPN while on Wi-Fi. To enable, check the Connect on demand checkbox for the VPN connection, and click Apply.

If you manually set up IKEv2 without using the helper script, click here for instructions.

First, securely transfer the generated .p12 file to your Mac, then double-click to import into the login keychain in Keychain Access. Next, double-click on the imported IKEv2 VPN CA certificate, expand Trust and select Always Trust from the IP Security (IPsec) drop-down menu. Close the dialog using the red "X" on the top-left corner. When prompted, use Touch ID or enter your password and click "Update Settings".

When finished, check to make sure both the new client certificate and IKEv2 VPN CA are listed under the Certificates category of login keychain.

Open System Preferences and go to the Network section.
Click the + button in the lower-left corner of the window.
Select VPN from the Interface drop-down menu.
Select IKEv2 from the VPN Type drop-down menu.
Enter anything you like for the Service Name.
Click Create.
Enter Your VPN Server IP (or DNS name) for the Server Address.
Note: If you specified the server's DNS name (instead of its IP address) during IKEv2 setup, you must enter the DNS name in the Server Address and Remote ID fields.
Enter Your VPN Server IP (or DNS name) for the Remote ID.
Enter Your VPN client name in the Local ID field.
Note: This must match exactly the client name you specified during IKEv2 setup. Same as the first part of your .p12 filename.
Click the Authentication Settings... button.
Select None from the Authentication Settings drop-down menu.
Select the Certificate radio button, then select the new client certificate.
Click OK.
Check the Show VPN status in menu bar checkbox.
Click Apply to save the VPN connection information.
Click Connect.

Once successfully connected, you can verify that your traffic is being routed properly by looking up your IP address on Google. It should say "Your public IP address is Your VPN Server IP".

If you get an error when trying to connect, see Troubleshooting.

iOS

First, securely transfer the generated .mobileconfig file to your iOS device, then import it as an iOS profile. To transfer the file, you may use:

AirDrop, or
Upload to your device using File Sharing, then open the "Files" app on your iOS device, move the uploaded file to the "On My iPhone" folder. After that, tap the file and go to the "Settings" app to import, or
Host the file on a secure website of yours, then download and import it in Mobile Safari.

When finished, check to make sure "IKEv2 VPN" is listed under Settings -> General -> Profile(s).

To connect to the VPN:

Go to Settings -> General -> VPN.
Select the VPN connection with Your VPN Server IP (or DNS name).
Slide the VPN switch ON.

(Optional feature) You can choose to enable VPN On Demand. This is an "always-on" feature that can automatically connect to the VPN while on Wi-Fi. To enable, tap the "i" icon on the right of the VPN connection, and enable Connect On Demand.

If you manually set up IKEv2 without using the helper script, click here for instructions.

First, securely transfer the generated ikev2vpnca.cer and .p12 files to your iOS device, then import them one by one as iOS profiles. To transfer the files, you may use:

AirDrop, or
Upload to your device using File Sharing, then open the "Files" app on your iOS device, move the uploaded files to the "On My iPhone" folder. After that, tap each file and go to the "Settings" app to import, or
Host the files on a secure website of yours, then download and import them in Mobile Safari.

When finished, check to make sure both the new client certificate and IKEv2 VPN CA are listed under Settings -> General -> Profiles.

Go to Settings -> General -> VPN.
Tap Add VPN Configuration....
Tap Type. Select IKEv2 and go back.
Tap Description and enter anything you like.
Tap Server and enter Your VPN Server IP (or DNS name).
Note: If you specified the server's DNS name (instead of its IP address) during IKEv2 setup, you must enter the DNS name in the Server and Remote ID fields.
Tap Remote ID and enter Your VPN Server IP (or DNS name).
Enter Your VPN client name in the Local ID field.
Note: This must match exactly the client name you specified during IKEv2 setup. Same as the first part of your .p12 filename.
Tap User Authentication. Select None and go back.
Make sure the Use Certificate switch is ON.
Tap Certificate. Select the new client certificate and go back.
Tap Done.
Slide the VPN switch ON.

Once successfully connected, you can verify that your traffic is being routed properly by looking up your IP address on Google. It should say "Your public IP address is Your VPN Server IP".

If you get an error when trying to connect, see Troubleshooting.

Android

Securely transfer the generated .sswan file to your Android device.
Install strongSwan VPN Client from Google Play, F-Droid or strongSwan download server.
Launch the strongSwan VPN client.
Tap the "more options" menu on top right, then tap Import VPN profile.
Choose the .sswan file you transferred from the VPN server.
Note: To find the .sswan file, tap the three-line menu button, then browse to the location you saved the file.
On the "Import VPN profile" screen, tap IMPORT CERTIFICATE FROM VPN PROFILE, and follow the prompts.
On the "Choose certificate" screen, select the new client certificate, then tap Select.
Tap IMPORT.
Tap the new VPN profile to connect.

If your device runs Android 6.0 or older, click here for additional instructions.

If your device runs Android 6.0 (Marshmallow) or older, in order to connect using the strongSwan VPN client, you must make the following change on the VPN server: Edit /etc/ipsec.d/ikev2.conf on the server. Append authby=rsa-sha1 to the end of the conn ikev2-cp section, indented by two spaces. Save the file and run service ipsec restart.

(Optional feature) You can choose to enable the "Always-on VPN" feature on Android. Launch the Settings app, go to Network & internet -> Advanced -> VPN, click the gear icon on the right of "strongSwan VPN Client", then enable the Always-on VPN and Block connections without VPN options.

If you manually set up IKEv2 without using the helper script, click here for instructions.

Android 10 and newer:

Securely transfer the generated .p12 file to your Android device.
Install strongSwan VPN Client from Google Play, F-Droid or strongSwan download server.
Launch the Settings application.
Go to Security -> Advanced -> Encryption & credentials.
Tap Install certificates from storage (or SD card).
Choose the .p12 file you transferred from the VPN server, and follow the prompts.
Note: To find the .p12 file, tap the three-line menu button, then browse to the location you saved the file.
Launch the strongSwan VPN client and tap Add VPN Profile.
Enter Your VPN Server IP (or DNS name) in the Server field.
Note: If you specified the server's DNS name (instead of its IP address) during IKEv2 setup, you must enter the DNS name in the Server field.
Select IKEv2 Certificate from the VPN Type drop-down menu.
Tap Select user certificate, select the new client certificate and confirm.
(Important) Tap Show advanced settings. Scroll down, find and enable the Use RSA/PSS signatures option.
Save the new VPN connection, then tap to connect.

Android 4 to 9:

Securely transfer the generated .p12 file to your Android device.
Install strongSwan VPN Client from Google Play, F-Droid or strongSwan download server.
Launch the strongSwan VPN client and tap Add VPN Profile.
Enter Your VPN Server IP (or DNS name) in the Server field.
Note: If you specified the server's DNS name (instead of its IP address) during IKEv2 setup, you must enter the DNS name in the Server field.
Select IKEv2 Certificate from the VPN Type drop-down menu.
Tap Select user certificate, then tap Install certificate.
Choose the .p12 file you transferred from the VPN server, and follow the prompts.
Note: To find the .p12 file, tap the three-line menu button, then browse to the location you saved the file.
(Important) Tap Show advanced settings. Scroll down, find and enable the Use RSA/PSS signatures option.
Save the new VPN connection, then tap to connect.

Once successfully connected, you can verify that your traffic is being routed properly by looking up your IP address on Google. It should say "Your public IP address is Your VPN Server IP".

If you get an error when trying to connect, see Troubleshooting.

Linux

Before configuring Linux VPN clients, you must make the following change on the VPN server: Edit /etc/ipsec.d/ikev2.conf on the server. Append authby=rsa-sha1 to the end of the conn ikev2-cp section, indented by two spaces. Save the file and run service ipsec restart.

To configure your Linux computer to connect to IKEv2 as a VPN client, first install the strongSwan plugin for NetworkManager:

# Ubuntu and Debian
sudo apt-get update
sudo apt-get install network-manager-strongswan

# Arch Linux
sudo pacman -Syu  # upgrade all packages
sudo pacman -S networkmanager-strongswan

# Fedora
sudo yum install NetworkManager-strongswan-gnome

# CentOS
sudo yum install epel-release
sudo yum --enablerepo=epel install NetworkManager-strongswan-gnome

Next, securely transfer the generated .p12 file from the VPN server to your Linux computer. After that, extract the CA certificate, client certificate and private key. Replace vpnclient.p12 in the example below with the name of your .p12 file.

# Example: Extract CA certificate, client certificate and private key.
#          You may delete the .p12 file when finished.
# Note: You may need to enter the import password, which can be found
#       in the output of the IKEv2 helper script. If the output does not
#       contain an import password, press Enter to continue.
openssl pkcs12 -in vpnclient.p12 -cacerts -nokeys -out ikev2vpnca.cer
openssl pkcs12 -in vpnclient.p12 -clcerts -nokeys -out vpnclient.cer
openssl pkcs12 -in vpnclient.p12 -nocerts -nodes  -out vpnclient.key
rm vpnclient.p12

# (Important) Protect certificate and private key files
# Note: This step is optional, but strongly recommended.
sudo chown root.root ikev2vpnca.cer vpnclient.cer vpnclient.key
sudo chmod 600 ikev2vpnca.cer vpnclient.cer vpnclient.key

You can then set up and enable the VPN connection:

Go to Settings -> Network -> VPN. Click the + button.
Select IPsec/IKEv2 (strongswan).
Enter anything you like in the Name field.
In the Gateway (Server) section, enter Your VPN Server IP (or DNS name) for the Address.
Select the ikev2vpnca.cer file for the Certificate.
In the Client section, select Certificate(/private key) in the Authentication drop-down menu.
Select Certificate/private key in the Certificate drop-down menu (if exists).
Select the vpnclient.cer file for the Certificate (file).
Select the vpnclient.key file for the Private key.
In the Options section, check the Request an inner IP address checkbox.
In the Cipher proposals (Algorithms) section, check the Enable custom proposals checkbox.
Leave the IKE field blank.
Enter aes128gcm16 in the ESP field.
Click Add to save the VPN connection information.
Turn the VPN switch ON.

Once successfully connected, you can verify that your traffic is being routed properly by looking up your IP address on Google. It should say "Your public IP address is Your VPN Server IP".

If you get an error when trying to connect, see Troubleshooting.

Manage client certificates

List existing clients
Add a client certificate
Export configuration for an existing client
Delete a client certificate
Revoke a client certificate

List existing clients

If you want to list the names of existing IKEv2 clients, run the helper script with the --listclients option. Use option -h to show usage information.

sudo ikev2.sh --listclients

Add a client certificate

To generate certificates for additional IKEv2 clients, just run the helper script again. To customize client certificate options, run the script without arguments.

sudo ikev2.sh --addclient [client name]

Alternatively, you may manually add a client certificate. Refer to step 4 in this section.

Export configuration for an existing client

By default, the IKEv2 helper script exports client configuration after running. If later you want to export configuration for an existing client, you may use:

sudo ikev2.sh --exportclient [client name]

Delete a client certificate

Important: Deleting a client certificate from the IPsec database WILL NOT prevent VPN client(s) from connecting using that certificate! For this use case, you MUST revoke the client certificate instead of deleting it.

First, read the important note above. Then click here for instructions.

Important: Please first read the important note above. If you still want to delete a certificate, refer to the steps below. This cannot be undone!

To delete a client certificate:

List certificates in the IPsec database:

certutil -L -d sql:/etc/ipsec.d

Example output:

Certificate Nickname                               Trust Attributes
                                                   SSL,S/MIME,JAR/XPI

IKEv2 VPN CA                                       CTu,u,u
($PUBLIC_IP)                                       u,u,u
vpnclient                                          u,u,u

Delete the client certificate and private key. Replace "Nickname" below with the nickname of the client certificate you want to delete, e.g. vpnclient.
```
certutil -F -d sql:/etc/ipsec.d -n "Nickname"
certutil -D -d sql:/etc/ipsec.d -n "Nickname" 2>/dev/null
```
(Optional) Delete the previously generated client configuration files (.p12, .mobileconfig and .sswan files) for this VPN client, if any.

Revoke a client certificate

In certain circumstances, you may need to revoke a previously generated VPN client certificate. To revoke a certificate, run the helper script again and select the appropriate option. Or you may run:

sudo ikev2.sh --revokeclient [client name]

Alternatively, you may manually revoke a client certificate. Click here for instructions.

Alternatively, you may manually revoke a client certificate. This can be done using crlutil. See example steps below, commands must be run as root.

Check the database, and identify the nickname of the client certificate you want to revoke.

certutil -L -d sql:/etc/ipsec.d

Certificate Nickname                               Trust Attributes
                                                   SSL,S/MIME,JAR/XPI

IKEv2 VPN CA                                       CTu,u,u
($PUBLIC_IP)                                       u,u,u
vpnclient-to-revoke                                u,u,u

In this example, we will revoke the certificate with nickname vpnclient-to-revoke, issued by IKEv2 VPN CA.

Find the serial number of this client certificate.
```
certutil -L -d sql:/etc/ipsec.d -n "vpnclient-to-revoke"
```
```
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            00:cd:69:ff:74
... ...
```
From the output, we see that the serial number is CD69FF74 in hexadecimal, which is 3446275956 in decimal. It will be used in the next steps.

Create a new Certificate Revocation List (CRL). You only need to do this once for each CA.

if ! crlutil -L -d sql:/etc/ipsec.d -n "IKEv2 VPN CA" 2>/dev/null; then
  crlutil -G -d sql:/etc/ipsec.d -n "IKEv2 VPN CA" -c /dev/null
fi

CRL Info:
:
    Version: 2 (0x1)
    Signature Algorithm: PKCS #1 SHA-256 With RSA Encryption
    Issuer: "O=IKEv2 VPN,CN=IKEv2 VPN CA"
    This Update: Sat Jun 06 22:00:00 2020
    CRL Extensions:

Add the client certificate you want to revoke to the CRL. Here we specify the certificate's serial number in decimal, and the revocation time in GeneralizedTime format (YYYYMMDDhhmmssZ) in UTC.

crlutil -M -d sql:/etc/ipsec.d -n "IKEv2 VPN CA" <<EOF
addcert 3446275956 20200606220100Z
EOF

CRL Info:
:
    Version: 2 (0x1)
    Signature Algorithm: PKCS #1 SHA-256 With RSA Encryption
    Issuer: "O=IKEv2 VPN,CN=IKEv2 VPN CA"
    This Update: Sat Jun 06 22:02:00 2020
    Entry 1 (0x1):
        Serial Number:
            00:cd:69:ff:74
        Revocation Date: Sat Jun 06 22:01:00 2020
    CRL Extensions:

Note: If you want to remove a certificate from the CRL, replace addcert 3446275956 20200606220100Z above with rmcert 3446275956. For other crlutil usage, read here.

Finally, let Libreswan re-read the updated CRL.
```
ipsec crls
```

Manually set up IKEv2 on the VPN server

As an alternative to using the helper script, advanced users can manually set up IKEv2. Before continuing, it is recommended to update Libreswan to the latest version.

The following example shows how to manually configure IKEv2 with Libreswan. Commands below must be run as root.

Find the VPN server's public IP, save it to a variable and check.
```
PUBLIC_IP=$(dig @resolver1.opendns.com -t A -4 myip.opendns.com +short)
[ -z "$PUBLIC_IP" ] && PUBLIC_IP=$(wget -t 3 -T 15 -qO- http://ipv4.icanhazip.com)
printf '%s\n' "$PUBLIC_IP"
```
Check to make sure the output matches the server's public IP. This variable is required in the steps below.

Note: Alternatively, you may specify the server's DNS name here. e.g. PUBLIC_IP=myvpn.example.com.

Add a new IKEv2 connection:

if ! grep -qs '^include /etc/ipsec\.d/\*\.conf$' /etc/ipsec.conf; then
  echo >> /etc/ipsec.conf
  echo 'include /etc/ipsec.d/*.conf' >> /etc/ipsec.conf
fi

Note: If you specified the server's DNS name (instead of its IP address) in step 1 above, you must replace leftid=$PUBLIC_IP in the command below with leftid=@$PUBLIC_IP.

cat > /etc/ipsec.d/ikev2.conf <<EOF

conn ikev2-cp
  left=%defaultroute
  leftcert=$PUBLIC_IP
  leftid=$PUBLIC_IP
  leftsendcert=always
  leftsubnet=0.0.0.0/0
  leftrsasigkey=%cert
  right=%any
  rightid=%fromcert
  rightaddresspool=192.168.43.10-192.168.43.250
  rightca=%same
  rightrsasigkey=%cert
  narrowing=yes
  dpddelay=30
  dpdtimeout=120
  dpdaction=clear
  auto=add
  ikev2=insist
  rekey=no
  pfs=no
  ike=aes256-sha2,aes128-sha2,aes256-sha1,aes128-sha1
  phase2alg=aes_gcm-null,aes128-sha1,aes256-sha1,aes128-sha2,aes256-sha2
  ikelifetime=24h
  salifetime=24h
EOF

We need to add a few more lines to that file. First check your Libreswan version, then run one of the following commands:

ipsec --version

For Libreswan 3.23 and newer:

cat >> /etc/ipsec.d/ikev2.conf <<EOF
  modecfgdns="8.8.8.8 8.8.4.4"
  encapsulation=yes
  mobike=no
EOF

Note: The MOBIKE IKEv2 extension allows VPN clients to change network attachment points, e.g. switch between mobile data and Wi-Fi and keep the IPsec tunnel up on the new IP. If your server (or Docker host) is NOT running Ubuntu Linux, and you wish to enable MOBIKE support, replace mobike=no with mobike=yes in the command above. DO NOT enable this option on Ubuntu systems or Raspberry Pis.

For Libreswan 3.19-3.22:

cat >> /etc/ipsec.d/ikev2.conf <<EOF
  modecfgdns1=8.8.8.8
  modecfgdns2=8.8.4.4
  encapsulation=yes
EOF

For Libreswan 3.18 and older:

cat >> /etc/ipsec.d/ikev2.conf <<EOF
  modecfgdns1=8.8.8.8
  modecfgdns2=8.8.4.4
  forceencaps=yes
EOF

Generate Certificate Authority (CA) and VPN server certificates.

Note: Specify the certificate validity period (in months) with "-v". e.g. "-v 120".

Generate CA certificate:

certutil -z <(head -c 1024 /dev/urandom) \
  -S -x -n "IKEv2 VPN CA" \
  -s "O=IKEv2 VPN,CN=IKEv2 VPN CA" \
  -k rsa -g 3072 -v 120 \
  -d sql:/etc/ipsec.d -t "CT,," -2

Generating key.  This may take a few moments...

Is this a CA certificate [y/N]?
y
Enter the path length constraint, enter to skip [<0 for unlimited path]: >
Is this a critical extension [y/N]?
N

Generate VPN server certificate:

Note: If you specified the server's DNS name (instead of its IP address) in step 1 above, you must replace --extSAN "ip:$PUBLIC_IP,dns:$PUBLIC_IP" in the command below with --extSAN "dns:$PUBLIC_IP".

certutil -z <(head -c 1024 /dev/urandom) \
  -S -c "IKEv2 VPN CA" -n "$PUBLIC_IP" \
  -s "O=IKEv2 VPN,CN=$PUBLIC_IP" \
  -k rsa -g 3072 -v 120 \
  -d sql:/etc/ipsec.d -t ",," \
  --keyUsage digitalSignature,keyEncipherment \
  --extKeyUsage serverAuth \
  --extSAN "ip:$PUBLIC_IP,dns:$PUBLIC_IP"

Generating key.  This may take a few moments...

Generate client certificate(s), then export the .p12 file that contains the client certificate, private key, and CA certificate.

Note: You may repeat this step to generate certificates for additional VPN clients, but make sure to replace every vpnclient with vpnclient2, etc. To connect multiple VPN clients, you must generate a unique certificate for each.

Generate client certificate:
```
certutil -z <(head -c 1024 /dev/urandom) \
  -S -c "IKEv2 VPN CA" -n "vpnclient" \
  -s "O=IKEv2 VPN,CN=vpnclient" \
  -k rsa -g 3072 -v 120 \
  -d sql:/etc/ipsec.d -t ",," \
  --keyUsage digitalSignature,keyEncipherment \
  --extKeyUsage serverAuth,clientAuth -8 "vpnclient"
```
```
Generating key.  This may take a few moments...
```
Export .p12 file:
```
pk12util -d sql:/etc/ipsec.d -n "vpnclient" -o vpnclient.p12
```
```
Enter password for PKCS12 file:
Re-enter password:
pk12util: PKCS12 EXPORT SUCCESSFUL
```
Enter a secure password to protect the exported .p12 file (when importing into an iOS or macOS device, this password cannot be empty).

(For iOS clients) Export the CA certificate as ikev2vpnca.cer:

certutil -L -d sql:/etc/ipsec.d -n "IKEv2 VPN CA" -a -o ikev2vpnca.cer

The database should now contain:

certutil -L -d sql:/etc/ipsec.d

Certificate Nickname                               Trust Attributes
                                                   SSL,S/MIME,JAR/XPI

IKEv2 VPN CA                                       CTu,u,u
($PUBLIC_IP)                                       u,u,u
vpnclient                                          u,u,u

Note: To display a certificate, use certutil -L -d sql:/etc/ipsec.d -n "Nickname". To revoke a client certificate, follow these steps. For other certutil usage, read here.

(Important) Restart the IPsec service:
```
service ipsec restart
```

Before continuing, you must restart the IPsec service. The IKEv2 setup on the VPN server is now complete. Follow instructions to configure VPN clients.

Troubleshooting

Read this in other languages: English, 简体中文.

IKEv2 disconnects after one hour
Unable to connect multiple IKEv2 clients
Other known issues

IKEv2 disconnects after one hour

If the IKEv2 connection disconnects automatically after one hour (60 minutes), apply this fix: Edit /etc/ipsec.d/ikev2.conf on the VPN server (or /etc/ipsec.conf if it does not exist), append these lines to the end of section conn ikev2-cp, indented by two spaces:

  ikelifetime=24h
  salifetime=24h

Save the file and run service ipsec restart. As of 2021-01-20, the IKEv2 helper script was updated to include this fix.

Unable to connect multiple IKEv2 clients

To connect multiple IKEv2 clients, you must generate a unique certificate for each.

If you are unable to connect multiple IKEv2 clients from behind the same NAT (e.g. home router), apply this fix: Edit /etc/ipsec.d/ikev2.conf on the VPN server, find the line leftid=@<your_server_ip> and remove the @, i.e. replace it with leftid=<your_server_ip>. Save the file and run service ipsec restart. Do not apply this fix if leftid is a DNS name, which is not affected. As of 2021-02-01, the IKEv2 helper script was updated to include this fix.

Other known issues

The built-in VPN client in Windows may not support IKEv2 fragmentation (this feature requires Windows 10 v1803 or newer). On some networks, this can cause the connection to fail or have other issues. You may instead try the IPsec/L2TP or IPsec/XAuth mode.
If using the strongSwan Android VPN client, you must update Libreswan on your server to version 3.26 or above.

Remove IKEv2

If you want to remove IKEv2 from the VPN server, but keep the IPsec/L2TP and IPsec/XAuth ("Cisco IPsec") modes (if installed), run the helper script again and select the "Remove IKEv2" option. Warning: All IKEv2 configuration including certificates and keys will be permanently deleted. This cannot be undone!

Alternatively, you can manually remove IKEv2. Click here for instructions.

To manually remove IKEv2 from the VPN server, but keep the IPsec/L2TP and IPsec/XAuth ("Cisco IPsec") modes, follow these steps. Commands must be run as root.

Warning: All IKEv2 configuration including certificates and keys will be permanently deleted. This cannot be undone!

Rename (or delete) the IKEv2 config file:
```
mv /etc/ipsec.d/ikev2.conf /etc/ipsec.d/ikev2.conf.bak
```
Note: If you used an older version (before 2020-05-31) of the IKEv2 helper script or instructions, file /etc/ipsec.d/ikev2.conf may not exist. In this case, please instead remove the conn ikev2-cp section from file /etc/ipsec.conf.
(Important) Restart the IPsec service:
```
service ipsec restart
```

List certificates in the IPsec database:

certutil -L -d sql:/etc/ipsec.d

Example output:

Certificate Nickname                               Trust Attributes
                                                   SSL,S/MIME,JAR/XPI

IKEv2 VPN CA                                       CTu,u,u
($PUBLIC_IP)                                       u,u,u
vpnclient                                          u,u,u

Delete the Certificate Revocation List (CRL), if any:

crlutil -D -d sql:/etc/ipsec.d -n "IKEv2 VPN CA" 2>/dev/null

Delete certificates and keys. Replace "Nickname" below with each certificate's nickname. Repeat these commands for each certificate. When finished, list certificates in the IPsec database again, and confirm that the list is empty.
```
certutil -F -d sql:/etc/ipsec.d -n "Nickname"
certutil -D -d sql:/etc/ipsec.d -n "Nickname" 2>/dev/null
```

References

License

This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License
Attribution required: please include my name in any derivative and let me know how you have improved it!

41 KiB Raw Blame History

Guide: How to Set Up and Use IKEv2 VPN

Introduction

Set up IKEv2 using helper script

Configure IKEv2 VPN clients

Windows 7, 8, 10 and 11

OS X (macOS)

iOS

Android

Linux

Manage client certificates

List existing clients

Add a client certificate

Export configuration for an existing client

Delete a client certificate

Revoke a client certificate

Manually set up IKEv2 on the VPN server

Troubleshooting

IKEv2 disconnects after one hour

Unable to connect multiple IKEv2 clients

Other known issues

Remove IKEv2

References

License

41 KiB

Raw Blame History