-
-
Save rkueny/301f7ead21ed2a0ee8bbe2d755bed90b to your computer and use it in GitHub Desktop.
mkdir temp && cd temp | |
# for linux 'amd64' architecture install those packages: | |
sudo apt-get install libx11-6:i386 libpam0g:i386 libstdc++5:i386 lib32z1 lib32ncurses5 lib32bz2-1.0 | |
wget https://vpnportal.aktifbank.com.tr/SNX/INSTALL/snx_install.sh | |
sudo ./snx_install.sh | |
cd .. && rm -rf temp/ |
I used to work with SNX connecting directly to CheckPoint VPN servers.
Meanwhile, CheckPoint VPN/snx was updated for TLS 1.2 and now CheckPoint checks for the user agent. Afaik, neither the old standalone version of SNX in the command line, nor snxvpn work anymore. Nowadays, it has to be SNX+CShell agent+Java+an Internet browser.
SNX and CShell install have also their share of problems, and I wrote a script to get around them and install them in a chroot, supporting many Linux distributions.
See https://github.com/ruyrybeyro/chrootvpn and the new chosen answer for https://unix.stackexchange.com/questions/450131/vpn-ssl-network-extender-in-firefox
Thank you, your solution worked for me!
In the meanwhile my solution was slightly adapted to Debian 12 and more linux distros.
I am using:
Ubuntu 24.04
Check Point's Linux SNX build 800010003
I was getting "Segmentation fault (core dumped)" trying to connect to my job vpn, my other team members that also use linux (Mint) were connecting normally so obviously the problem was my OS. Doing some investigation and I found the /etc/resolv.conf with some crazy data, deleted the file, rebooted the OS so the file could be autogenerated again and SNX was able to connect normally.
There should be some way to autogenerate the /etc/resolv.conf without rebooting after deleting it, if the stub file exists, try:
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
then
sudo systemctl restart systemd-resolved && sudo systemctl restart NetworkManager
then try reconnecting to your vpn.
Everytime I disconnect from my job vpn (snx -d) it leaves some dirty data in resolv.conf that might break following attempts to reconnect, so if you have problems connecting check resolv.conf.
I am using: Ubuntu 24.04 Check Point's Linux SNX build 800010003
I was getting "Segmentation fault (core dumped)" trying to connect to my job vpn, my other team members that also use linux (Mint) were connecting normally so obviously the problem was my OS. Doing some investigation and I found the /etc/resolv.conf with some crazy data, deleted the file, rebooted the OS so the file could be autogenerated again and SNX was able to connect normally.
There should be some way to autogenerate the /etc/resolv.conf without rebooting after deleting it, if the stub file exists, try:
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
thensudo systemctl restart systemd-resolved && sudo systemctl restart NetworkManager
then try reconnecting to your vpn.Everytime I disconnect from my job vpn (snx -d) it leaves some dirty data in resolv.conf that might break following attempts to reconnect, so if you have problems connecting check resolv.conf.
I have this error every now and then. I was able to overcome this problem by restarting resolved as you mentioned:
sudo systemctl restart systemd-resolved
I fix this error! And I create this tutorial!
cd /usr/bin/ sudo sh snx_uninstall.sh
wget http://www.pucrs.br/trabalheremoto/snx_install_linux30.sh -O snx_install.sh
sudo bash snx_install_linux30.sh sudo ldd /usr/bin/snx sudo dpkg --add-architecture i386 cat /var/lib/dpkg/arch sudo apt update sudo apt install libpam0g:i386 libx11-6:i386 libstdc++6:i386 libstdc++5:i386 libnss3-tools
chmod +x snx_install_linux30.sh
sudo ./snx_install_linux30.sh
ty @al4xs - worked!
chrootvpn did not work for me, as the Checkpoint I'm connecting to is pretty old
I used to work with SNX connecting directly to CheckPoint VPN servers.
Meanwhile, CheckPoint VPN/snx was updated for TLS 1.2 and now CheckPoint checks for the user agent. Afaik, neither the old standalone version of SNX in the command line, nor snxvpn work anymore. Nowadays, it has to be SNX+CShell agent+Java+an Internet browser.
SNX and CShell install have also their share of problems, and I wrote a script to get around them and install them in a chroot, supporting many Linux distributions.
See https://github.com/ruyrybeyro/chrootvpn and the new chosen answer for https://unix.stackexchange.com/questions/450131/vpn-ssl-network-extender-in-firefox