You can always use a consumer VPN because sometimes your network IP gets crowded thus causing jitter to happen.

https://forum.netgate.com/topic/169837/upnp-fix-for-multiple-clients-consoles-playing-the-same-game The patch above looks like the solution. I am taking some time to test it. But if you find this old post, try the stickied patch thread above. That looks to be the real solution.

same issue here

@keepitsimple said in Configure OPT port for Gaming Console: I enabled OPT port, with DHCP for IPv4 and everything else left blank. In the interface setting you marked IPv4 Configuration type as DHCP? If so then you need to change it to Static IPv4 since there's no DHCP server on the OPT to issue the interface an IP. Then you'll need to go to Services -> DHCP Server -> OPT 1 and enable DHCP server for OPT 1 then also create a DHCP pool. Alternatively, you can just create an ACL in UPnP to only allow your gaming console. https://blog.gravitywall.net/2021/12/27/fixing-nat-type-strict-on-xbox-series-sx-with-pfsense/

These are my current settings: [image: 1648149142590-f8dde048-9832-4f94-9a2d-a2958b4aa38a-image-resized.png] [image: 1648149004634-600499be-cbe9-4606-a4de-9d24ff7c4687-image.png] [image: 1648149597815-26c8f1ce-154e-4ab5-9388-e8a09976b7c6-image-resized.png]

@steveits I tried that just to see if it would work for me, and it still would not allow a connection

@behemyth Sorry for being back so "late" but it sure works!

@jimp Yes, thank you, that's probably exactly it. It's been so long since I've upgraded that I completely forgot to reinstall updated drivers as I've done in the past.

@bob-dig said in [solved] UPnP behind double NAT is not working, even with a STUN-Server: @jimp @viktor_g I now tested it with the google STUN Server and it is working for me. Great! That's the same one I used when testing and it worked well here. I guess the redmine Issue https://redmine.pfsense.org/issues/12797 could be closed too. The problem I mentioned on the Redmine issue is still a legitimate issue that is being worked on. It affects new outbound connections (like for game clients) and not inbound connections like those for torrent/download clients.

@oldirtyjedi said in How about updating the pinned topics?: @jimp Well, this is an interesting case. Everything is fixed, by installing the new miniupnpd patch that is pinned at the top of the gaming subforum. Yep, but I also did update that pinned post since the fix was discovered :-) So, you are correct - but this is perhaps now added to pfSense and makes this appliance more consumer friendly? Indeed. In retrospect - this all just happened. But these pinned topics will need to be revised if this fix is added to pfSense in future builds. They are no longer valid. With the exception of needing the patch, the other info is still valid. Some games and/or consoles do not support UPnP so they need static port oubound NAT. If games support UPnP that will need to be enabled+configured.