Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT

borediniraq

@m0t0k0 I'm having the same problem with WZ on 2 XBOX consoles

m0t0k0

@borediniraq I gave up and moved back to OpenWRT works with just the click of a button

andrew_r

I'm not sure when it happened, but I installed the latest dev update as of last night and it's broken this again.

andrew_r

Update: false alarm; somehow something changed in one of the updates that broke my OpenVPN connection. "Fixing" that ended up routing ALL traffic through the VPN. Breaking it again fixed the NAT problem, but there is still something squarely with the OpenVPN client rules.

I hadn't changed anything in the rules before it stopped working. I'll try setting it up again from scratch to see if that fixes it, but...

Hopefully the 2.5.0 stable release will be out soon, that's all I can say on that! :/

JeGr

@jimp quick question as this popped up in my subforum: does the new miniupnp daemon to test or the version in 2.5 also have the patch for https://redmine.pfsense.org/issues/10398 included?

Namely that was this miniupnp discussion: https://github.com/miniupnp/miniupnp/issues/433 about problems with RFC1918 addresses on WAN.

Also: the snapshots now already contain the new version, no need to manually patch/install it anymore?

Thanks,
\jens

goonie

Is this topic really going to die like all the other previous topics on this same issue over the years. This has been ongoing for years now. Can we get a little more developer traction on this issue? What is needed at this point from the pfSense side of things? What is needed for the miniupnpd side of things? Please, lets not let this die again.

jonathanjadams

I would also be interested to see if there has been any advancements on this.

Has anyone managed to get this to work?

Marc05

I think what's lacking at the moment is sufficient testing. The package responsible for UPnP has been update and is available in 2.5.0. Testing this requires a hardware setup that many don't have - if you're interested in resolving this and have the multiple consoles, multiple copies of the same game, and the time to test things, please do.

jonathanjadams

@Marc05 Thanks for getting back so quickly.

I do have multiple Xbox Ones with the same game (note that some people including myself have been having issues with Ghost Recon Wildlands) and some time to provide some testing. My knowledge is not 100% but I can certainly give testing ago.

Before I upgrade to v2.5 can I just confirm how best to conduct the testing:

I have successfully gained Open NAT via the use of Outbound NAT rules and static ports as well as UPNP ACLs. My xboxes are contained within their own specific VLAN.

Do I just need to remove all UPNP ACLs and Outbound NAT rules and then test to see if I get open NAT across consoles as well as seeing if I can play online in games I have previously had problems with?

Marc05

@jonathanjadams

It's important to first get a baseline of what works/doesn't. The basic configuration that should be currently in place is:
System / Advanced / Firewall & NAT

NAT Reflection mode for port forwards: Pure NAT
Enable automatic outbound NAT for Reflection: Checked

Firewall / NAT / Outbound

Rule with the following: Interface: WAN | Source: Alias with console IPs | NAT Address: Interface IP | Static Port: Checked

Firewall / Rules / LAN (or whichever interface the consoles are on)

Rule at top with the following: Protocol: UDP | Source: Alias with console IPs | Destination: Any | Allow IP options: Checked

Services / UPnP & NAT-PMP

Enabled with UPnP & NAT-PMP both checkd
External Interface: WAN
Interfaces: LAN (or whichever interface the consoles are on)
Default Deny: Checked
ACL: (e.g.) allow 0-65535 10.0.5.0/24 0-65535

Test
After these settings are set, power off the consoles, reboot the firewall (to clear states, old mappings, and ensure a control state for testing), then power on the consoles. Now test the same game at the same time on two consoles.

Does it work?
What is the output of (Diagnostics / Command Prompt): pfSsh.php playback pfanchordrill

Now upgrade to 2.5.0 and run through the same test steps. Please back up the configuration before upgrading.

jonathanjadams

Thanks @Marc05 my settings are exactly as you have them. I will do some testing and post my results here.

chrcoluk

@jimp said in Test Request: UPnP Fix for Multiple Consoles playing the same game / static port outbound NAT:

miniupnpd

Here is the github issue.

https://github.com/miniupnp/miniupnp/issues/226

