This page provides interoperability guides and vendor-specific notes for on-premises third-party VPN devices or services you can use to connect to Cloud VPN.
Each Interop guide offers specific instructions for connecting the third-party VPN solution to Cloud VPN.
If the third-party solution supports dynamic (BGP) routing, the guide includes configuration instructions for Cloud Router.
- Most on-premises VPN devices should be compatible with Cloud VPN. For general information about configuring on-premises VPN devices, see Configuring the On-premises VPN Gateway.
- For a list of IKE ciphers and other configuration parameters used by Cloud VPN, see Supported IKE Ciphers.
Interop guides by vendor
This section lists interoperability guides by vendor in alphabetical order. Each guide covers how to use that vendor's VPN gateway solution with Cloud VPN.
- Alibaba Cloud VPN Gateway without redundancy — supports static routes only
- Amazon Web Services — supports static routes or dynamic routing with Cloud Router
- Cisco ASA — supports static routes only
- Cisco ASR
- Check Point security gateway
- Fortinet FortiGate 300C — supports static routes or dynamic routing with Cloud Router
- Microsoft Azure — supports static routes only
- Palo Alto Networks PA-3020 — supports static routes or dynamic routing with Cloud Router
- VyOS — supports static routes or dynamic routing with Cloud Router
If your VPN gateway runs Cisco IOS XE, make sure you're running version 16.6.3 (Everest) or later. Earlier versions have known problems with Phase 2 rekey events, which results in tunnels going down for a few minutes every few hours.
When using Cisco ASA devices with a Cloud VPN tunnel, you cannot configure more than one IP address range (CIDR block) for each of the local and remote traffic selectors. This is because Cisco ASA devices use a unique Security Association (SA) for each IP address range in a traffic selector, while Cloud VPN uses a single SA for all IP ranges in a traffic selector. See traffic selectors for more information.