Opening home server ports when CGNAT blocks normal forwarding
When an internet connection sits behind CGNAT, normal router may not let outside devices reach a server inside the network. The current setup uses a VPS running an OpenVPN server, while the internal server connects to that VPS as an OpenVPN client. Iptables rules on the VPS then forward a chosen port, such as port 3309, to the internal server.
This is being used so sales staff can connect from a directly to the company database and enter sales data. The desired setup is closer to old-style , where someone connects to VPSIP:3000 and reaches the chosen internal server. The goal is to avoid VPN, Tailscale, WireGuard, client apps, and , while managing multiple forwarded ports through a web page or GUI.
Pangolin and NetBird were considered, but they require a domain, which does not fit the need.
Key points
- CGNAT can stop normal router from exposing a home or office server.
- The current uses a VPS, OpenVPN, and Iptables .
- Port 3309 is being forwarded so a can reach a database directly.
- The wanted solution should work by and port, without client apps or a domain.
- A web page or GUI for managing several forwarded ports is preferred.