Selfhosted

40696 readers

315 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

If I already have a VPN always on on my system, do I need to set up a gluetun container? (lemmy.dbzer0.com)

submitted 3 months ago by Polite_Crocodile@lemmy.dbzer0.com to c/selfhosted@lemmy.world

23 comments fedilink hide all child comments

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...

you are viewing a single comment's thread
view the rest of the comments

[–] gravitas_deficiency@sh.itjust.works 8 points 3 months ago* (last edited 3 months ago) (2 children)

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 directly pinged by DMCA rats. That way, if the VPN goes down, your torrent client isn’t just downloading stuff nakedly. Also, if you want to set up different VPN connections for different containers, it’s pretty easy to set a handful of replica containers for that too.

[–] kitnaht@lemmy.world 3 points 3 months ago* (last edited 3 months ago) (1 children)

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. Most modern clients have this (qBittorrent certainly does)

[–] gravitas_deficiency@sh.itjust.works 5 points 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 points 3 months ago (1 children)

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 2 points 3 months ago (1 children)

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 1 points 3 months ago (1 children)

In terms of homelab stuff, I know a lot of people appreciate the containerized approach.

What I said applies to containerized setups as well. Same logic, just managed in a slightly different way.

[–] gravitas_deficiency@sh.itjust.works 1 points 3 months ago

Fair; I blame target fixation