Ideally if we could see the rules created on linux, then its trivial from that to send the correct syntax to that github post, and then I expect we will see progress.

goonie

My network setup:

cable modem -> pfsense (WAN igb0) -> Access Point (opt1) (igb1)
                                  -> opt2 (igb2)
                                  -> opt3 (igb3)

Xbox One 1 Static IP: 10.100.100.100 Port: 56450 (wired) (igb2) 
Gateway: 10.100.100.1
Xbox One 2 Static IP: 10.200.200.120 Port: 53063 (wireless) (igb1)
Gateway: 10.200.200.1

Ignore the PS4 info as well as any other irelevant IP's in the miniupnd debug info I posted below since I was only testing the 2 Xbox One's.

PS4 Static IP: 10.0.0.100 (igb3)
Gateway: 10.0.0.1
PS4 Static IP: 10.200.200.121 (igb1)
PS4 Static IP: 10.200.200.122 (igb1)
Gateway: 10.200.200.1

My miniupnpd.conf file:

ext_ifname=igb0
port=2189
listening_ip=igb1
listening_ip=igb3
listening_ip=igb2
secure_mode=yes
system_uptime=yes
presentation_url=https://10.200.200.1:30000/
uuid=c09cf14b-f345-e551-63c7-0514bc6bb0d
serial=C09CF14B
model_number=20.7.3
allow 53-65535 10.200.200.120/32 53-65535
allow 53-65535 10.200.200.121/32 53-65535
allow 53-65535 10.200.200.122/32 53-65535
allow 53-65535 10.100.100.100/32 53-65535
allow 53-65535 10.0.0.100/32 53-65535
deny 0-65535 0.0.0.0/0 0-65535
enable_upnp=yes
enable_natpmp=no
clean_ruleset_interval=600
min_lifetime=120
max_lifetime=86400

I manually built miniupnpd from source:

root@pfsense:~ # miniupnpd --version
miniupnpd 2.2.0-RC1 Aug 23 2020
using pf backend

My Build Options for Miniunpd:

CHECK_PORTINUSE: on
IPV6           : off
LEASEFILE      : off
PF_FILTER_RULES: on
UPNP_IGDV2     : off
UPNP_STRICT    : off

Unforunately I couldn't run a test where I only had just the 2 Xbox One's connected to the network. I ran miniupnpd in debug mode. I had other devices connected wired and wirelessly. Ignore anything except for the Xbox One static IP's and their gateways. I started both of my Xbox One's at the same time and started the same game (Apex Legends) at the same time. I then attempted to play same game with both xbox's while in the same lobby and it didn't work. One of the Xbox's would not connect but the other would. See the output below at pastbin.com since I couldn't post the entire output here:

miniupnpd runnning in debug mode

goonie

I wanted to add the below information in my original post as well but the forum wouldn't allow me after a certain amount of time ellapsed.

I was able to achieve Open NAT for the "Xbox Live Service" for both Xbox One's. Gaming is completely separate from the Xbox Live service where the problem resides. miniupnpd did not add any port mappings for the game Apex Legends only for the static port that each Xbox One has port 56450 & port 53063. Search the miniupnpd debug log I posted at pastbin and you will only see 2 AddPortMapping requests. There should have been more port mapping requests for the port dynamically needed for the game Apex Legends. Unfortunately, this was not the case.

aniel

what is the state of this, has it been fixed/ implemented ?

food007

@Marc05,
I have performed a test per your previously listed specifications.

Here is my testing scenario:

Devices:
- Firewall: Netgate SG-3100 on 2.5.0-DEVELOPMENT (built on Thu Nov 12 12:57:50 EST 2020) - 192.168.1.1
- Consoles: 1x PS4, 1x PS4 Pro - 192.168.1.2/31 respectively
- Test game: Tony Hawk's Pro Skater 1+2 (uses same ports as EA COD games)
- admin pc - 192.168.1.106

First, I reset the device to factory defaults, then followed your instructions to the letter, with the additional pre-work steps as follows:

