For a new problem, you really need a new thread. The config in this thread has been working for many of us for years. If it doesn't work for you, then it's something new, a game-specific issue, or unrelated to this thread in some other way.
regardless of what i do, following the whole steps mentioned here:
upnp does not seem to allow the packets, you can see the packet answers always to be blocked in the system-logs :-(
i use 2.0-RC2 (i386) built on Sun May 15 20:43:07 EDT 2011
now i defined NAT by hand and it works…
but why not upnp ?
i used the following upnp rule: allow 1-65535 xxx.xxx.xxx.xxx/32 1-65535
anyone any ideas ?
i even created a pass-rule for the upne ports from lan-network to lan-address as stated in http://forum.pfsense.org/index.php/topic,33024.0.html
but it still does not work, there are simply no mapping in the upnp status...
I remember when I had such problems logging into a game on Xbox. I wrote a lot more in support of Activision about this, and in the end, they did not help me, and the problem was solved after a while. But I think you are already playing the new version of Call of Duty MW II, and there are no such bugs. And if someone here wants to play Warzone 2 with me, then write to me in private messages. And I assure you we will constantly occupy the top 1 because I play with scripts that I bought on https://royal-coders.com/product/cod-warzone-2-no-recoil-macro-script/. Yes, it's a little unfair, but there is a result.
Hi- Just out of curiosity have you tried just giving your game consuls a static port and abandon UPnP? I only have one PS so I have no idea how well this will work with two.This gives me NAT 2
Screenshot from 2022-11-15 07-53-50.png
Not sure about anyone else but I play MWII on XBOX Series X with static IP. There are ports for just accessing XBox Live. Then Activision has ports for updates/upgrades and game play separately. Keep in mind now, Activision says only UDP but that's BS because the System logs showed TCP on a bunch.
I spent two hours trying to figure this out and here are all the ports I had to allow just to get to play MWII multiplayer.
**I didn't go through each one to determine which is TCP vs UDP because I was too frustrated. Although I should but I allowed only these ports to the XBox IP address. At this point I'm just glad it's working...
Here you go:
88, 500, 1900, 3544, 3658, 4500, 49408, 5223
If anyone cares to identify UDP vs TCP that would be helpful but I'm not going through the struggle...
@donzalmrol i remember on 2.5 i used to get UPnP & NAT-PMP sessions but for some reason am not getting it with 2.6, i have tried many configurations and am not sure what am doing wrong, hopefully somebody knows the fix.
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.
@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.
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?
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.
@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?