Comment on Forwarding ports to other devices via Wireguard doesn't work
bookworm@feddit.de 10 months ago
Does the machine running the WireGuard tunnel to the VPS acts as a “router” aka gateway for the network? Otherwise the windows machine doesn’t have a return path for the connection.
kokesh@lemmy.world 10 months ago
I’ve got 4G modem. It runs DHCP. From that it is a mix of wifi routers, one dumb switch and things sitting on powerline connected parts f the network. All is running on 192.168.1.xx , only the wg0 interface is 10.1.0.2. My ubuntu server runs just my web server, adguard home, jellyfin, etc.
bookworm@feddit.de 10 months ago
I would advise that you also connect the Windows machine to the VPS with WireGuard as 10.1.0.3, basically mirroring what you’ve done on the Ubuntu server. The routing will be a mess otherwise.
Oisteink@feddit.nl 10 months ago
This - why add another machine into the equation?
Or set up an account at Tailscale or similar. They let you have like 10 machines in your network w/o payment
Or route to your home network through the vpn interface on the VPS. So you can reference the windows ip, rather than NAT
Your current setup is very complicated. I did not check your rules at all but maybe you are setting up forwarding on your servers lan interface rather than the WireGuard interface.
Also you don’t say much about how the VPS setup is. Do you Nat the other working services? What IP/host do you forward to? Are you rdp’ing from the VPS or is that also some form of forwarder/revproxy?