--- name: vmwaresolutions-vpn title: IBM Cloud VPN overview description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026. last-updated: 2025-10-24 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # IBM Cloud VPN overview {: #interconnectivity-vpn} As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026. {: deprecated} IBM Cloud® Virtual Private Network (VPN) for VPC service offers two types of VPNs: * **Site-to-site gateways** - This VPN type connects your on-premises network to the IBM Cloud VPC network. * **Client-to-site servers** - This VPN type allows clients on the internet to connect to VPN servers, while still maintaining secure connectivity. IBM Cloud VPN Gateway for VPC provides a simple yet powerful solution for highly scalable and robust site-to-site VPN gateways. With this service, you can create site-to-site VPN tunnels for secure, encrypted connectivity. Also, you connect from on-premises sites to IBM Cloud through a VPN gateway on an IBM Cloud VPC, and a peer gateway on-premises. For more information, see [About site-to-site VPN gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn&format=markdown). IBM Cloud Client VPN for VPC provides an open source compatible client-to-site VPN solution that allows users to connect to IBM Cloud resources through secure, encrypted connections. Whether you want to connect to access or manage your workloads that are running in VPC Virtual Servers or VMware® workloads, you can use the OpenVPN-based client-to-site VPN solution for remote access. For more information, see [About client-to-site VPN servers](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview&format=markdown). ## Considerations with VMware Cloud Foundation solution in VPC {: #interconnectivity-vpn-vcf-considerations} When you use the VMware virtual machines (VMs) on the VPC subnet architecture, your VMs are attached to VPC subnets and the routing behaves in the same way as with VPC Virtual Servers. The VPC subnets are provisioned from the zone prefix, and the routing works between the VPC without any required changes. You can use both IBM Cloud VPN Gateway for VPC and IBM Cloud Client VPN for VPC with this solution as described in the documentation previously listed. ![VPNaaS with VMware on VPC](../../images/vpc-vcf-diagrams-dl-sub-arch.svg "VPNaaS with VMware on VPC"){: caption="VPNaaS with VMware on VPC" caption-side="bottom"} When you use NSX® on your VMware solution on VPC, the VMs are attached on the NSX overlay segments. They use an IP address range or prefix, which is reachable through VPC route that points to NSX Tier-0 private uplink VIP as described in the [VMware NSX logical routing on VPC](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-vcf-nsx-t-vpc-routing&format=markdown) topic. You can use both IBM Cloud VPN Gateway for VPC and IBM Cloud Client VPN for VPC with this solution as described in the documentation previously listed. ![VPNaaS with VMware on VPC with NSX](../../images/vpc-vcf-diagrams-dl-nsx-t-arch.svg "VPNaaS with VMware on VPC with NSX"){: caption="VPNaaS with VMware on VPC with NSX" caption-side="bottom"} When you use IBM Cloud Client VPN for VPC, you must add VPN routes that are advertised to the VPN clients for the NSX overlay destinations. Set the VPC routes to the same destination and pointing to the NSX Tier-0 Private Uplink VIP. In NSX Tier-0, ensure that you have a static route for the prefix route of your VPN Client IPv4 address pool, which points to the default gateway of the uplink subnet. With IBM Cloud VPN Gateway for VPC, it is recommended to use route-based tunnels, as described in the [VPN Gateway for VPC features](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn&format=markdown#vpn-features) topic. Ensure that you define static routes at the on-premises VPN gateway toward NSX overlay prefixes. Set the VPC routes to the same destination and pointing to the NSX Tier-0 Private Uplink VIP. For on-premises destinations, VPC routes must point to the VPN Tunnel. In NSX Tier-0, ensure that your private routes are pointing to the default gateway of the uplink subnet. ## Related links {: #interconnectivity-vpn-vcf-links} * [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started&format=markdown) * [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers&format=markdown) * [IBM Cloud Direct Link overview](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl&format=markdown) * [IBM Cloud Transit Gateway overview](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started&format=markdown) * [IBM Cloud VPC VPN overview](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-overview&format=markdown) * [VPC IaaS endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpc&format=markdown#infrastructure-as-a-service-iaas-endpoints) * [VCF for VPC overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-vcf-ovw&format=markdown)