Submitted 1 month ago by Polite_Crocodile@lemmy.dbzer0.com to selfhosted@lemmy.world
I honestly can’t get my head around this. I have a machine with Linux (endeavouros), and docker with a few containers. Since I want all the traffic from this system to go through the VPN, do I need to set up gluetun? I think not, but I am not 100% sure…
Nope
Ok, thanks. So if I’m getting this right every container should return the VPN IP with curl ifconfig.me
That’s correct and a good way to test it out.
Yeah, when you have the VPN running all of your external traffic should go through it. It starts to get complicated when you only want a specific container/user to use/bypass the VPN.
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.
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.
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.
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.
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.
I ran a Linux VM and just had Mullvad app installed and always on, and that was all I needed
And that works too. Containers are just a way to do it more efficiently. Better for weaker hardware and energy usage.
Yeah I know, I use Gluetun now, I was just answering OPs question.
GreenKnight23@lemmy.world 1 month ago
I’ll ask this question because it might be something you didn’t think of.
What happens to your network connection if the VPN fails? will it continue to connect without a VPN?
I had a similar case of that happening, and ended up causing me to get some shame mail from my ISP.
now I run my VPN inside docker, and any containers that need access to it are configured as network slaves to it. VPN goes down? container reboots, all the others reboot after connection is restored, but will have no connection while it’s down.
it’s all in a well designed system of healthchecks and container configuration.
Polite_Crocodile@lemmy.dbzer0.com 1 month ago
I simply enable the killswitch in mullvad settings and get all the Linux isos I need. But I’m thinking to keep gluetun enabled since I’ve already configured it
GreenKnight23@lemmy.world 1 month ago
I would recommend it. Speaking from personal experience, I trusted my VPN connection to remain on and self-heal. Thinking that cost me a strike against my ISP.
Now I know for a fact that if anything goes wrong with the VPN connection, all the containers that need it will need to restart before they have connectivity again and that can only happen after the VPN container restarts and passes healthcheck.
TCB13@lemmy.world 1 month ago
You can force all outgoing traffic to use the VPN interface via iptables/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 services except for the VPN client.
GreenKnight23@lemmy.world 1 month ago
IMO this is the best OS way, but without nix it’s a pita to maintain through restores/rebuilds. personally I never fully comprehended how to properly configure iptables/routes (I did try though, so nobody can blame me lol).
however, a major benefit to using a contained VPN or gluetun is that you can be selective on what apps use the VPN.
I host 12 other containers (with nas mounts) on the same host outside of the three that need to use a VPN, so this is why the solution I described works for me. and should I ever need to use routes for more advanced network filtering I still have it available without adding the complexity of splitting normal traffic vs VPN traffic.