@selfhosted Have a commerical @wireguard vpn on my server. The problem i have is that if i use a docker, it does use the vpn interface with iptables, but if that goes down, the docker still goes through without the vpn interface. I have looked at iptables, but docker makes it own, and bit of a minefield. Any ideas? Thanks
IMO the best way to ensure that traffic always goes through a VPN is to use network namespaces. The wireguard website has an article describing the process. In a nutshell, you create a dedicated namespace to put the physical interface in, create the wireguard interface in that namespace, then move the wireguard interface to the root (“normal”) namespace. That way the only way to get traffic out without the VPN is to run a program in that dedicated namespace.
unkn0wn@midwest.social 9 months ago
Check out gluetun, I use this on my server to ensure that all traffic for certain Docker containers goes through a Wireguard VPN.
redcalcium@lemmy.institute 9 months ago
This is the way to go.
finestnothing@lemmy.world 9 months ago
Same here, idc about some of my containers going through VPN (tandoor, gitea, Plex, etc) but my whole arr suite, qbittorrent, and sabnzbd are routed through a gluetun container that uses my protonvpn credentials. Never have to worry about turning my VPN off for gaming or something since the… totally legal research papager aquirerer apps… are all routes through the VPN which changes it’s connection every 4 hours (changes my public IP but also just to make sure none of the containers run into any issues that they can’t figure out without a restart)
ShepherdPie@midwest.social 9 months ago
Just FYI for anyone else, you don’t need to run the *arrs through a VPN only your torrent client as that’s where your IP gets exposed to the outside world.