User Guide - Site-to-Site Private Connectivity

Owen has completed the signup process as shown here. During the signup process, Owen selects technop.openvpn.cloud as the web domain for the user portal. This domain uniquely identifies the VPN that will be set up by Owen and is used by Connect Client applications (VPN Client software) to identify the VPN that it needs to connect to.

Owen wants to create a Full-Mesh private Network among two private Networks (represented by AWS VPC in separate AWS Regions) and enable Remote Access to those Networks for himself and employees.

Owen wants to create a full-mesh private network among two private networks (represented by AWS VPC in separate AWS Regions) and enable remote access to those networks for himself and employees.

North California network is using the 172.31.0.0/16 subnet. Owen needs to configure this as the Network subnet that needs to be available from CloudConnexa.

Owen configures both networks using the Admin portal as shown below. See, Adding A Network.

Owen installs Connector on one of the instances in the network and uses the respective Connector profile to get the instance connected to CloudConnexa. See, Installing Network Connector – Linux.

Prior to adding routes, Owen disables ‘Source/Destination’ Check on the Network interface of the instance running the Connector.

He enables forwarding in the Linux kernel of the instance running the Connector.

From the command line he enters:

            sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/g' /etc/sysctl.conf
sysctl -p
         

Next, he adds routes, in the route table associated with the VPC, for the Oregon Network and the CloudConnexa WPC subnets using the instance running the Connector as the next-hop Target.

Owen installs a Connector on one of the instances in the Network and uses the respective Connector Profile to get the instance connected to CloudConnexa. See, Installing Network Connector – Linux.

Prior to adding routes, Owen disables Source/Destination Check on the Network interface of the instance running the Connector.

He enables forwarding in the Linux kernel of the instance running the Connector

From the command line he enters:

            sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/g' /etc/sysctl.conf
sysctl -p
         

Next, he adds routes, in the route table associated with the VPC, for the North California Network and the CloudConnexa WPC subnets using the instance running the Connector as the next-hop Target.

Now, Owen can connect his laptop to CloudConnexa using the Connect Client (see importing Profile section, User Guide – Configuring a VPN for Secure Access to Internet), and reach any instance in both of the private Networks. As shown below, instances in private Networks can also reach each other.