49
sharing my simple wireguard kill-switch for Linux
(lemmings.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 May 2024
49 points (98.0% liked)
Privacy
31601 readers
309 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
In what way are you not re-inventing the gluetun wheel ? Not trying to put you down, just that I'd need a good reason to consider anything less battle hardened.
Or even just a list of design considerations and tradeoffs tbh
I'm no network security expert, so I mainly followed Mullvad VPN for my implementation. I looked at the nftables rules that official Mullvad linux client uses, and also their document here: https://github.com/mullvad/mullvadvpn-app/blob/main/docs/security.md.
Though if you have any alternatives for vanilla wireguard users like me, I'll gladly switch. I know somebody mentioned Gluetun but I thought that was for docker only. Do you know of any others?
No worries thats cool and a great contribution. (didnt mean to attack your work).
i have only used gluetun in a docker like context so i cant honestly tell you but you can have vpn and non vpn traffic on your system and you just proxy traffic.
also, now i can see the reason for this (work) and why its cool, which was missing in your post. Also knowing your approach helps others point you to ways to improve what youve done. Thanks you!
No offense taken, on the contrary thanks for the constructive criticism! I'll add some more details to my repo to make things more clear.
Of course! And anytime!!
Isn't gluetun for docker? Are there people running it on the host system?
Just use its proxy for the host system's needs...
How do you route all a host system's traffic through Gluetun? If you use routing tables, wouldn't it similarly be affected by TunnelVision? In which case you would still need a firewall on the host...
Also, the host system likely makes network requests right after boot, before a Gluetun container has time to start. How do you make sure those don't leak?
I am curious though, how you were able to route all host traffic through Gluetun. I know it can be used as a http/socks proxy, but I only know of ways to configure your browser to use that. What about other applications and system-level services? What about other kinds of traffic, like ssh?
I don't route all my system's traffic through Gluetun, my threat model doesn't need it, I just route relevant apps, e.g. package management is in the clear but firefox, SearXNG, and nicotine go via gluetun. SSH can look after itself, or I'm in dire trouble. If my threat model did need it, I'd be considering a similar solution to yours, but it'd be heavily cribbed from the known good of gluetun, basically the docker (podman) put to bare metal.
Yeah, it does come down to threat model and preference. If you only need to route specific apps, Gluetun sounds like a great solution.