Setting up site-to-site on Google Cloud (VPC peering)


Note: If you are unsure whether site-to-site is the best solution for you, please take a look at our Remote Access article first. What is more, if your device/service supports SHA256 and DH group 14, it is recommended to use these settings instead.

 

You can utilize VPC peering on the Google Cloud Platform with NordLayer, by exporting the route of your NordLayer network to the VPC you are peering with and subsequently importing it in the peered VPC.

This allows for a design where only a single tunnel is required from NordLayer to the "shared" Google Cloud VPC. Other peered VPC must know how to get back to NordLayer subnets by having the NordLayer route in the routing table.

Screenshot_2021-05-26_at_12.52.30.png

Screenshot_2021-05-26_at_12.53.02.png

Screenshot_2021-05-26_at_12.52.43.png

 

Ending note:

In order to finalize the site-to-site setup on our end, we will need these values:

  • Pre-shared key - you can generate it or we can provide it
  • Encryption  details (AES, SHA and DH group) - AES256, SHA256 and DH group 14 are recommended (also must support IKEv2)
  • Remote gateway/router public IP (must be reachable while connected to the dedicated server)
  • Remote subnet and mask (the subnet is used in your local network)

Lastly, it is important to know what device or cloud network is being used (Ubiquiti, Fortigate, AWS, Google Cloud, etc.)

You can provide all of these values to us securely via privnote.com

In case you are experiencing different results, make sure that you have you carefully gone through all the steps. Having said that, in case the issue persists please feel free to contact our 24/7 customer support team.


Return to top