>>101356391
You can do VPN so many ways.
>If I make a WireGuard VPN connection to my house, how can I access local resources?
>how can I access local resources?
That's whole another question.
You can think of WireGuard/OpenVPN/whatever tunnel as having another network card that was plugged into the other end.
>I have services running that I access via IP:port but this doesn't work when I'm on VPN
Who "does the WireGuard"? The local machine you have services on? Or do you have a router that *bridges* your local Ethernet to the other end? Or does the router *route* the extra net?
If you do bridging, please pay a lot of attention to IP addressing on both ends. You are making yourself a network admin now that you are interconnecting networks. (still assuming you don't route)
I have a point-to-point style of setup between my router and my VPS, this is from the router:
# 01-hetzner-wireguard.netdev
[NetDev]
Name=wg0
Kind=wireguard
[WireGuard]
PrivateKeyFile=/mnt/anime/wireguard-home.key
[WireGuardPeer]
Endpoint=**********:****
AllowedIPs=10.255.44.0/24
PublicKey=**********
# 01-hetzner-wireguard.network
[Match]
Name=wg0
[Network]
Address=10.255.44.2/24
Yes, systemd/Linux files. And ones for the VPS that looks mostly the same but IPs other way around and a different key.
This particular setup ROUTES (doesn't bridge) 10.255.44.0/24 between my local 192.168.1.0/24 so I effectively have an intranet here. I could've bridged it too but the peer on the other end has no reason to receive all my Ethernet packets, IP is enough.