We have been using a VPN solution from a competitor for several years. The hardware of the product will be discontinued. We would like to to move to a Check Point VPN in order to benefit from an administrative integration into our existing Check Point firewall.
Our 20 Linux users had been happily using an openconnect plugin for VPN access. Zero support effort dispite a broad range of Linux variants. We only realized how perfect that approach was until after we started to evaluate two Check Point VPNs. The level of dissatisfaction and frustration during the evaluation phase is high. The users vetoed against moving to Check Point. Others like me successfully use the windows client, but I agree that the required amount of local Linux support is not realistic. It is impressive to see the official clients exist - but in the end they are neither working out-of-the-box, nor compliant to local legislation, nor Linuxish from our experience.
The CP openconnect plugin, the ideal zero-support solution, has not been merged into master for the past three years. Probably it is ready only after we made a purchase decision.
The cpyvpn MAP login algorithm consists of "a bunch of hacks and tricks", so one day the Linux users might not be able to connect. We welcome the frank documentation and accept cpyvpn does not meet our expectations.
We learned about snx-rs, which would be accepted by our users. Closest we can get. However, it has a timeout problem. See https://github.com/ancwrd1/snx-rs/issues/49 The issue is not fixed in my opinion. Having the option of keepalive=true/false aids in debugging. But an idle timeout after 60 minutes still happens although the connection is not idle. That sounds like a matter that could be explained (fixed) quickly by somebody at CP deep into the matter. Maybe the keepalive-Packet is simply sent to the wrong target or not getting through. Any pointer is appreciated.