mjhjmtu

I'm trying to use the command line tool from Checkpoint to set up an SSL Network Extender VPN using a certificate (P12) rather than a password.

I tried the solution mentioned in getting Checkpoint VPN SSL Network Extender working in the command line.

Specifically:

• build 800007075


• compiled down to 32-bit (as per the accepted answer)

I'm able to connect with the OS X desktop client, but the command line tool throws the following error:

"Virtual Network Adapter initialization and configuration failed. Try to reconnect."

I'm running the connection in a Docker container with the ubuntu:18.04 base image (once I get it to work, I'll port it to something lightweight), using the following command:

RUN snx -s <server_ip> -c <path_to_cert> -g

Using MacOS, I would download/use the latest Mac OS Check Point official client, that is actively supported by CheckPoint, instead of using Docker.

Been using Checkpoint's client in Mojave for a couple of months now, and contrary to my experience at the beginning of the year, in High Sierra, where it was going off all the time, it is fairly stable now.

As for running the Linux CheckPoint VPN client/snx in Docker, it won't work.

The snx VPN client routines:

• check for the kernel presence/the tun kernel module being loaded;


• load/insmod the tun kernel module if not loaded;


• create and use the resulting tunsnx virtual network interface;


• manipulate your routing table;


• send traffic through the virtual tunsnx interface.

Some or all of those actions won't simply happen inside a Docker container.

TDLR snx inside Docker won't work. Either use the Mac native client, or run the Linux snx VPN client on a Linux VM.

PS. I would advise getting familiar with the differences between a container and a VM.