Hi,
I'm having a hard time with the netskope client on Linux. This is a WSL2 installation, and a netskope agent is running on the windows host. But the windows agent status has no influence on the behavior of the guest linux one.
Very often, the nsclient config outputs a normal status with tunnel up, and private access enabled. Unfortunately the show-pa show this :
$ nsclient show-pa
start process....
Status: Connected (User Tunnel)
Sent: 0 bytes
Received: 78646 bytes
and the nsdebuglog.log is spammen with this kind of errors :
2025/09/16 20:21:00.358996 stAgentSvc p46ba6 t46db5 error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:01.381263 stAgentSvc p46ba6 t46db5 error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:02.404470 stAgentSvc p46ba6 t46db5 error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:25.547248 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:26.561979 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:27.584093 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:28.610099 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:29.411557 stAgentSvc p47489 t4755c debug nsPktFlow.cpp:188 nsPktFlow TcpFlow [1] open NAT flow: src 100.65.0.2:51726, dst 100.65.0.6:443, resolvedAddr 163.116.171.136
2025/09/16 20:21:29.641242 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:30.661539 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:32.677737 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:36.706373 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:21:44.897880 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:22:02.086970 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:22:35.613406 stAgentSvc p47489 t4755c error nsKernelUserShim.cpp:359 KernelUserShim Failed to register NAT flow!
2025/09/16 20:22:57.942446 stAgentSvc p47489 t4755c debug nsPktFlow.cpp:188 nsPktFlow TcpFlow [2] open NAT flow: src 100.65.0.2:52812, dst 100.65.0.6:443, resolvedAddr 163.116.171.136This is a very unstable behavior as from time to time, doing mothing, the private apps are accessible again.
Do you any idea guys how to tackle this ?
