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

  • magikmw@piefed.socialEnglish
    1·
    59 minutes ago

    You can set this up with your router connecting to the remote server and routing your client traffic through there instead of the gateway your router is using for WAN.

    Specifics are router… Specific.

    You can do the same with a vm in your network acting as a router or proxy as well, pick your poison.

  • comrade_twisty@feddit.orgEnglish
    6·
    6 hours ago

    VPN cascading is the term you’re looking for. Yes, it’s possible with wireguard. Who controls the exit server is not of any concern, although you might break the ToS of the commercial VPN provider in question - but they can’t really see that.

  • jubilationtcornpone@sh.itjust.worksEnglish
    2·
    5 hours ago

    I want to make sure I understand your goal correctly. Here’s what I’m getting.

    1. You have a wire guard connection that you want to use for outbound traffic from your local LAN.
    2. You have a Debian box that serves at the client in this situation.

    Here’s the part where I’m a little fuzzy

    1. You want to connect to your local LAN using another wire guard connection and have WAN requests routed from clients connecting to your LAN (via wire guard) out the wire guard connection mentioned in #1.

    Did I get any part of that wrong?

    Edit: NVM. I saw your response to another comment that sounds like this is exactly what you want.

    This should be achievable via routing. I actually do the same thing. The main difference is all the work is done on my router which handles both wire guard connections and routing.

    At the minimim you’re going to need:

    • A NAT rule on your local router to port forward incoming wire guard requests on the WAN to your Debian box. **Assuming the Debian box is also the wire guard server.
    • An iptables DSTNAT rule on your Debian box to route local traffic to the LAN gateway.
    • An iptables DSTNAT rule on your Debian box to route outbound WAN traffic that does NOT originate from your Debian box to the gateway at the other end of the outbound wire guard connection.
  • null_dot@lemmy.dbzer0.comEnglish
    21·
    6 hours ago

    It’s not really clear exactly what you want.

    When you’re at home, and for services running on your home server, it you want everything to go through the remote wireguard server then that’s achievable.

    However, if you want to be able to access services running on your home server, while you’re not at home, via that remote wireguard server, that generally requires port forwarding which commercial providers generally don’t offer.

    Can you clarify ?

    • PortNull@lemmy.dbzer0.comOPEnglish
      3·
      5 hours ago

      Sorry to be unclear Yes I want to be able to access my home services from outside over wireguard, but connect directly into the home network. However once connected to the home network I want all traffic to be routed outside via the remote wireguard server.