The platform enables you to create site-to-site VPNs between virtual datacenter networks, and other entities.
To work with VPNs, go to Virtual datacenters → select a Virtual datacenter → Network → VPN
Initial support for VPNs requires you to create a VPN site for each connected virtual datacenter. Both sites of a VPN must have the same encryption and authentication settings, and inverse local and remote network configurations.
The following table describes VPN functionality in the providers.
AWS | VMware NSX | |
---|---|---|
Encryption | AES | AES, AES256, Triple DES, AES-GCM |
Perfect forward secrecy enabled | mandatory | optional |
DH group | DH2 | DH2, DH5, DH14 |
Authentication | PSK (mandatory) | PSK (mandatory) |
It may be helpful to complete this table to record your network values before you create your VPN:
VDC name | VDC1 ________________ | VDC2 ________________ |
---|---|---|
VPN site name | ||
NAT IP | ||
Private networks |
For example:
VDC name | VDC1 ________________ | VDC2 ________________ |
---|---|---|
VPN site name | axsdTOaxsd2 | axsd2TOaxsd |
NAT IP | 10.200.100.8 | 10.200.100.23 |
Private networks |
|
|
To connect private cloud with public cloud, define the VPN site in private cloud first.
To create the first VPN site:
- Go to Virtual datacenters → select a Virtual datacenter → Network → VPN
- Click the + Add button and enter the VPN details
The platform will create the VPN site.
To create the other VPN site in another VDC:
- Select the Virtual datacenter
- Add another VPN site using the remote network configuration of the first VPN site as the local values.
So in this example, the local network endpoint for the second VPN site would be 10.200.100.23 and the local network would be 192.168.200.0/24. The remote endpoint would be 10.200.100.8 and the remote network would be 192.168.0.0/24.
After you have created both VPN sites, on the VPNs tab, to check the connection in the network virtualization system, click the Check link in the VPN Status column, or when you edit a VPN site.