NAT Type 3 on PS4 - I've tried everything I can think of
-
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?
-
When you look at the dashboard of your pfsense, is the WAN IP a public or private IP?
I'm not sure where it says that exactly…
-
Upper right hand corner.
It will say WAN interface IP.
What is that IP?
Its a number like 173.213.81.1 or something…
-
The reason I'm asking about that IP is because if its private, like 192.168.1.1, then you are Double NAT and nothing you do is going to work properly.
You would need to make your modem pass a public IP to pfsense WAN.
-
Oh! I misunderstood your first question. My modem is set in bypass mode, it does not do anything firewall or routing related.
The reason I'm asking about that IP is because if its private, like 192.168.1.1, then you are Double NAT and nothing you do is going to work properly.
You would need to make your modem pass a public IP to pfsense WAN.
-
OK - So then you have verified that the the pfsense wan has a public IP?
-
OK - So then you have verified that the the pfsense wan has a public IP?
I haven't made it homs yet, but I'm certain it does. I use dyndns to maintain remote access to it.
-
The reason I want to check that is because unless you are running multiple LAN segments, with uPNP up, this should be simple. Unless its double NAT
-
So I've been scratching my head on how to get this to work. I've followed the guide and I would get a NAT2 on the PS4 but unfortunately I cannot connect to any online games. These are my settings as followed and I am on Pfsense 2.2 with Hybrid on.
Mappings.
Interface Source Source Port Destination Destination Port NAT Address NAT Port Static Port
WAN GameConsoles * * * WAN address * YES
VPN1 10.11.1.0/24 * * * VPN1 address * NO*Game consoles is an alias for my IP's for the consoles (xbox one and ps4)
Automatic rules:
Interface Source Source Port Destination Destination Port NAT Address NAT Port Static Port Description
WAN 127.0.0.0/8 10.11.1.0/24 10.10.21.0/30 * * 500 xxx.xxx.xxx * YES Auto created rule
WAN 127.0.0.0/8 10.11.1.0/24 10.10.21.0/30 * * * xxx.xxx.xxx * NOAny suggestions?
-
Where did you get the idea to use static on your outbound nat for every single port? That makes NO SENSE as setting, and will surely break stuff!
"I haven't made it homs yet, but I'm certain it does. I use dyndns to maintain remote access to it. " Sorry but dyn dns doesn't mean that pfsense has a public IP.. Sorry but most setups uses end up being behind a double nat.. Unless you have specifically setup the device from the isp in bridge mode, or have actual just cable modem and not a gateway like they like to hand out when they sign you up for tripleplay, etc. etc.
Have you validated that you are seeing UPnP request to pfsense via sniff?
-
Missed some replies here, but was thinking about this topic after I switched from things around in my own setup.
Reason is that I wanted to control the YouTube app on the PS4 from my iPad, but also connect the PlayStation app to my PS4.I plugged the PS4 into my switch, which has the uplink from my pfSense box, and gave is the IP address 192.168.1.60.
Then I edited the Rules for each of the ports opened for 192.168.2.10 (old IP address of PS4 in seperate subnet/DMZ) and changed the IP address to the new one.I then added a NAT rule to allow Static Port on 192.168.1.60, and placed that line above the 192.168.1.0/24 line.
And I got NAT2 on the PS4 again.To johnpoz, why wouldn't you enable Static Port for every port from the specific IP address of the PS4?
After months of playing Destiny like this I yet have to see anything break.
