I actually just got this to work, YMMV since set ups are so different like my VLAN usage, etc. but it does work for me now.

The dedicated server has a built in network test that they do to ensure it can "communicate" properly. I saw some forum post on steam discussions and reddit (https://www.reddit.com/r/SonsOfTheForest/comments/14jo4y0/bug_with_the_new_dedicated_server_tools/) about users being able to play/connect even though the network test failed. Most likely it is either a bug with the network test being used or just that is unfamiliar with the way packets are being handled by pfsense.

So most of my set up was actually good and working. Setting NAT + Proxy mode allowed the self-test to pass but as stated only external friends could connect and see the server, I was unable to do so at all. A post mentioned they were using Pure NAT setting for NAT reflection - I tried that and the network self-test failed in the dedicated server. From a suggestion from a user, I tried Pure NAT again and then added the following in the server config file: "SkipNetworkAccessibilityTest": true. This skips the built-in network self-test that is problematic with pfsense NATing or either has a bug as stated.

I then was able to see the server in Steam Public List and connect properly. Side note, I am not able to see the server at all in LAN list probably due to VLAN and/or subnet differences. But that is not a big issue since I can connect via public listing. I hope this helps any other users experiencing similar issues

@DonZalmrol

Can you provide a detailed view of the relevant NAT rule settings for those of us who are not so savvy?

@jonathanlee everything else works roblox, amazon prime, disney plus. Tubi works for one movie only and requires app reset to work again.

@gblenn for what ever reason that doesn't work on my end.
I've tried that, tried restarting pfSense tried changing my static IP, rebooting my desktop and nothing.
Starting to think I'll either have to move to a normal router, or just give up on the hopes of it working correctly.

@kenhans I'm pretty sure you have things set up as they should be in pfsense already. I mean the only thing you need is the port forward of 10308 to the DCS appliance (which needs to be on the pfsense subnet and under it's DHCP server).

If I read things correctly the issue was that you had your wifi-router set up and connected as a router still...?

You need to treat it like a switch, and give it an IP in the same range as your pfsense (within the static range preferably). Unlike a managed switch it will probably not pick up an IP handed out by pfsense.
AND you need to dumb it down and turn off the DHCP server which would otherwise be conflicting with pfsense. After that you can call it an AP basically... and all you need then is to move the cable you had coming from pfsense, from the WAN to one of the LAN ports, and you are all set to go...
Some wifi-routers allow bridging of WAN to LAN when used as an AP. This would give you 5 switch ports instead of 4...

@fox-hound For me it's been COD MW2/3 that have always been the most difficult to handle. Before I upgraded to 22.05 (2.7.0) I never got more than Moderate NAT without using UPnP AND port forward of 3074. If I'm not mistaken I also had to use static ports in Outgoing NAT.

Now after the upgrade, UPnP handles everything as it should...

Although UPnP works when using something other than a private IP on WAN2, it does break the Dynamic DNS update.
Normally pfSense will use http://checkip.dyndns.org to get the IP address IF it detects a Private IP on the monitored port. If not, it will assume it is the correct IP which means the DDNS will be incorrect.

As there doesn't seem to be a way to force it to use that checkup service so I guess it's back to using port forwards for MW3 on the WAN2 port ...

@dbmandrake said in pfSense multiple PCs, open NAT: a solution, and a grievance:

@permachill said in pfSense multiple PCs, open NAT: a solution, and a grievance:

@gblenn

Well what's not working was being able to have 2 people open the game at the same time, the second person gets a network error that they can't connect to mw2 servers.

Weird. Haven't tried that game but we have had two Xboxes joining the same Roblox server instance and playing together without problems since configuring UPnP with the patch...

That is wierd...
@permachill, which version of MW2 are you referring to?

The 2009 version doesn't use port 3074. Testing just now, I see ports 28960-28962 showing up as external ports and 28960 as internal (remapping as it seems?)

The 2022 version is asking for port 3074 and perhaps 3075 etc if that is not available. Interestingly it seems to ask for the port being closed when you leave the game, as 3074 disappears from the list immediately.

I will add one note -> port config was definitely the issue in my case but not sure how using PIA vpn on my primary gaming PC was able to alleviate the issue because as i mentioned, connecting over a vpn to COD servers would work, despite the pc being connected to the same problematic span port.

@issa
pfsense does not block any outgoing traffic by default.

did you add block/reject rules on LAN?
if yes=>remove those rules

do you use packages like squid / snort / surricate / pfblockerng ?
if yes => remove/disable those packages

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

@yorke I would have to research this more. Thanks for the reply.

@natethegreat21 I will also note that this windows machine is a VM

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

I don't care if this post is old...bump for an awesome solution!

2 days I've spent on this trying countless "solutions" I found searching Google - all of which failed. This took me about 10 minutes total and just like that, my kid and I were gaming together again.

Thanks OP. I hope others in agonizing pain ready to delete pfSense (like me) find this!!