See also Linux Checkpoint SNX tool configuration issues for some clarifications about which snx version to use.

For closing/disconnecting the VPN, while you may stop/kill snx, the better and official way is issuing the command:.

If you understand the security risks of hard coding a VPN password in a script, you also can use it as: echo 'Password' | snx

You might need to run manually first snx -s CheckpointURLFQDN -u USER, before scripting any automatic use, for the signature VPN be saved at /etc/snx/USER.db.īefore using it, you create a ~/.snxrc file, using your regular user (not root) with the following contents: server IP_address_of_your_VPN You can only proceed to the following points when all the dependencies are satisfied. Check if any dynamic libraries are missing with: sudo ldd /usr/bin/snx You will have now a /usr/bin/snx 32-bit client binary executable. Run then the snx installation script: chmod a+rx snx_install.sh I had to install the following 32-bit packages: sudo apt-get install libstdc++5:i386 libx11-6:i386 libpam0g:i386 To install snx build 800007075, get it from:įor Debian and Debian-based 64-bit systems like Ubuntu and Linux Mint, you might need to add the 32-bit architecture: sudo dpkg -add-architecture i386.

Presently, the solution is then installing this specific last version of SNX that still supports doing the VPN from the command line. So ultimately, my other answer in this thread holds true, if you cannot get hold of SNX build 800007075 or if that specific version of SNX stops working with the current Linux versions (it might happen in a near future) or if you need OTP support.

So I tested it, and lo and behold, it still works with the latest distributions and kernel(s) 4.x/5.x. SNX build 800007075 from 2012, used to support the CheckPoint VPN from the Linux command line.

Check point vpn certificate delete