Those rules don't appear correct to me. The necessary mapped ports aren't even identified. Modifying the kernel is drastic, and really that shouldn't be necessary either but I'm not 100% sure. Anyone using netfilter will have the same problem as me. I did try several different destination/source nat rules yesterday with no luck. I believe the proper iptables rules should give full cone but if really limited by kernel, I will not go further. If I discover a solution, I will post it here.
Port_Restricted Router, even after Port Forwarding. Only game I've ever had this issue with.
- Thread starter SavageSndz
- Start date
They were just examples and would need to be tailored to your specific needs. This appears to have a more complete example, but I'm not familiar enough with iptables to evaluate it myself.
Will be interesting to know what you discover.
I've been looking into this lately too after having so much trouble with multi-crew disconnects.
I have a Segemcom 5260 and followed the PF doc to set up UDP forwarding for 5100, 5101, 5102, 5111, and 5200.
Also set up the static IP in my PC network settings.
I've tried using Upnp without forwarding. I can switch it on and off in the router gui.
I've tried selecting ports 5100 thru 5200 in the Game Options menu with Upnp turned off in the router gui.
I've tried the software port checker but it always says "closed" using my external address or my local address to check 5100 thru 5200.
After all this, Multi-crew disconnects are just as frequent... no change.
Not sure what else to try.
I have a Segemcom 5260 and followed the PF doc to set up UDP forwarding for 5100, 5101, 5102, 5111, and 5200.
Also set up the static IP in my PC network settings.
I've tried using Upnp without forwarding. I can switch it on and off in the router gui.
I've tried selecting ports 5100 thru 5200 in the Game Options menu with Upnp turned off in the router gui.
I've tried the software port checker but it always says "closed" using my external address or my local address to check 5100 thru 5200.
After all this, Multi-crew disconnects are just as frequent... no change.
Not sure what else to try.
Do you have a dedicated IPv4 address? UPnP and port forwarding won't work if your ISP doesn't allocate a public IPv4 address just for you. This is also known as Dual Stack Lite (if you have IPv6 as well) or Carrier Grade Network Address Translation (if you don't)
It's basically a router your ISP sat in front of your own at their end. And you can't configure that one to forward ports, for good reasons. This type of setup is typical for cable ISPs that have a 20:1 download/upload ratio.
CGNAT/DSLite is the death of IPv4-dependent Peer-To-Peer.
Last edited:
It is a cable ISP so I suppose that the address is not dedicated. How would I confirm that?
If I'm not able to forward ports, I wonder why the router gui offers port forwarding.
If your router displays a WAN address, look there.
If it's one of the following:
- 10.x.x.x
- 100.64.0.x to 100.64.127.x
- 172.16.x.x to 172.31.x.x
- 192.168.x.x
Another alternative is doing a
tracert -4 to f. ex. google.com and check the second (the first hop is always your router) and subsequent hops for an IPv4 address as listed above.Because the router can be used on non-CGNAT connections as well and most router manufacturers don't care about these details.
Last edited: