Skip Navigation
Selfhosted @lemmy.world Kokesh @lemmy.world

Forwarding ports to other devices via Wireguard doesn't work

I've made wireguard tu nel out to VPS (to circumvent CGNAT). Dns server works, web server + Gitea, Jellyfin,.. works. All the stuff running on my thin Ubuntu client. What doesn't work is forwarding the RDP port to my windows machine. No firewall on the windows machine. Used to work before CGNAT got enabled by my ISP. I've tried also UDP port, but still no connection.

Here is my wg0 conf:

[Interface] PrivateKey = ..... Address = 10.1.0.2/24

PostUp = iptables -t nat -A PREROUTING -p tcp --dport 3389 -j DNAT --to-destination 192.168.1.21:3389; iptables -t nat -A POSTROUTING -p tcp --dport 3389 -j MASQUERADE

PostDown = iptables -t nat -D PREROUTING -p tcp --dport 3389 -j DNAT --to-destination 192.168.1.21:3389; iptables -t nat -D POSTROUTING -p tcp --dport 3389 -j MASQUERADE

[Peer] PublicKey = ........ AllowedIPs = 0.0.0.0/0 Endpoint = ...oraclevpsIP....:55108 PersistentKeepalive = 25

10

You're viewing a single thread.

10 comments

  • I remember having to enable forwarding of the initial packet when I used to forward a webserver

    iptables -A FORWARD -i eth0 -o wg0 -p tcp --syn --dport 80 -m conntrack --ctstate NEW -j ACCEPT

    • Is it PostUp, or PostDown? Im noob with wireguard

      • UP

        • On my server inside, or the VPS sitting out on the internet? wireguard doesn't start if I put it into PostUP on my server. Yes, I've changed the interface to enp1s0 and port to 3389

          • Pretty sure you configure everything on the entrypoint, for the services runnin in your home machine it should be transparent

10 comments