@Sherwatt said in Unable to do Open NAT in pfSense 2.7.2-RELEASE:

No, we play different games, so this shouldn't be a problem. :)

Unless they require the same port... Which for example many Activision games do, like port deamonware port 3074. But then again, they usually have the ability to select alternative ports as well. So with UPnP they should be able to retry another if the first one is already in use.

I found the issue I changed the OPT1 name and it would not change in the config.xml so it does not bind to the new name, I set it back to OPT1 after seeing that the config.xml did not recognize this as selected for upnp section of the code and it worked.

It is like the name change messed up somehow

@JonathanLee I block DNS over HTTPS to the firewall using unbound because I have unbound running DoT. My solution to the Nintendo griping about DNS was to route it out to 1.0.0.2. I was also having issues with unbound using the ephemeral ports I was using, interrupting my sensitive codel games so had change localhost's NAT outbound.

@stephenw10 Managed to solve it myself. I don't know how I missed this before when I created the VLAN's I created them on igb2 rather than igb1 which is where my LAN network resides. I changed that and now everything is working fine as it was before I started a fresh configuration. Thank you for the suggestions anyway!

@Chris78 Sorry to sort of resurrect this.. I went through all of the instructions , my intent was to have all traffic go through the VPN yet no luck :(
Could pfBlockerNG be the cause?
I'll admit this is a LOT of steps to go through and so much could go wrong

Thank you