I can connect to the vpn on my own machine just fine via this docker image ananni/snx-checkpoint-vpn.
however when I tried to do the same on Github Actions using a Docker container action, it just won’t connect to the internal network, even though the process doesn’t indicate any error.
I noticed a difference tho, when I ran ifconfig on my machine it showed an extra interface called tunsnx which doesn’t get created on github actions I don’t know why. is there any network limitation that I am not aware of?
Not exactly what you’re trying to do, but we have a “dark”, privately hosted Mattermost instance we use internally, only available over OpenZiti. OpenZiti supports SDK access, including a Python SDK that we use to post a webhook from a GitHub action. The action happens run from a container, and you can have a look at it here: https://github.com/openziti/ziti-mattermost-action-py
The interesting line in the main python script is ziti-mattermost-action-py/zhook.py at fb1a4f612c6986775893b73b005a83caff0556ff · openziti/ziti-mattermost-action-py · GitHub , which monkeypatches to send network traffic over OpenZiti.
Happy to help if you want to look into this approach. There are also some docs about connecting with OpenZiti from a docker container (e.g., https://hub.docker.com/r/netfoundry/ziti-tunnel). I haven’t tried this from a GitHub action, but some of the notes might be relevant/helpful in your scenario (e.g., setting `–cap-add=NET_ADMIN`)
i dont think this is a solution, I just need to connect to the internal school network which happens to use checkpoint vpn
yeah - you would need OpenZiti on “both sides” for that to work. I don’t know of a way to configure network settings when using a docker-based action. You might have better luck running docker manually so you can include command line params to `docker run` and allow access to that tun device. Possibly something like docker run --network=host --cap-add=ALL ... Hope this helps - good luck!