vopono VS gluetun

Vopono (https://github.com/jamesmcm/vopono):

"vopono is a tool to run applications through VPN tunnels via temporary network namespaces. This allows you to run only a handful of applications through different VPNs simultaneously, whilst keeping your main connection as normal.

vopono includes built-in killswitches for both Wireguard and OpenVPN."

I think for now on Linux you (still!) have to use external application to do the splitting. Such is vopono

I use vopono to manage it for me with Mullvad though.

you might want to check out vopono, i've gotten it working with firefox and its nice

https://github.com/jamesmcm/vopono

I highly recommend using something like vopono with this on Linux that runs only the target application (e.g. Transmission) in a network namespace in the VPN and only forwards the specified ports and only allows traffic via the VPN.

This is why I use vopono - you can run just the torrent client in the VPN on its own and the killswitch keeps it safe.

You can find the option in the settings of windows and android apps. Unfortunately, it's Still not available for Linux. As a workaround for Linux, you can use vopono, which has OpenVPN support for Proton. Or just manually add routing table entries :)

I wrote vopono, I use it all the time for quickly spinning up browsers through different VPNs for checking geographical restrictions, etc.

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki