Thanks for the great product! I’ve always despised VPN clients and the complication they bring to my working life. Viscosity manages to be entirely seamless – most impressive.
Unfortunately, my employer has moved to a new VPN solution which is not supported by Viscosity. Thus my question: do you have plans to add support for OpenConnect [0] as an additional backing client implementation?
Thanks for the positive feedback - much appreciated.
Multi-protocol support is something this is coming (fairly soon we hope). To be honest I wasn’t even aware the OpenConnect project existed, however it looks pretty solid (and you’re not the first to ask for AnyConnect SSL support) so we’ll see about implementing it as well.
Glad to hear there is some demand for this. I’m afraid there is no ETA at this stage - we’ve got a lot of projects in the works, but hopefully we’ll have something available sometime soon.
Bump; my company just changed from an OpenVPN server to a Cisco AnyConnect VPN (boo). The vendor native client is terrible; openconnect works as a command-line VPN client, but I’d love a SparkLabs take on this.
As a fairly long time user of Viscosity I’d like to give a “+1” to the call for OpenConnect support to be added to Viscosity.
OpenConnect seems to have some advantages over OpenVPN, is far quicker to connect, gives a slightly higher throughput speed (at least for me), and (if I’m understanding correctly) has the advantage that data using it cannot be identified as using a VPN at all. The only disadvantage I can find is that there is a CPU overhead not present with OpenVPN.
Is there any chance of Viscosity supporting OpenConnect in the near future?
As a visocity user I would extremely like to have openconnect support.
SparkLabs Newsletter
Thank you for being interested in keeping up with the latest news from us! Please double-check your email address below and then click the Subscribe button.