PfSense and the PS5 NAT2/NAT3 problem
-
Rather than skirt around it, let me say upfront that my problem is getting my PS5 to see a NAT2 configuration rather than NAT3. With the latter, many multiplayer features stop working.
I have a Netstat3100 at home as follows:
ISP modem -> Netstat 3100 -> Netgear ORBI
There are wired and WiFi devices. The PS5 uses WiFi. I have a list of ports that the PS5 uses, and I think I could set up port forwarding, but should be able to use UpnP (easier, no static IPs…)
Has anyone got such a configuration working, and if so could you please share what you did? The Orbi is simple enough, but I am new to pfSense.
-
@mdecyk Follow this video guide, it works perfectly:
https://www.youtube.com/watch?v=whGPRC9rQYw
Now, I will have to say, you need to use your Orbi as a simple access point, it can't be doing any routing in this scenario.
-
Thank you, that’s exactly what I needed. That, and a wood chipper to “configure” the Orbi. It won’t release existing leases, and doesn’t seem to want to pass DHCP requests to pfSense, but I will figure that out.
@akuma1x said in PfSense and the PS5 NAT2/NAT3 problem:
@mdecyk Follow this video guide, it works perfectly:
https://www.youtube.com/watch?v=whGPRC9rQYw
Now, I will have to say, you need to use your Orbi as a simple access point, it can't be doing any routing in this scenario.
-
Changing the setting from Router to AP was key: thanks for noting it.
PS5 sees NAT2 now. There was great rejoicing.