Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT
-
@donzalmrol Your results are consistent with the expectations of your settings at this time. The only other workaround for end users at the moment is to use one of the workarounds mentioned earlier in this thread, or sit tight while more details and development are ironed out. Being subscribed to this thread (as you are since you have replied) will help you know when more progress has been made. Best of luck.
-
@theprestigepacketfilter Thanks for validating!
Another workaround is creating a new VLAN where the ISP its network is routed through, then place the 2nd computer in that vlan (by either cable or wireless), downside is that you bypass the firewall...
-
Add me to the list of users having this issue. Spent 5+ hours today reading through this forum, Reddit, etc. I can’t get two series X online with Warzone at the same time. If I move one Xbox over to my LTE router, everything is fine. I have the latest PFS release with outbound NAT rules and upnp with an allow list. The Xboxes test fine with an Open NAT. Warzone refuses to function on one.
-
I found a solution that actually worked for me for the meantime. I never noticed Warzone trying to NAT out 1024 also, so rbflurry's response (link below) was what I needed. A NAT from 3075->3075 and then another from 3075->1024 on the other console was what I needed.
https://forum.netgate.com/topic/152142/call-of-duty-modern-warfare-multiple-xbox-ones-upnp-and-nat-failure/8?loggedin=true
Still, I'd love to have a workable upnp solution in the future. Thanks!
-
I wish this was fixed...
-
Like others have mentioned this is what helped me: https://redmine.pfsense.org/issues/7727#note-35
And I got both of the PCs to show open NAT. In my case I was trying to get COD to work so port "3074" works and this is what UPNP should have been doing automatically for us.
For what it's worth, I did have both PC's showing "Open" NAT types, and both were able to join each other's lobby, without upnp. I manually created port forwards and outbound mappings. For outbound, I had: 192.168.1.48:3074 => WAN:13074 192.168.1.49:3074 => WAN:23074 For port forwards: ANY:13074 => 192.168.1.48:3074 ANY:23074 => 192.168.1.49:3074 -
@hansaya It'd be nice to have this tested on the latest dev snapshot. There seems to have been a lot of fixes with NAT.
-
@chrcoluk said in Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT:
How are you even getting one peron on open nat on the pc, how are you testing it?
do u still this question to be answered ? btw: i don't check this forum that often or at all
-
@marc05 said in Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT:
@hansaya It'd be nice to have this tested on the latest dev snapshot. There seems to have been a lot of fixes with NAT.
do u know if this is fixed in the latest dev builds ?
-
@hansaya Can you post a screenshot of your outbound and port forward rule? Thanks
-
@mkayze sure
Outbound
Port forwarding
Port Aliases
Some of you ask to test on a dev branch and I might try that this weekend. I just need to make sure my vm backed-up etc.. before I attempt it.
-
@hansaya Thank you for that! I was finally able to get both PC's to not have strict NAT. Although one PC is still showing Moderate no matter what I do, not sure why. But this is way better than having it at strict.
Tested it on both PFsense and OPNsense and both work with this method.
-
@mkayze My guess is you are not covering all the ports needed for the game(check both TCP and UDP). I do not have UPNP enabled and both machines are showing Open NAT for all call of duty games. Vanguard, Cold war, Warzone etc...
@aniel @Marc05 I tested the latest 2.6.0_devel and UPNP acts the same way. Both computers was on static NAT on outbound and UPNP turned on. First one to get online will get moderate NAT and the other gets strict. Without the static outbound rule both game shows strict as expected. UPNP seems to work as well since I can see the requests pop up on the upnp status page. However I only can see the requests from one of the computers(whoever makes the request first).
-
@hansaya If this works, that means that static ports aren't actually necessary which goes against the general consensus. This is what pfSense does by default, and the only thing that would really be needed is for UPnP and NAT Reflection to be enabled. It would be really helpful if you could retest on latest dev again but skip setting any additional outbound rules with static ports (edit) unless there's specific ones that are known to need the option like with the switch.
-
Unfortunately, this gives me moderate for both of my PS5s. I really wish we had a working solution to this..... 3 years later.
-
@vmac That's exactly what you're supposed to get. The only way to get open NAT would be for the consoles to have a public IP themselves.
-
@marc05 If a proper UPnP was working then they would both get Open NAT. When I just had one PS5, it received an Open NAT with no issues. I'm not following why moderate is correct or would be considered "working."
-
@vmac said in Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT:
@marc05 If a proper UPnP was working then they would both get Open NAT. When I just had one PS5, it received an Open NAT with no issues. I'm not following why moderate is correct or would be considered "working."
See here: https://portforward.com/nat-types/
-
See here: https://portforward.com/nat-types/
From your link and UPnP doesn't work.
NAT Type Open
NAT Type Open is the goal when setting up an Xbox. In order to get NAT Type Open on your Xbox you need to do one of the following:Forward the Xbox Live ports in your router to your Xbox, or
Setup a DMZ in your router pointing at your Xbox, or
Have a fully UPnP compliant network. Usually, this means having a router that supports UPnP and is enabled.
Any of the above methods should net you a NAT Type Open on your Xbox. Our site recommends a port forward as the best option to get NAT Type Open. DMZ is the easiest choice, but it's a bit overkill and best reserved as a testing tool for network problems. UPnP is a really dangerous protocol and it allows any piece of malware on your network to forward a port to any device inside your home without you knowing it. We keep UPnP turned off on our routers for increased security.NAT Type Open means the following:
Your Xbox may or may not be behind a router.
If your Xbox is behind a router, then your router is aware of your Xbox and is forwarding incoming packets on predefined ports to your Xbox, usually 3074.
Your Xbox is able to receive incoming packets from the internet including connection requests from other players.
You are able to be the host of multiplayer lobbies.
You should have no limits on chat, video.
If you have NAT Type Open on your Xbox then you are done. There is nothing more for you to do. -
PFSENSE Team, What if we raise some funding so you can buy a few XBOX's and PS5's so you can test and fix all the gaming challenges including this upnp issue and make PFSENSE the perfect "Gaming Router".