Uncheck DHCPv6 Server for LAN interface and set IPv6 Configuration Type on the LAN interface to None
(i.e. steps to disable IPv6 on LAN interface)
Create static DHCP reservations for two consoles
Create an alias containing both of the consoles' IPs

My UPnP ACL is allow 0-65535 192.168.1.2/31 0-65535.

--
I unplugged the consoles from power to make sure they were completely off. Next, I rebooted the SG-3100. After pfSense fully booted, I plugged the consoles back in to power and started them up. Answers to your questions are below:

Test

Does it work? No - One console can connect and play fine, but the other can not start game sessions or join lobbies
What is the output of (Diagnostics / Command Prompt): pfSsh.php playback pfanchordrill

ipsec rules/nat contents:

miniupnpd rules/nat contents:
nat quick on mvneta2 inet proto udp from 192.168.1.3 port = 9308 to any keep state label "192.168.1.3:9308 to 9308 (UDP)" rtable 0 -> 68.186.83.135 port 9308
nat quick on mvneta2 inet proto udp from 192.168.1.3 port = 9306 to any keep state label "192.168.1.3:9306 to 9306 (UDP)" rtable 0 -> 68.186.83.135 port 9306
nat quick on mvneta2 inet proto udp from 192.168.1.2 port = 7777 to any keep state label "DemonwarePortMapping" rtable 0 -> 68.186.83.135 port 7777
nat quick on mvneta2 inet proto udp from 192.168.1.3 port = 7777 to any keep state label "DemonwarePortMapping" rtable 0 -> 68.186.83.135 port 7898
nat quick on mvneta2 inet proto udp from 192.168.1.2 port = 3478 to any keep state label "DemonwarePortMapping" rtable 0 -> 68.186.83.135 port 3478
rdr pass quick on mvneta2 inet proto udp from any to any port = 9308 keep state label "192.168.1.3:9308 to 9308 (UDP)" rtable 0 -> 192.168.1.3 port 9308
rdr pass quick on mvneta2 inet proto udp from any to any port = 9306 keep state label "192.168.1.3:9306 to 9306 (UDP)" rtable 0 -> 192.168.1.3 port 9306
rdr pass quick on mvneta2 inet proto udp from any to any port = 7777 keep state label "DemonwarePortMapping" rtable 0 -> 192.168.1.2 port 7777
rdr pass quick on mvneta2 inet proto udp from any to any port = 7898 keep state label "DemonwarePortMapping" rtable 0 -> 192.168.1.3 port 7777
rdr pass quick on mvneta2 inet proto udp from any to any port = 3478 keep state label "DemonwarePortMapping" rtable 0 -> 192.168.1.2 port 3478

natearly rules/nat contents:

natrules rules/nat contents:

openvpn rules/nat contents:

tftp-proxy rules/nat contents:

userrules rules/nat contents:

Output of miniupnpd --version is

miniupnpd 2.2.0-RC1 Nov 11 2020
using pf backend

Additionally, I would like to note that when running the "Test Internet Connection" program from the PS4 Settings menu, one console comes back with a "NAT Type" of "Type 2", while the other comes back with a "NAT Type" of "Failed".

It was mentioned earlier in this thread that this is somewhat of a niche problem with not enough testers with sufficient hardware. I am more than willing to test this out on the testing environment listed above.
I believe this is a bigger deal than just a niche problem, especially seeing how COTS routers from major brands can handle this situation out of the box, and how long this issue has been open.

If there is any information I can provide that would make my testing more useful, please let me know.

w26

trunix

@food007 Maybe try two separate ACL entries, the first "allow 0-65535 192.168.1.2 0-65535" and the second "allow 0-65535 192.168.1.3 0-65535" if .2 and .3 are the addresses of your PS4s.

food007

@trunix , sure. I can try that. I will change the setting, test, and report back.

I don't think it should change anything though, as even the helper text above the ACL Entries field uses CIDR notation for its example. (see highlighted text in pic... screenshot from 2.4.5, but I believe the helper text is the same in 2.5.0 as well)

aniel

@food007 where u able to test it out ?

food007

@aniel Yes, I tested specifying each address individually... no difference.