Fios CR1000B Port forwarding for games

I've had some strange inconsistencies on my Fios router when it comes to port forwarding. Two services, Plex and Remote Desktop, went through just fine (32400 and 3389 TCP ports respectively), verified on canyouseeme.org and by using the services. However, whenever I try to port forward additional ports for gaming, like the newly released Palworld, the port never ends up exposed to the internet.

I tried a factory reset and re-inputting the port forwards from scratch, but once again 3389 and 32400 were allowed while 8211 stays closed. Everything looks totally fine in the router control panel:

The rules even show up on the Verizon account portal:

My only theory at this point is that Verizon is blocking the traffic on their end as an additional security measure, since the first two services are trusted and popular but most games aren't—indeed, I even tried the nuclear option of putting my IP in the demilitarized zone setting and nothing was changed. Is it possible to get this done?

Firmware version 3.1.1.20

Hardware version 103

Model CR1000B.

Accepted answers

Cang_Household

Very well, you need to select the protocol to be UDP, not TCP as you original had it.

Besides that, it should just work. Once you have opened the port, could you run some tests independent of the applications you are trying to use (I was using netcat to probe and tcpdump on the inside to detect traffic)? Needing to eliminate as much variables as possible for a meaningful test.

All comments

Cang_Household

I will replicate the ports you are forwarding on my test bench to see if I get the same issue, which I doubt.

Cang_Household

Per the following, failed to reproduce the OP's condition. Added 3 discrete TCP based port forwarding and all are working in order per netcat.

3 Concurrent Port Forwarding on CR1000A/B

amalesevic

I appreciate what you're doing here, but now I'm all the more mystified as to why it's still failing for me in this way. I noticed that the game does need UDP on port 8211, so I've enabled that as well, but external connections to the server are still timing out.

Virtually every other port forwarding issue reported seems to be all or nothing; I haven't been able to find a remotely similar problem except for when ISPs block particular ports or the server hasn't cleared the proper firewall rules (which I have).

Cang_Household

Very well, you need to select the protocol to be UDP, not TCP as you original had it.