Overview
VPN as a Service (VPNaaS) provides IPsec-based site-to-site tunnel connectivity, enabling secure communication between your Polystack private cloud and remote data centers, branch offices, or other cloud environments. VPNaaS is available with Polystack deployments.Prerequisites
- Active project with
memberrole 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
Supported Algorithms
- IKE Policy
- IPsec Policy
Create a VPN Connection
- Dashboard
- CLI
Create an IKE Policy
Navigate to Network > VPNs (IKE Policies tab) and click Create.
Create an IPsec Policy
Navigate to Network > VPNs (IPsec Policies tab) and click Create.
3
Create a VPN Gateway
Navigate to Network > VPNs (VPN Gateways tab) and click Create.
Create Endpoint Groups
Navigate to Network > VPNs (VPN EndPoint Groups tab) and create two endpoint groups:Local Endpoint Group:
Remote Endpoint Group:
Create the IPsec Site Connection
Navigate to Network > VPNs (IPsec Site Connections tab) and click Create.
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:- Dashboard
- CLI
Navigate to Network > VPNs (IPsec Site Connections tab). The connection status should display Active.
Connection status is Active — the tunnel is operational.
Troubleshooting
Connection stuck in DOWN status
Connection stuck in DOWN status
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)
Tunnel established but no traffic flows
Tunnel established but no traffic flows
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
