East-west Overlay Encryption

NVIDIA DOCA East-West Overlay Encryption Application

This document describes IPsec based strongSwan solution.

Important note for NVIDIA® BlueField®-2 DPUs only: If your target application utilizes 100Gb/s or higher bandwidth, where a substantial part of the bandwidth is allocated for IPsec traffic, please refer to the NVIDIA BlueField-2 DPUs Product Release Notes to learn about a potential bandwidth limitation. To access the relevant product release notes, please contact your NVIDIA sales representative.

IPsec is used to set up encrypted connections between different devices. It helps keep data sent over public networks secure. IPsec is often used to set up VPNs, and it works by encrypting IP packets as well as authenticating the packets' originator. IPsec contains the following main modules:

• Key exchange – a key is a string of random bytes that can be used for encryption and decryption of messages. IPsec sets up keys with a key exchange between the connected devices, so that each device can decrypt the other device's messages.
• Authentication – IPsec provides authentication for each packet which ensures that they come from a trusted source.
• Encryption – IPsec encrypts the payloads within each packet and possibly, based on the transport mode, the packet's IP header.
• Decryption – at the other end of the communication, packets are decrypted by the IPsec supported node.

IPsec supports two types of headers:

• Authentication header (AH) – AH protocol ensures that packets are from a trusted source. AH does not provide any encryption.
• Encapsulating security protocol (ESP) – ESP encrypts the payload for each packet as well as the IP header depending on the transport mode. ESP adds its own header and a trailer to each data packet.

IPsec support two types of transport mode:

• IPsec tunnel mode – used between two network nodes, each acting as tunnel initiator/terminator on a public network. In this mode, the original IP header and payload are both encrypted. Since the IP header is encrypted, an IP tunnel is added for network forwarding. At each end of the tunnel, the routers decrypt the IP headers to route the packets to their destinations.
• Transport mode – the payload of each packet is encrypted, but the original IP header is not. Intermediary network nodes are therefore able to view the destination of each packet and route the packet, unless a separate tunneling protocol is used.

strongSwan is an open-source IPsec-based VPN solution. For more information, please refer to strongSwan documentation.

IPsec full offload offloads both IPsec crypto (encrypt/decrypt) and IPsec encapsulation to the hardware. IPsec full offload is configured on the Arm via the uplink netdev.

The deployment model allows the IPsec offload to be transparent to the host with the benefits of securing legacy workloads (no dependency on host SW stack) and to zero CPU utilization on host.

IPsec full offload configuration works with and is transparent to OVS offload. This means all packets from OVS offload are encrypted by IPsec rules.

The following figure illustrates the interaction between IPsec full offload and OVS VXLAN offload.

Note: OVS offload and IPsec IPv6 do not work together.

1. Configure strongSwan IPsec offload using swanctl.conf configuration file.
2. Traffic is sent from the host through BlueField.
3. Using OVS, the packets are encapsulated on ingress using tunnel protocols (VXLAN for example) to match IPsec configuration by strongSwan.
4. Set by strongSwan configuration file, traffic will be encrypted using the hardware offload.
5. Egress flow is decryption first, decapsulation of the tunnel header and forward to the relevant physical function.

N/A

The following section provides information on manually configuring IPsec full offload in general and on using OVS IPsec with strongSwan specifically.

If you are working directly with the ip xfrm tool, use /opt/mellanox/iproute2/sbin/ip to benefit from IPsec full offload support. There are two parts in the configuration flow:

1. Enabling IPsec full offload mode.
2. Configuring the IPsec OVS bridge using one of three modes of authentication.

5.1. Enabling IPsec Full Offload

This section explicitly enables IPsec full offload on the Arm cores before setting up offload-aware IPSec tunnels.

Explicitly enable IPsec full offload on the Arm cores:

1. Disable mlx-regex. Run:
   Copy

   Copied!

               
   
               
   systemctl stop mlx-regex
           

