I got a bunch of self-hosted stuff and use a VPS that has a public IPv4 to access my services because my home network has only DS-Lite. My home server ist connected to the VPS using Wireguard.
Now I want to connect my Smartphone to my VPN to be able to access some local services remotely. I’m able to add a second peer to the Wireguard config on the VPS, but I’m struggeling to configure the AllowedIPs correctly.
The VPS apparently needs AllowedIPs 10.0.0.0/24 and 192.168.178.0/24, but the Smartphone as well for both to redirect request into my home network. But it’s not possible to configure the same IP ranges for two peers. What do I do?

EDIT: Solved: https://iliasa.eu/wireguard-how-to-access-a-peers-local-network/

  • notabot@lemm.eeEnglish
    6·
    9 months ago

    The allowed IP ranges on the server indicate what private addresses the clients can use, so you should have a separate one for each client. They can be /32 addresses as each client only needs one address and, I’m assuming, doesn’t route traffic for anything else.

    The allowed IP range on each client indicates what private address the server can use, but as the server is also routing traffic for other machines (the other client for example) it should cover those too.

    Apologies that this isn’t better formatted, but I’m away from my machine. For example, on your setup you might use:

    On home server: AllowedIPs 192.168.178.0/24 Address 192.168.178.2

    On phone: AllowedIPs 192.168.178.0/24 Address 192.168.178.3

    On VPS: Address 192.168.178.1 Home server peer: AllowedIPs 192.168.178.2/32

    Phone peer: AllowedIPs 192.168.178.3/32

    • atzanteol@sh.itjust.worksEnglish
      5·
      9 months ago

      The allowed IP range on each client indicates what private address the server can use

      I really dislike this description - yet I see it everywhere. It caused me a ton of confusion initially.

      It’s the IP addresses that will be routed over the VPN. So if you wanted, say, all traffic to go through the VPN then you would use “0.0.0.0/0”. Which is what I do for my phone.

      • notabot@lemm.eeEnglish
        3·
        9 months ago

        Sort of. If you’re using wg-quick then it serves two purposes, one, as you say, is to indicate what is routed over the link, and the second (and only if you’re setting up the connection directly) is to limit what incoming packets are accepted.

        It definitely can be a bit confusing as most people are using the wg-quick script to manage their connections and so the terminology isn’t obvious, but it makes more sense if you’re configuring the connection directly with wg.

      • bobs_monkey@lemm.eeEnglish
        1·
        9 months ago

        I’ve always understood it as the x.x.x.0/x being the gateway designator and network identifier, followed by the range of allowable IP addresses

    • Dataprolet@lemmy.dbzer0.comOPEnglish
      2·
      9 months ago

      Thanks, but I have configured a dedicated IP range for my Wireguard network, so the devices have IPs like 10.0.0.1. But I still want to access services in my home network in the IP range 192.168.178.0/24.

      And in your example the AllowedIP = 192.168.178.2/32 of the VPS would still make it possible to route traffic from my smartphone via the VPS to my home server?

      • notabot@lemm.eeEnglish
        4·
        9 months ago

        Ah, ok. You’ll want to specify two allowedip ranges on the clients, 192.168.178.0/24 for your network, and 10.0.0.0/24 for the other clients. Then your going to need to add a couple of routes:

        • On the phone, a route to 192.168.178.0/24 via the wireguard address of your home server
        • On your home network router, a route to 10.0.0.0/24 via the local address of the machine that is connected to the wireguard vpn. (Unless it’s your router/gateway that is connected)

        You’ll also need to ensure IP forwarding is enabled on both the VPS and your home machine.