Connecnt Google Compute Engine to local Network

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
markus78566
Posts: 2
Joined: Fri May 15, 2020 9:14 pm

Connecnt Google Compute Engine to local Network

Post by markus78566 » Sat May 16, 2020 7:03 am

Hello, as part of my thesis I would like to connect a local network with the Google Compute Eninge to build a distributed Kubernetes cluster. I have followed the tutorial linked here (https://www.softether.org/4-docs/2-howt ... Bridge_VPN) and have set up all steps up to point 9.4.1 (https://www.softether.org/4-docs/1-manu ... igurations). I now have a VPN server in the cloud and a VPN bridge in my local network.

II have no experience in building a VPN network so I am a bit lost as I now have to create the Cascade Connection with a Local Bridge. And in the next step the build a LAN-to-LAN Bridge VPN between Cloud and On-premise. Is there perhaps already another tutorial which describes the steps in more detail or can anyone here help me how to do this on the first implementation? (For your information, all my machines run under Ubuntu)

drkrool
Posts: 97
Joined: Mon May 25, 2020 4:38 am
Location: Quebec, Canada

Re: Connecnt Google Compute Engine to local Network

Post by drkrool » Thu May 28, 2020 11:15 am

The cascade connection on the bridge would connects to the vpn server in the cloud and would essentially be the same as putting the network card you choosed in the network of your cloud.

I did a similar project using a vpn bridge. My friend had a IPTV provider with a few boxes so I took one home. He made a vpnserver in his network, I did a vpnbridge on mine, connected to his server via cascade and hooked the IPTV box on the lan card that had the bridge and the service was working almost flawlessly (anything that wasn't super latency dependent).

Keep in mind that in this example, his network had a router doing the NAT and he had a DHCP server also. When using the "cloud", you most likely don't have theses so using the securenat feature on the vpnserver is tempting but costly in ressources.

Post Reply