2. Set IPSEC_FULL_OFFLOAD="yes" in /etc/mellanox/mlnx-bf.conf.
   Note:

   If IPSEC_FULL_OFFLOAD does not appear in /etc/mellanox/mlnx-bf.conf then you are probably using an old version of the BlueField image. Check the way of enabling IPsec full offload in a previous DOCA versions in the NVIDIA DOCA Documentation Archives.

3. Restart IB driver (rebooting also works). Run:
   Copy

   Copied!

               
   
               
   /etc/init.d/openibd restart
           

4. Re-enable mlx-regex. Run:
   Copy

   Copied!

               
   
               
   systemctl restart mlx-regex
           

   Note:

   To check if IPsec full offload is indeed enabled, verify that /sys/class/net/*/compat/devlink/ipsec_mode is full. If not (i.e., none), then something is wrong. Retry this procedure and try rebooting instead of restarting the IB driver.

   Note:

   To revert IPsec full offload mode, redo the procedure from step 1, only difference is to set IPSEC_FULL_OFFLOAD="no" in /etc/mellanox/mlnx-bf.conf.

5.2. Configuring OVS IPsec

This section configures OVS IPsec VXLAN tunnel which automatically generates the swanctl.conf files and runs strongSwan (the IPsec daemon). The following figure illustrates an example with two BlueField DPUs, Left and Right, operating with a secured VXLAN channel.

Two BlueField DPUs are required to build an OVS IPsec tunnel between the two hosts, Right and Left.

The OVS IPsec tunnel configures an unaware IPsec connection between the two hosts' InfiniBand devices. For the sake of this example, the host's InfiniBand network device is HOST_PF, and the DPU's host representor is PF_REP and the DPU's physical function PF. This example sets up the following variables on both Arms:

            

            
# host_ip1=1.1.1.1
# host_ip2=1.1.1.2
# HOST_PF=ens7np0
# ip1=192.168.50.1
# ip2=192.168.50.2
# PF=p0
# PF_REP=pf0hpf
        

            

            
# ibdev2netdev 
mlx5_0 port 1 ==> ens7np0 (Down)
mlx5_1 port 1 ==> ens8np1 (Down)
        

1. Configure IP addresses for the HOST_PFs of both hosts (x86):
   1. On host_1:
      Copy

      Copied!

                  
      
                  
      # ifconfig $HOST_PF $host_ip1/24 up
              

   2. On host_2:
      Copy

      Copied!

                  
      
                  
      # ifconfig $HOST_PF $host_ip2/24 up
              

      Note:

      Step 1 is the only command that is performed on the host, the rest of the commands are performed on the Arm (DPU) side.

2. Configure IP addresses for the PFs of both Arms:
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ifconfig $PF $ip1/24 up
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ifconfig $PF $ip2/24 up
              

3. Enable TC offloading for the PF. Run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # ethtool -K $PF hw-tc-offload on
           

4. Disable host PF as the port owner from Arm. Run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # mlxprivhost -d /dev/mst/mt${pciconf} --disable_port_owner r
           

   Note:

   To get ${pciconf}, run the following on the Arm:

   Copy

   Copied!

               
   
               
   # ls --color=never /dev/mst/ | grep --color=never '^m.*f0$' | cut -c 3-
           

   For example:

   Copy

   Copied!

               
   
               
   # mlxprivhost -d /dev/mst/mt41686_pciconf0 --disable_port_owner r
           

   
   

5. Start Open vSwitch. If your operating system is Ubuntu, run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # service openvswitch-switch start
           

   If your operating system is CentOS, run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # service openvswitch restart
           

   
   
6. Start OVS IPsec service. Run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # systemctl start openvswitch-ipsec.service
           

7. Set up OVS bridges in both DPUs. Run the following on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # ovs-vsctl add-br vxlan-br
   # ovs-vsctl add-port ovs-br $PF_REP
   # ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
           

   Note:

   Configuring other_config:hw-offload=true sets IPsec full offload. Setting it to false sets software IPsec. Make sure that IPsec devlink's mode is set back to none for software IPsec. This is done by reverting the configurations in Enabling IPsec Full Offload.

   Note:

   The MTU of the tunnel interface (PF) should be at least 50 bytes larger than the MTU of the endpoints of the tunnels above (PF_REP) to account for the size of the VXLAN tunnel header. For example, if the MTU of PF_REP is 1500 then the MTU of PF should at least be 1550. To configure the MTU of the PF:

   Copy

   Copied!

               
   
               
   # ifconfig $PF mtu $PF_MTU up
           

8. Set up IPsec tunnel on the OVS bridge. Three authentication methods are possible. Select your preferred method and follow the steps relevant to it. Note that the last two authentication methods require you to create certificates (self-signed or certificate authority certificates).
   Note:

   After the IPsec tunnel is set up using one of the three methods of authentication, strongSwan configuration is done automatically and the swanctl.conf files are generated and strongSwan runs automatically.

   
   

5.2.1. Authentication Methods

The following subsections detail the possible authentication methods for setting up the IPsec tunnel on the OVS bridge.

5.2.1.1. Pre-shared Key

This method configures OVS IPsec using a pre-shared key. You must select a pre-shared key, for example:

            

            
psk=swordfish
        

1. On Arm_1, run:
   Copy

   Copied!

               
   
               
   # ovs-vsctl add-port vxlan-br tun -- \
               set interface tun type=vxlan \
                             options:local_ip=$ip1 \
                             options:remote_ip=$ip2 \
                             options:key=100 \
                             options:dst_port=4789 \
                             options:psk=$psk
           

2. On Arm_2, run:
   Copy

   Copied!

               
   
               
   # ovs-vsctl add-port vxlan-br tun -- \
               set interface tun type=vxlan \
                             options:local_ip=$ip2 \
                             options:remote_ip=$ip1 \
                             options:key=100 \
                             options:dst_port=4789\
                             options:psk=$psk
           

5.2.1.2. Self-signed Certificate

This method configures OVS IPsec using self-signed certificates. You must generate self-signed certificates and keys. This example demonstrates how to generate self-signed certificates using ovs-pki but you may generate them in any other way while skipping step 1.

1. Generate self-signed certificates using ovs-pki:
   1. On Arm_1, run:
      Copy

      Copied!

                  
      
                  
      # ovs-pki req -u host_1
      # ovs-pki self-sign host_1
              

      After running this code you should have host_1-cert.pem and host_1-privkey.pem.

   2. On Arm_2, run:
      Copy

      Copied!

                  
      
                  
      # ovs-pki req -u host_2
      # ovs-pki self-sign host_2
              

      After running this code you should have host_2-cert.pem and host_2-privkey.pem.

2. Configure the certificates and private keys:
   1. Copy the certificate of Arm_1 to Arm_2, and the certificate of Arm_2 to Arm_1.
   2. On each machine, move both host_1-privkey.pem and host_2-cert.pem to /etc/swanctl/x509/ if on Ubuntu, or /etc/strongswan/swanctl/x509/ if on CentOS.
   3. On each machine, move the local private key (host_1-privkey.pem on Arm_1 and host_2-privkey.pem on Arm_2) to /etc/swanctl/private if on Ubuntu, or /etc/strongswan/swanctl/private if on CentOS.
3. Set up OVS other_config on both sides.
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl set Open_vSwitch . other_config:certificate=/etc/swanctl/x509/host_1-cert.pem \
        other_config:private_key=/etc/swanctl/private/host_1-privkey.pem
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl set Open_vSwitch . other_config:certificate=/etc/swanctl/x509/host_2-cert.pem \
        other_config:private_key=/etc/swanctl/private/host_2-privkey.pem
              

4. Set up the VXLAN tunnel:
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-port vxlan-br vxlanp0 -- set interface vxlanp0 type=vxlan options:local_ip=$ip1 \
        options:remote_ip=$ip2 options:key=100 options:dst_port=4789 \
        options:remote_cert=/etc/swanctl/x509/host_2-cert.pem
      # service openvswitch-switch restart
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-port vxlan-br vxlanp0 -- set interface vxlanp0 type=vxlan options:local_ip=$ip2 \
        options:remote_ip=$ip1 options:key=100 options:dst_port=4789 \
        options:remote_cert=/etc/swanctl/x509/host_1-cert.pem
      # service openvswitch-switch restart
              

   Note:

   In steps 3 and 4, if you are in CentOS you must change the path of the certificates to /etc/strongswan/swanctl/x509/ and the path of the private keys to /etc/strongswan/swanctl/private.

5.2.1.3. CA-signed Certificate

This method configures OVS IPsec using self-signed certificates. You must generate self-signed certificates and keys. This example demonstrates how to generate self-signed certificates using ovs-pki but you may generate them in any other way while skipping step 1.

1. Generate CA-signed certificates using ovs-pki. For this method, all the certificates and the requests must be in the same directory during the certificate generating and signing. This example refers to this directory as certsworkspace.
   1. On Arm_1, run:
      Copy

      Copied!

                  
      
                  
      # ovs-pki init --force
      # cp /var/lib/openvswitch/pki/controllerca/cacert.pem <path_to>/certsworkspace
      # cd <path_to>/certsworkspace
      # ovs-pki req -u host_1
      # ovs-pki sign host1 switch
              

      After running this code, you should have host_1-cert.pem, host_1-privkey.pem, and cacert.pm in the certsworkspace folder.

   2. On Arm_2, run:
      Copy

      Copied!

                  
      
                  
      # ovs-pki init --force
      # cp /var/lib/openvswitch/pki/controllerca/cacert.pem <path_to>/certsworkspace
      # cd <path_to>/certsworkspace
      # ovs-pki req -u host_2
      # ovs-pki sign host_2 switch
              

      After running this code, you should have host_2-cert.pem, host_2-privkey.pem, and cacert.pm in the certsworkspace folder.

2. Configure the certificates and private keys:
   1. Copy the certificate of Arm_1 to Arm_2 and the certificate of Arm_2 to Arm_1.
   2. On each machine, move both host_1-privkey.pem and host_2-cert.pem to /etc/swanctl/x509/ if on Ubuntu, or /etc/strongswan/swanctl/x509/ if on CentOS.
   3. On each machine, move the local private key (host_1-privkey.pem if on Arm_1 and host_2-privkey.pem if on Arm_2) to /etc/swanctl/private if on Ubuntu, or /etc/strongswan/swanctl/private if on CentOS.
   4. On each machine, copy cacert.pem to the x509ca directory under /etc/swanctl/x509ca/ if on Ubuntu, or /etc/strongswan/swanctl/x509ca/ if on CentOS.
3. Set up OVS other_config on both sides.
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl set Open_vSwitch . \
              other_config:certificate=/etc/strongswan/swanctl/x509/host_1.pem \
              other_config:private_key=/etc/strongswan/swanctl/private/host_1-privkey.pem \
              other_config:ca_cert=/etc/strongswan/swanctl/x509ca/cacert.pem
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl set Open_vSwitch . \
              other_config:certificate=/etc/strongswan/swanctl/x509/host_2.pem \
              other_config:private_key=/etc/strongswan/swanctl/private/host_2-privkey.pem \
              other_config:ca_cert=/etc/strongswan/swanctl/x509ca/cacert.pem
              

4. Set up the tunnel:
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-port vxlan-br vxlanp0 -- set interface vxlanp0 type=vxlan options:local_ip=$ip1 \
      options:remote_ip=$ip2 options:key=100 options:dst_port=4789 \ options:remote_name=host_2
      # service openvswitch-switch restart
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-port vxlan-br vxlanp0 -- set interface vxlanp0 type=vxlan options:local_ip=$ip2 \
      options:remote_ip=$ip1 options:key=100 options:dst_port=4789 \ options:remote_name=host_1
      # service openvswitch-switch restart
              

   Note:

   In steps 3 and 4, if you are in CenOS you must change the path of the certificates to /etc/strongswan/swanctl/x509/, the path of the CA certificate to /etc/strongswan/swanctl/x509ca/, and the path of the private keys to /etc/strongswan/swanctl/private/.

5.4. Configuring OVS IPsec Using strongSwan Manually

This section configures an OVS VXLAN tunnel which then uses swanctl.conf files and runs strongSwan (the IPsec daemon) manually.

1. Build a VXLAN tunnel over OVS and connect the PF representor to the same OVS bridge.
   1. On Arm_1:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-br vxlan-br
      # ovs-vsctl add-port vxlan-br PF_REP
      # ovs-vsctl add-port vxlan-br vxlan11 -- set interface vxlan11 type=vxlan options:local_ip=$ip1 \
               options:remote_ip=$ip2 options:key=100 options:dst_port=4789 \
      # ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
              

   2. On Arm_2:
      Copy

      Copied!

                  
      
                  
      # ovs-vsctl add-br vxlan-br
      # ovs-vsctl add-port vxlan-br PF_REP
      # ovs-vsctl add-port vxlan-br vxlan11 -- set interface vxlan11 type=vxlan options:local_ip=$ip2 \
               options:remote_ip=$ip1 options:key=100 options:dst_port=4789 \
      # ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
              

2. If your operating system is Ubuntu, run on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   service openvswitch-switch start
           

   If your operating system is CentOS, run:
   Copy

   Copied!

               
   
               
   service openvswitch restart
           

   
   
3. Enable TC offloading for the PF. Run on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # ethtool -K $PF hw-tc-offload on
           

4. Disable host PF as the port owner from Arm. Run on both Arm_1 and Arm_2:
   Copy

   Copied!

               
   
               
   # mlxprivhost -d /dev/mst/mt${pciconf} --disable_port_owner r
           

   Note:

   To get ${pciconf}, run the following on the DPU:

   Copy

   Copied!

               
   
               
   # ls --color=never /dev/mst/ | grep --color=never '^m.*f0$' | cut -c 3-
           

   For example:

   Copy

   Copied!

               
   
               
   # mlxprivhost -d /dev/mst/mt41686_pciconf0 --disable_port_owner r
           

   
   

5. Configure theswanctl.conf files for each machine. See section swanctl.conf Files.
   Note:

   Each machine should have exactly one .swanctl.conf file in /etc/swanctl/conf.d/.

6. Load the swanctl.conf files and initialize strongSwan. Run:
   1. On the Arm_2, run:
      Copy

      Copied!

                  
      
                  
      systemctl restart strongswan-starter.service
      swanctl --load-all
              

   2. On the Arm_1, run:
      Copy

      Copied!

                  
      
                  
      systemctl restart strongswan-starter.service
      swanctl --load-all
      swanctl -i --child bf
              

Now the IPsec connection should be established.

5.5. swanctl.conf Files

strongSwan configures IPSec HW full offload using a new value added to its configuration file swanctl.conf. The file should be placed under sysconfdir which by default can be found at /etc/swanctl/swanctl.conf. The terms Left (BFL) and Right (BFR), in reference to the illustration under Application Architecture, are used to identify the two nodes (or machines) that communicate.

In this example, 192.168.50.1 is used for the left PF uplink and 192.168.50.2 for the right PF uplink.

            

            
connections {
   BFL-BFR {
      local_addrs  = 192.168.50.1
      remote_addrs = 192.168.50.2
 
      local {
        auth = psk
        id = host1
      }
      remote {
        auth = psk
        id = host2
      }
 
      children {
         bf {
            local_ts = 192.168.50.1/24 [udp/4789]
            remote_ts = 192.168.50.2/24 [udp/4789]
            esp_proposals = aes128gcm128-x25519
            mode = transport
            policies_fwd_out = yes
            hw_offload = full
         }
      }
      version = 2
      mobike = no
      reauth_time = 0
      proposals = aes128-sha256-x25519
   }
}
 
secrets {
   ike-BF {
      id-host1 = host1
      id-host2 = host2
      secret = 0sv+NkxY9LLZvwj4qCC2o/gGrWDF2d21jL
   }
   }
        

The BFB installation will place two example swanctl.conf files for BFL and BFR (BFL.swanctl.conf and BFR.swanctl.conf respectively) in the strongSwan conf.d directory. Each node should have only one swanctl.conf file in its strongSwan conf.d directory.

Note that:

• "hw_offload = full" is responsible for configuring IPSec HW full offload
• Full offload support has been added to the existing hw_offload field and preserves backward compatibility.

  For your reference:

  Value	Description
  no	Do not configure HW offload, fail if not supported
  yes	Configure crypto HW offload if supported by the kernel, fail if not supported (Existing)
  auto	Configure crypto HW offload if supported by the kernel, do not fail (Existing)
  full	Configure full HW offload if supported by the kernel, fail if not supported (New)

• Whenever the value of hw_offload is changed, strongSwan configuration must be reloaded.
• Switching to crypto HW offload requires setting up devlink/ipsec_mode to none beforehand.
• Switching to full HW offload requires setting up devlink/ipsec_mode to full beforehand.
• [udp/4789] is crucial for instructing strongSwan to IPSec only VXLAN communication.
• Full HW offload can only be done on what is streamed over VXLAN.

Mind the following limitations:

Refer to the following documents:

• NVIDIA DOCA Installation Guide for Linux for details on how to install BlueField-related software.
• NVIDIA DOCA Troubleshooting Guide for any issue you may encounter with the installation, compilation, or execution of DOCA applications.

6.1. Running strongSwan Example

Notes:

• IPsec daemons are started by systemd strongswan-starter.service
• Use systemctl [start | stop | restart] to control IPsec daemons through strongswan-starter.service. For example, to restart, run:
  Copy

  Copied!

              
  
              
  systemctl restart strongswan-starter.service
          

  This command effectively does the same thing as ipsec restart.
  Note:

  Do not use the ipsec script (located under /usr/sbin/ipsec) to restart/stop/start the IPsec connection.

  
  

This subsection explains how to configure and set an IPsec connection using the script. To configure the IPsec connection, you need two DPUs, referred to as the initiator and receiver machines. There are no differences between the two machines except that the initiator is the one that initiates the connection between the two (and should run the script after the receiver).

The script is located under /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh.

6.1.1. Script Parameters

6.1.2. Using JSON Parameters File

In this method, you must configure the parameters file and the then run the script:

1. Configure the JSON parameters file located under /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption_params.json or create a JSON file according to the template of east_west_overlay_encryption_params.json for the script according to the explanation under Script Parameters.
2. Run the script on the receiver's DPU with the JSON file:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=r --json=/opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption_params.json
           

3. Run the script on the initiator's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=i --json=/opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption_params.json
           

   You may now send encrypted data over the PF interface (192.168.50.[1|2]) configured for VXLAN.

6.1.3. Passing Parameters on Command Line

In this method, you do not need to configure the parameters file and can run the script with the appropriate parameters.

6.1.3.1. Passing Parameters for Pre-shared Key Authentication Method

1. Run the script on the receiver's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=r --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=psk --preshared_key=PRESHARED_KEY
           

2. Run the script on the initiator's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=i --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=psk --preshared_key=PRESHARED_KEY
           

6.1.3.2. Passing Parameters for Self-signed Certificates Authentication Method

1. Run the script on the receiver's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=r --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=ssc --initiator_cert_path=INITIATOR_CERT_PATH --receiver_cert_path=RECEIVER_CERT_PATH --receiver_key_path=RECEIVER_KEY_PATH
           

2. Run the script on the initiator's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=i --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=ssc --initiator_cert_path=INITIATOR_CERT_PATH --receiver_cert_path=RECEIVER_CERT_PATH --initiator_key_path=INITIATOR_KEY_PATH
           

6.1.3.3. Passing Parameters for CA Certificates Authentication Method

1. Run the script on the receiver's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=r --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=ca --initiator_cert_path=INITIATOR_CERT_PATH --receiver_cert_path=RECEIVER_CERT_PATH --receiver_key_path=RECEIVER_KEY_PATH --receiver_cacert_path=RECEIVER_CACERT_PATH --initiator_cn=INITIATOR_CN
           

2. Run the script on the initiator's DPU:
   Copy

   Copied!

               
   
               
   /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh --side=i --initiator_ip_addr=INITIATOR_IP_ADDRESS --receiver_ip_addr=RECEIVER_IP_ADDRESS --port_num=PORT_NUM \
   --auth_method=ssc --initiator_cert_path=INITIATOR_CERT_PATH --receiver_cert_path=RECEIVER_CERT_PATH --initiator_key_path=INITIATOR_KEY_PATH --initiator_cacert_path=INITIATOR_CACERT_PATH --receiver_cn=RECEIVER_CN
           

For help and usage, run the script with --help/-h flag:

            

            
/opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh -h
        

6.2. Building strongSwan

1. strongSwan IPsec full version can be found here (tag: 5.9.6bf).
2. Install dependencies mentioned here. libgmp-dev is missing from that list, so make sure to install that as well.
3. Git clone https://github.com/Mellanox/strongswan.git.
4. Git checkout BF-5.9.6.
5. Run autogen.sh within the strongSwan repo.
6. Run the following:
   Copy

   Copied!

               
   
               
   configure --enable-openssl --disable-random --prefix=/usr/local --sysconfdir=/etc --enable-systemd
   make
   make install
           

   Notes:
   • --enable-systemd enables the systemd service for strongSwan present inside the GitHub repo (see step 3) at init/systemd-starter/strongswan-starter.service.in. This service file is meant for Ubuntu, Debian and Yocto distributions. For CentOS, the contents of the above file must be replaced by the one present in systemd-conf/strongswan-starter.service.in.centos (inside the GitHub repo) before running the configure script above.
   • When building strongSwan on your own, the openssl.cnf.mlnx file, required for PK and RNG HW offload via OpenSSL plugin, is not installed. It must be copied over manually from GitHub repo inside the openssl-conf directory. See section "Running Strongswan Example" for important notes.
   • The openssl.cnf.mlnx file references PKA engine shared objects. libpka (version 1.3 or later) and openssl (version 1.1.1) must be installed for this to work.

6.3. Reverting IPsec Configuration

To destroy IPsec configuration, run the following on both machines:

            

            
/opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh -d
        

• /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption.sh
• /opt/mellanox/doca/applications/east_west_overlay_encryption/bin/east_west_overlay_encryption_params.json

Notice

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation nor any of its direct or indirect subsidiaries and affiliates (collectively: “NVIDIA”) make no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assume no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.

NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.

Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.

NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.

NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.

No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.

Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.

THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

Trademarks

NVIDIA, the NVIDIA logo, and Mellanox are trademarks and/or registered trademarks of Mellanox Technologies Ltd. and/or NVIDIA Corporation in the U.S. and in other countries. The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world¬wide basis. Other company and product names may be trademarks of the respective companies with which they are associated.

Copyright

© 2022 NVIDIA Corporation & affiliates. All rights reserved.