@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.

can be closed i deactivated uPnP and now steam works - lol

Just in case anyone else has this problem: I reinstalled pfsense with the same settings and now it's working.

Checkout solution https://forum.netgate.com/topic/168376/multiple-xbox-consoles-with-open-nat-and-working-play-together

Thanks for your contribution! i was inspired by this post and came to solution with every console with open nat and working play together https://forum.netgate.com/topic/168376/multiple-xbox-consoles-with-open-nat-and-working-play-together?_=1639047807695

@radarg ok it looks like all the UPNP is working I see the rules pop up. Why would the second xbox try to talk to the same port at the first one? I thought that once the second xbox made contact with the server it would use a different port. Am I wrong?

To anyone got the same problem, don't tick Static port box in Outbound rule (other games may need it). It took me a few days trial and error XD

@striker-pl well after hours of investigation, turning off Storm Control on my switch solved the issue. Posting here in case it helps anyone else.

@mcury Thanks for the help but no luck. Ill just give up on the box preforming a port forward. I'm moving soon but wanted to get some better game performance without all the packet losses. I will be thrilled to have a better ISP provider than the local one here or the other terrible option of Spectrum.

@stacyann33 Nope, we 'play' pfSense. And you're the first one using the word 'HiRez' on this forum. pfSense it's a firewall that assures that there are no holes. Nobody want holes in a wall. If there were, there is no meaning of putting up the wall in the first place. pfSense can let you make 'holes', to devices that run programs on your LAN. It seems to me that Smite Hires doesn't have any public documentation - otherwise you were reading that doc instead of asking here , and do what they were asking you to do, like NATting a port(s) to the PC that runs the game. By default : do nothing. Btw : https://www.reddit.com/r/OutOfTheLoop/comments/2pvfen/why_is_smitehi_rez_studios_often_ridiculed_in_the/ make sme understand that, if your host your own 'server' version of the game, you should make that service accsible to the outside world == you have to "open ports" == NATting ports. Google doesn't know anything about it, so there is only the documentation that can help you.