So the anyconnect client prevents forward of traffic from a VM to the VPN, which means virtual machines and docker containers which rely upon NAT won't work. OpenConnect allows you to get around this as it doesn't enforce ipfw rules upon you.
OpenConnect is a command-line client for Cisco's AnyConnect SSL VPN.
Here's how to get it set up on Mac OS X:
-
OpenConnect can be installed via homebrew:
brew update brew install openconnect -
(Optional) Running openconnect requires sudo, presumably because it affects resolution of DNS. So, I added password-less sudo ability for the openconnect command.
sudo visudo -f /etc/sudoers
And added this line:
%admin ALL=(ALL) NOPASSWD: /usr/local/bin/openconnect
-
(Optional) When connecting to your SSL VPN, openconnect may complain about a "self-signed certificate" being in the chain and force you to explicitly accept it every time. The self-signed cert is actually the root certficate and (hopefully) is one with implicit trust (i.e. trusted by browsers), so we can safely trust it by specifying the CA file after exporting it from KeyChain:
-
Determine the name your root certificate (i.e. visit your SSL VPN in Chrome (https://vpn.ncsasports.org), click the green lock, click "Certificate Information")
-
Open the Keychain Access App
-
Search the "System Roots" keychain to find your root certificate and select it
-
File>Export Items...the certificate as a.pemfile somewhere on your hard drive (I put it in~/.ssh/<certificate name>.pem -
Connect!
sudo openconnect --user=<VPN username> --cafile=<.pem file from step 4.3> <your vpn hostname>The only thing you should be prompted for is your VPN password. I added the command to my aliases file.
-
To disconnect, just Ctrl-c in the window where you started the VPN connection.
I had an incident after an unclean VPN exit where later the VPN hostname could not be found. I guess the DNS resolver was messed up. I was forced to reboot to fix it so I could reconnect to the VPN.