Skip to main content

Overview

VPN as a Service (VPNaaS) provides IPsec-based site-to-site tunnel connectivity, enabling secure communication between your Xloud private cloud and remote data centers, branch offices, or other cloud environments. VPNaaS is available with XPCI deployments.
Prerequisites
  • Active project with member role or higher
  • At least one router with an external gateway configured
  • Remote site VPN endpoint details (peer IP, subnets, pre-shared key)
  • VPNaaS enabled by your administrator (enable_neutron_vpnaas: "yes")

Key Concepts

ConceptDescription
IKE PolicyDefines the Internet Key Exchange parameters used during Phase 1 negotiation — authentication algorithm, encryption algorithm, IKE version (v1 or v2), and key lifetime
IPsec PolicyDefines the Phase 2 parameters for the data channel — encryption algorithm, authentication algorithm, encapsulation mode (tunnel or transport), and Perfect Forward Secrecy (PFS) group
VPN ServiceAssociates a VPN with a specific router and subnet in your project
Endpoint GroupDefines the local or remote subnets that participate in the VPN tunnel
IPsec Site ConnectionCombines the IKE policy, IPsec policy, VPN service, and endpoint groups into an active tunnel to a remote peer

Supported Algorithms

ParameterSupported ValuesDefault
IKE Versionv1, v2v1
Authentication Algorithmsha1, sha256, sha384, sha512sha1
Encryption Algorithmaes-128, aes-192, aes-256, 3desaes-128
Phase 1 Negotiation Modemainmain
Lifetime60 — 86400 seconds3600
PFS Groupgroup2, group5, group14group5
Use IKEv2 with AES-256 and SHA-256 for production deployments. IKEv1 is supported for backward compatibility with legacy equipment.

Create a VPN Connection

Create an IKE Policy

Navigate to Project > Network > VPN > IKE Policies and click Add IKE Policy.
FieldValue
NameA descriptive name (e.g., ike-aes256-sha256)
IKE Versionv2
Encryption Algorithmaes-256
Authentication Algorithmsha256
PFS Groupgroup14
Lifetime3600

Create an IPsec Policy

Navigate to Project > Network > VPN > IPsec Policies and click Add IPsec Policy.
FieldValue
NameA descriptive name (e.g., ipsec-aes256-sha256)
Transform Protocolesp
Encryption Algorithmaes-256
Authentication Algorithmsha256
Encapsulation Modetunnel
PFS Groupgroup14

Create a VPN Service

Navigate to Project > Network > VPN > VPN Services and click Add VPN Service.
FieldValue
NameA descriptive name (e.g., vpn-to-branch-office)
RouterSelect the router with an external gateway
SubnetSelect the local subnet to expose through the tunnel

Create Endpoint Groups

Navigate to Project > Network > VPN > Endpoint Groups and create two endpoint groups:Local Endpoint Group:
FieldValue
Namelocal-subnets
Typesubnet
EndpointsSelect your local project subnet(s)
Remote Endpoint Group:
FieldValue
Nameremote-subnets
Typecidr
EndpointsEnter the remote subnet CIDRs (e.g., 192.168.1.0/24)

Create the IPsec Site Connection

Navigate to Project > Network > VPN > IPsec Site Connections and click Add IPsec Site Connection.
FieldValue
Nameconnection-to-branch
VPN ServiceSelect the VPN service created above
IKE PolicySelect the IKE policy created above
IPsec PolicySelect the IPsec policy created above
Local Endpoint Grouplocal-subnets
Peer Endpoint Groupremote-subnets
Peer Gateway IPPublic IP of the remote VPN device
Peer IDRemote peer identifier (typically the peer gateway IP)
Pre-Shared KeyShared secret agreed upon with the remote site
Click Create to establish the tunnel.
The connection appears in the list with status Active once both sides negotiate successfully.

Validation

Confirm the VPN tunnel is established and operational:
Navigate to Project > Network > VPN > IPsec Site Connections. The connection status should display Active.
StatusMeaning
ActiveTunnel is established and passing traffic
DownTunnel negotiation failed or peer is unreachable
Pending CreateConnection is being provisioned
ErrorConfiguration error — review IKE/IPsec parameters
Connection status is Active — the tunnel is operational.

Troubleshooting

Cause: The remote peer is unreachable or IKE/IPsec parameters do not match.Resolution:
  • Verify the peer gateway IP is reachable from the router’s external network
  • Confirm that IKE version, encryption, authentication, and PFS settings match on both sides
  • Check that the pre-shared key is identical on both endpoints
  • Verify security group rules allow UDP ports 500 and 4500 (IKE/NAT-T) and IP protocol 50 (ESP)
Cause: Endpoint group CIDRs do not match between the local and remote configurations.Resolution:
  • Verify the local endpoint group subnets match what the remote side expects as “remote” subnets
  • Verify the remote endpoint group CIDRs match the actual subnets behind the remote peer
  • Check routing tables on both sides to ensure traffic is directed through the tunnel

Next Steps

Security Groups

Configure firewall rules to control traffic flow through the VPN tunnel

Routers

Manage the routers that anchor your VPN services

Network Topology

Visualize your network layout including VPN connections

Key Manager

Store and manage VPN pre-shared keys and certificates securely