NAT Type 3 on PS4 - I've tried everything I can think of
-
PS4 is reporting a Type 3 NAT which is restrictive. I've tried what I thought would fix it, and I've looked up many threads with similar issues and I cannot seem to resolve this.
I've tried it with NAT and Port Forwarding and with Aliases. Anyone have any ideas?
 -
Anyone have any input? I've got a useless ps4 as of right now
-
1. Your second Port Forward Rule is setup for TCP. Change it to UDP.
2. Your PS4 Outbound NAT Rule says Static Port NO. Change it to YES.
3. Not important for the PS4 but your Localhost Outbound NAT Rule should have Static Port NO.
Should have posted this in the Gaming Sub Forum.
-
1. Your second Port Forward Rule is setup for TCP. Change it to UDP.
2. Your PS4 Outbound NAT Rule says Static Port NO. Change it to YES.
3. Not important for the PS4 but your Localhost Outbound NAT Rule should have Static Port NO.
Should have posted this in the Gaming Sub Forum.
I did everything you suggested and it is the same as before, type 3 NAT unfortunately.
I apologize, I didn't realize there was a gaming forum, I headed straight to to the firewall section. I'll post over in the correct forum.
-
Started over from scratch, still nothing. New settings are attached to this post.
-
I have my PS4 on a seperate port. DMZ basically.
Outbound is open, and just a bunch NAT and Rules to hook it up to a Type 2 just fine.If you can give it a dedicated port on your router/firewall machine, I can show you some screenshots.
-
@weust:
I have my PS4 on a seperate port. DMZ basically.
Outbound is open, and just a bunch NAT and Rules to hook it up to a Type 2 just fine.If you can give it a dedicated port on your router/firewall machine, I can show you some screenshots.
I can but I'll have to buy a new card. I'll definitely do that if I can't get it situated. Thanks!
-
Had it working with m0n0wall and since a few days now with pfSense.
And back in september even through Hyper-V.I've been running like this since the beta of Destiny.
I will get some screenshots up. -
@weust:
Had it working with m0n0wall and since a few days now with pfSense.
And back in september even through Hyper-V.I've been running like this since the beta of Destiny.
I will get some screenshots up.I appreciate that, thank you!
-
Have you tried turning on uPNP?
Or are you behing a router thats behind another router or something like that? -
My setup is a Soekris net6501-30 which has four Ethernet ports.
em0 = WAN
em1 = LAN (192.168.1.0/24)
em2 = OPT1 (not used)
em3 = OPT2 (192.168.2.0/24) (PlayStation 3 and 4. Cable switch at the console end)My PS4 and PS3 are both on 192.168.2.10/24 as I couldn't be bothered figuring out how to do it for two IP addresses.
I just switch the cable between the two.
Also, I set the IP address manually as you can only set one IP address on one MAC address.
And since it's only two consoles, who cares…First is to enable the interface you're hooking up the PS4, and give it an IP address.
Don't forget to set the mask as the default is /32 which took me some digging around as to why the console couldn't connect to at all...
I know I didn't use the Private Networks options. Perhaps I should enable it just in case.
Next is to add NAT Port Forwarding. Let it at a Firewall Rule as well.
I brushed one line away as that has nothing to do with the PlayStation forwarding.
Second is to set NAT Outbound. I am not paranoid enough to set specific ports for outbound, so I let it all go from the console to the internet.
Mind the Static Port is set to YES.
Below is the Rules list created by the NAT Port Forwarding.
The Rules for PLAYSTATION include IPv6, but that was mainly as a copy from LAN.
I don't IPv6 at all here at home as my ISP does not use it yet.
Hope this helps. Let me know if you run into trouble. I might have forgotten to mention something :D
-
Can you try going into services > upnp and turn on upnp?
-
Have you tried turning on uPNP?
Or are you behing a router thats behind another router or something like that?I have not.
My setup is modem - pfsense box. Coming out of the pfsense box on the lan port I have a linksys router acting as a wifi AP and a switch, DHCP and firewall are both off.
I'll turn on uPNP shortly when I get home.
-
If uPNP doesn't do it for you try to eliminate the AP.
If thats feasible. -
If uPNP doesn't do it for you try to eliminate the AP.
If thats feasible.I have a brand new 16 port gigabit switch I can plug in and test with if need be. It can't stay there, but I can certainly use it to test.
-
That sounds like a very good idea.
-
That sounds like a very good idea.
Alright -
Pulled the AP (which is a Linksys E2500 running TomatoUSB) and put in my 16 port Netgear gigabit switch. Still the same with a Type 3 NAT.
I removed pfSense and reset my Linksys after backing it up, and it connects to problem with a Type 2 NAT.
Turn on uPnP with the AP removed and still nothing, same with it connected.
Showing traffic for the PS4 in uPnP status on pfSense as well.
-
Not sure if it will help, but I found this:
http://www.playstationlifestyle.net/2014/02/08/possible-ps4-firmware-upnp-bug-and-workaround/
-
Not sure if it will help, but I found this:
http://www.playstationlifestyle.net/2014/02/08/possible-ps4-firmware-upnp-bug-and-workaround/
Seems like a plausible cause, but I've ran the network connection test and it always comes back with a type3.
On another note, I've purchased another nic and it got here last night. In the meantime, I think I'm just going to put it on it's own network and make it a DMZ and run the PS4 from there for the time being. Definitely not how I want to run my network, but I'm tired of switching over to an old router router every time I play on the PS4.
-
When you look at the dashboard of your pfsense, is the WAN IP a public or private IP?
