this post was submitted on 17 Dec 2025
16 points (100.0% liked)

Linux

60439 readers
436 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
16
What's the "proper" way to share a single Wireguard connection for all devices on the local network? (lemmy.ml)
submitted 1 week ago* (last edited 1 week ago) by HiddenLayer555@lemmy.ml to c/linux@lemmy.ml
19 comments fedilink hide all child comments
 

My VPN provider has a limit to how many concurrent connections I can have, and a workaround I've been using is to run the Wireguard client as a daemon (wg-quick@my-wg-config) and a Squid proxy on my home server, and point my local devices to the HTTP proxy port, which will route the traffic through the Wireguard connection. However, this has broken randomly multiple times in the past few months, where it will randomly decide to just not allow the server to connect to ANY internet address while the Wireguard connection is active, and no amount of network or routing table configuration changes fixes it. The Squid proxy works fine as far as I can tell, it's just the Wireguard connection that's failing, which doesn't even allow a ping to an internet address from the server's terminal (which doesn't go through the proxy). The only way I've been able to fix it is to completely reinstall the OS on the server and reconfigure everything from scratch, which is annoying and also only works until it randomly decides to break again. This makes me think I'm doing something wrong.

Is there a more "proper" or widely supported way of routing internet traffic on local devices through a single Wireguard connection? Everything I could read online says running Wireguard with an HTTP proxy server is the way to do it, but it clearly isn't very reliable or my computer is just defective in some weird intermittent way? The server is running Fedora Server 43. I've also checked for SELinux denials but there are none.

I'm aware of wireproxy but it uses a SOCKS5 proxy which is not as widely supported as an HTTP proxy and a lot of my devices (mainly phones) won't be able to access it. Also I'd like the server itself to also use the VPN, not just the devices on the proxy.

Does anyone have more experience with this and can give some advice?

you are viewing a single comment's thread
view the rest of the comments
[–] gravitywell@sh.itjust.works 8 points 1 week ago

The proper way to do it is connect your router to the vpn, most routers have support for it these days.

If you want to do it the harder way, connect one machine to your vpn provide on one wg network and create a second wg network for your local devices which routes all traffic (not just http) through the one device thats connected to your VPN provider. Basically make youe own home vpn server and connect to that.

Using just squid for http to relay the vpn in addition to being fragile and breaking sometimes is also just not really giving you the full vpn coverage, your ip is going to be leaking all over the place.