I hereby claim:
- I am CyberKoz on github.
- I am dkhenry (https://keybase.io/dkhenry) on keybase.
- I have a public key whose fingerprint is D58B 130C 23A2 5FC8 DE08 5A9E B316 1C27 4369 1D8F
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
This is a sequence of steps that will allow you to run your own VPN on GCP. It will expose two VPN protocols. The first is L2TP/IPSec. This is the default VPN protocol for most operating systems and has built in clients for all your devices. The one serious limitation of this is that is must communicate over very well known ports ( 500, 1701 ). Its common for those ports to be blocked by restrictive firewalls so this will also configure an OpenVPN server that will listen on port 443. This makes your VPN connection look exactly like a HTTPS connection. Its unlikely that port 443 will be blocked to GCP or any other cloud provider since that is a very common way to host TLS secured websites
Choose CentOS 7, and a f1.micro instance
Allow 500/udp; 4500/udp; 1701/tcp; 1194/udp; 443/tcp
tag that rule with "vpn" or another identifier.
Tag the instance with "vpn" or the identifier listed above
We want to show you a few of the primitives github provides to do project management Github has a simplified workflow model, but I wanted to cover the full range of activities that you would need to do and show how some of those concepts translate into GitHub. What I am presenting today is going to be simplistic and that is so we can focus on the tool For larger projects we make a few changes, but the principles are going to remain.
This is also going to cover a lot of material and I will be moving pretty fast to cover as much as I can in the time we have, but I also want to be able to dive deep on any topic