![]() ![]() ![]() See ping fails to server behind tunnel docker run -rm -ti -net=company_net busybox /bin/sh -c "ping 192.168.210. Here are my findings and the solution to (temp) fix it: On kernel >5.8 the tunsnx interface is no longer created with global scope and need to be recreated. It would be really nice if someone could help me with this. macOS and Linux clients) Create a free MyMSK account that gives you access to the latest. I have been looking for a solution for several days but have not found anything. Mskcc VpnMskcc Vpn Outlook, Vpn Con Fibra Movistar, Csu Vpn. However, this was only a test scenario and cannot be used as an alternative. I also did a test with another VPN (OpenVPN) which worked fine. I tried the whole thing with a fresh Pop OS 20.10 installation, same problem. Because of dependencies I have also to downgrade gcc, gcc-libs and lib32-gcc-libs to version 10.2.0-4. If I downgrade packages glibc and lib32-glibc to version 2.32-5, the ping out of the container works again. ~ ]$ docker run -rm alpine ping company-serverĪlso using the IP from the 'company-server' doesn't work.Ī ping outside the container works, no matter using the name or IP. When I start a Docker container (Docker version 20.10.3, build 48d30b5b32) which should connect to a machine from the company network, I get the following message. I am connected to my company network via VPN.įor this I use SNX with the build version 800010003. Download a remote access client and connect to your corporate network from anywhere. I am working with the latest Manjaro with the kernel: x86_64 Linux 5.10.15-1-MANJARO. Check Point Remote Access VPN provides secure access to remote users. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |