7 ms·
The client side of the VPN is pretty straightforward. It's a closed source program that basically creates a `tun` device. So I run it in a VM so it can't harm m
by anonymouscowar1 13y ago
The client side of the VPN is pretty straightforward. It's a closed source program that basically creates a `tun` device. So I run it in a VM so it can't harm my home machine, and just use iptables to route work traffic to it. No idea what is needed on the infrastructure side.
No idea how much the video costs either, but my employer is a Fortune 500 company.
- jlgaddis 13y agoThere's also "OpenConnect", an open source replacement for Cisco's VPN client. On the infrastructure side, you'll have a Cisco router or firewall providing remote access VPN services.
- anonymouscowar1 13y agoYeah, the problem with OpenConnect is that every time they bump the 'cstub' binary on the cisco remote end, OpenConnect stops working until you grab the new one somehow. ('cstub' is a wonderful program that is downloaded over HTTP and runs as root. It's supposed to monitor security, or something. I did mention I run this on a VM, right?)