![viscosity vpn viscosity vpn](http://dettmer.maclab.org/i/vpntoggler.png)
I've confirmed this issue in testing with Viscosity v1.7.3 and 1.7.4.
#VISCOSITY VPN WINDOWS#
We have disabled client-side caching on Windows clients so auto-reconnecting is only an issue with Viscosity clients. Running through the 10 connections of course involves the user missing or ignoring the Duo notifications on their mobile but the disconnects generally happen within the first 2 re-connection attempts. My issue is that when Viscosity does it's 10 re-connection attempts once per minute, any other users who are already connected to OpenVPN are disconnected and cannot reconnect until that Viscosity client abandons it's attempt to reconnect. It is actually set not to reconnect automatically but that's an issue I can approach SparkLabs about later.
![viscosity vpn viscosity vpn](https://www.bestvpn.co/wp-content/uploads/2017/07/viscosity-vpn-twitter.png)
If the Viscosity user gets disconnected for any reason, Viscosity attempts to reconnect automatically. PfSense is paired with Duo for two-factor authentication and there is a local Duo proxy running that pulls authentication from Active Directory before handing the result off to Duo. The company has purchased copies of Viscosity to give out to a handful of OSX users. Most of their users use the OpenVPN client on their home computers for RDP sessions to their in-office desktops. I have a customer that has been running OpenVPN on a virtualized pfSense instance for many years virtually issue free.Īt the moment they're running 2.3.4p1 in a 64-bit instance on a 100Mbps fiber line.
![viscosity vpn viscosity vpn](https://www.vpnlux.com/i/instructions/mac_ovpn_visc_en_01.jpg)
I realize this is more of a Viscosity issue but I'd like to pose it here as it impacts the pfSense OpenVPN implementation in a way that I wouldn't expect.