this post was submitted on 09 Aug 2025
33 points (97.1% liked)

Selfhosted

50779 readers
1295 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
33
HELP: Wireguard for home network with remote exit node (lemmy.dbzer0.com)
submitted 2 weeks ago* (last edited 2 weeks ago) by portnull@lemmy.dbzer0.com to c/selfhosted@lemmy.world
14 comments fedilink hide all child comments
 

I am looking for some advice on how to (if possible) setup a wireguard network for my home network and when I am connected to that network have a remote wireguard server act as an exit node, so that all external traffic appears to be coming from that remote server whilst keeping traffic bound for the home network local (only accessible via wireguard network)

Local server is a Debian box and other devices will run a flavour of linux. Remote server is already running wireguard and I can connect to that if I bring up a route on each device, but ideally I want to connect to my home net and automatically have outbound traffic go via the remote server. The remote server's wireguard config is not under my control, which may make this unfeasible

you are viewing a single comment's thread
view the rest of the comments
[–] portnull@lemmy.dbzer0.com 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Thank you for everyone's help and input. I have it working now, albeit not in the way I had hoped (not using docker containers for it) but it works. I followed https://thedevquill.substack.com/p/setting-up-a-tailscale-exit-node but instead of using the NordVPN image I used the plain Wireguard client image. In the wireguard compose I set network_mode: container:wireguard. Now when I connect tailscale over the exit node, traffic is going out over the wireguard IP

[–] stratself@lemdro.id 2 points 3 days ago

Hey, glad you got it working. I'm late to the party, but I got a similar solution here: https://github.com/stratself/tswg. Basically just mounts your own wg.conf to the container and get Tailscale connected over it

Since Wireguard is peer-to-peer, I suppose the "intended" way is to install Tailscale on every client. But it is possible to use the router as a VPN gateway as per this [OpenWRT guide])https://openwrt.org/docs/guide-user/services/vpn/tailscale/start#force_lan_traffic_to_route_through_exit_node). Hope you get it working anyhow