port foward How does on port forward game servers when connected to VPN on Router (OpenWrt)

[Vixanora 0]

Hello!

I am trying to host dedicated game servers and would love to not have my actual IP exposed, I've read some guides and other topics with similar issues from what I am experiencing and neither of them seem to be the case for me. 

I currently have AirVPN on my Router (OpenWrt), I have port forwarded the ports on my router (using the external zone that is the tunnel instead of WAN- because I read that from "How to forward ports in DD-WRT & Tomato with iptables") Which assumes that I can't use the GUI to change the external zone from other than WAN.

_{Yes- I have the port in the External + Internal port, its not shown in the screenshot but it is there.}
--

My firewall is allowing applications and services that I use to host the game server (in this case java/javaw) and I am using the IP the server detects (Its the public server IP [198.XXX.XXX.XXX] rather than client virtual IP [10.XXX.XXX.XXX]).
_{I tried using the client virtual IP, but the software I use to host my minecraft server (MCSS) throws an error saying it wasn't able to bind to that port and suggests another server is using that port which is not the case on my end at least.}

When checking the ports to see if they are open, TCP gets a connection timed out (110). UDP is fine.
_{I checked other forums/topics on this issue and I read through and tested their (potential) solutions and I have yet to get one that works for me.}


I am fully able to connect to other games and services just fine (as well as other minecraft servers), but when I try to host it, nothing seems to prevail.

I believe this is as much info I can give on this- if there is anything I can do on my end to help troubleshoot this, please feel free to inform me and I'll try my best.

Much appreciated in advance <3

[frankgarcia21 0]

The exit IP is not assigned to any local interface, so bind the Minecraft server to the LAN IP of the hosting machine (or 0.0.0.0) instead of the 198.x exit address, since the router's port forward DNATs inbound tunnel traffic to your LAN host. Make sure the OpenWrt forward runs from your VPN tunnel zone to LAN for both TCP and UDP, and that the matching port forward exists in the AirVPN client area. Since UDP is fine but TCP times out, also confirm the hosting machine's return traffic goes back out through the tunnel, because if replies leave via WAN the TCP handshake can never complete.

[Vixanora 0]

I believe tried that and it hasn't worked

On 10/8/2026 at 7:26 AM, frankgarcia21 said:

The exit IP is not assigned to any local interface, so bind the Minecraft server to the LAN IP of the hosting machine (or 0.0.0.0) instead of the 198.x exit address, since the router's port forward DNATs inbound tunnel traffic to your LAN host. Make sure the OpenWrt forward runs from your VPN tunnel zone to LAN for both TCP and UDP, and that the matching port forward exists in the AirVPN client area. Since UDP is fine but TCP times out, also confirm the hosting machine's return traffic goes back out through the tunnel, because if replies leave via WAN the TCP handshake can never complete.