That way, if the VPN goes down, your torrent client isn’t just downloading stuff nakedly.
You always just bind the torrent client to the VPN adapter so this doesn’t happen.
Comment on If I already have a VPN always on on my system, do I need to set up a gluetun container?
gravitas_deficiency@sh.itjust.works 3 months ago
It’s convenient if you want to see gluetun up as the only way a container (say, your torrenting container) can get to the open net, in the interest of avoiding getting pinged by DMCA rats.
kitnaht@lemmy.world 3 months ago
gravitas_deficiency@sh.itjust.works 3 months ago
Oh yeah you can do it that way too, but if you want it all containerized, that’s roughly how to do it. That’s all I meant.
TCB13@lemmy.world 3 months ago
All of that can be achieved with simple systemd or iptables/routes tweaks. You can force all outgoing traffic to use the VPN interface via routes (meaning if it doesn’t exist or doesn’t work nothing will be able to access the internet) OR use systemd globally hide the non-VPN network interface from all software except for the VPN client.
gravitas_deficiency@sh.itjust.works 3 months ago
Well sure, but the question was about gluetun, so I was trying to focus on that and the applications thereof. In terms of homelab stuff, I know a lot of people appreciate the containerized approach.
TCB13@lemmy.world 3 months ago
What I said applies to containerized setups as well. Same logic, just managed in a slightly different way.
gravitas_deficiency@sh.itjust.works 3 months ago
Fair; I blame target fixation