DMZ not working for PS4?

[Thelolinator]

Hi all,

So if I connect my PS4 directly to the modem and give it the PPoE details from my ISP, it will have NAT Type 1, which is great for online gaming. Connected via the router and put in a DMZ, it shows NAT Type 2 and I get issues with voice chat with some people.

I've flashed my ASUS RT-N66U with the latest ASUSWRT-Merlin firmware, in the hopes that the DMZ would prove better than the stock firmware which also doesn't seem to work either.

My PS4 has a static IP assigned (192.168.1.83) and this is the IP I enter into the DMZ.

Any advice would be greatly appreciated.

 

[L&LD]

Did you reboot the entire network?

 

[matthew johnson]

Your dmz is working fine. Nat type 2 is what you will get when connected to a router of any kind even on dmz. If you were to have type 3 then dmz and correct ports would not be working or open. Type 1 is what you get when connected straight to modem. Maybe try other dns servers besides google. Try these instead or your internet provider dns. Its probably not the issue but cant hurt to try.

Level3:
Preferred DNS server - 209.244.0.3
Alternate DNS server - 209.244.0.4

 

[sfx2000]

Why are consoles so brain dead with networking - drives a lot of folks totally nuts...

Blows my mind, esp. in the current gen, with the XBone on the WinNT stack, and esp. PS4 being based on what many consider the best networking stack in the business - but still these consoles are troublesome...

 

[RMerlin]

Why are consoles so brain dead with networking - drives a lot of folks totally nuts...

Blows my mind, esp. in the current gen, with the XBone on the WinNT stack, and esp. PS4 being based on what many consider the best networking stack in the business - but still these consoles are troublesome...

Cryptic NAT modes that only exist in those console manufacturer's mind and aren't clearly documented, confusing documentation leading customers to forward ports such as 80 and 53... It's a real joke if you ask me.

 

[sfx2000]

Cryptic NAT modes that only exist in those console manufacturer's mind and aren't clearly documented, confusing documentation leading customers to forward ports such as 80 and 53... It's a real joke if you ask me.

Amen...

I know that some games on the PC/Windows environment have specific needs, but in the console space, MSFT/Sony/Nintendo/Valve could do much better here, esp since they have a fair amount of control on the network stack..

Esp. in the user case where multiple consoles on the same LAN are at play with the public internet...

crazy stuff...

 

[RMerlin]

Your dmz is working fine. Nat type 2 is what you will get when connected to a router of any kind even on dmz. If you were to have type 3 then dmz and correct ports would not be working or open. Type 1 is what you get when connected straight to modem. Maybe try other dns servers besides google. Try these instead or your internet provider dns. Its probably not the issue but cant hurt to try.

So in proper technical terms, Type I should be called "Direct/No NAT", Type II should be called "NAT with working port forwards" and Type III would be "NAT without port forward".

Funny, cause I think my descriptions are far more helpful than those imaginary NAT classes of theirs...

 

[matthew johnson]

So in proper technical terms, Type I should be called "Direct/No NAT", Type II should be called "NAT with working port forwards" and Type III would be "NAT without port forward".

Funny, cause I think my descriptions are far more helpful than those imaginary NAT classes of theirs...

Yeah its crazy the way they explain stuff. My sons xbox used to mess up all the time.

 

[reerden]

So in proper technical terms, Type I should be called "Direct/No NAT", Type II should be called "NAT with working port forwards" and Type III would be "NAT without port forward".

Funny, cause I think my descriptions are far more helpful than those imaginary NAT classes of theirs...

Just as weird as the NAT description on the Xbox. Open is "port forwarded", Moderate is "port not forwarded using default port" and Strict is "port not forwarded using alternative random port".

If you open the network troubleshooting by pressing all the triggers and bumpers after a connection test, it shows that these terms are actually based on how the STUN protocol describes how NAT networks treat UDP packages. It shows "cone NAT" for open, "port restricted" NAT for moderate and "port-preserving port-symmetric NAT" for strict.

Not necessarily wrong if the Xbox Live server uses STUN, but confusing to the end user nonetheless. I like how they give easy names to how the STUN server sees your NAT network, but forget to tell you what's is actually wrong with it in the first place.

 

[sfx2000]

Hole-punching thru NAT's and Firewalls should be easier than what the console vendors have done - and a great opportunity for the vendors to improve.

This should be completely seamless to the end-user - not that it's impossible to do, entirely possible to do - if BitTorrent and Skype can do it at the app level...

oh well...

 

[RMerlin]

Hole-punching thru NAT's and Firewalls should be easier than what the console vendors have done - and a great opportunity for the vendors to improve.

This should be completely seamless to the end-user - not that it's impossible to do, entirely possible to do - if BitTorrent and Skype can do it at the app level...

oh well...

And that's what UPNP/NAT-PMP/PCP are for.

 

[Thelolinator]

Hi all,

Thanks for the replies! I always assumed that placing the PS4 in a DMZ would essentially open it up to the internet, essentially the same thing as connecting directly to the modem.

Did you reboot the entire network?

Yes, I tried that.

Your dmz is working fine. Nat type 2 is what you will get when connected to a router of any kind even on dmz. If you were to have type 3 then dmz and correct ports would not be working or open. Type 1 is what you get when connected straight to modem. Maybe try other dns servers besides google. Try these instead or your internet provider dns. Its probably not the issue but cant hurt to try.

Level3:
Preferred DNS server - 209.244.0.3
Alternate DNS server - 209.244.0.4

Right I see, thanks! Didn't really make any difference, but was worth a try.

So am I correct in assuming that no matter what I do, unless the PS4 is connected directly to the modem I won't be able to get Sony's definition of 'NAT Type 1'?

Thanks!

 

[RMerlin]

Hi all,

Thanks for the replies! I always assumed that placing the PS4 in a DMZ would essentially open it up to the internet, essentially the same thing as connecting directly to the modem.



Yes, I tried that.



Right I see, thanks! Didn't really make any difference, but was worth a try.

So am I correct in assuming that no matter what I do, unless the PS4 is connected directly to the modem I won't be able to get Sony's definition of 'NAT Type 1'?

Thanks!

Forget about NAT 1. From what I gather, it means being directly connected to the Internet, without NAT, and without any firewall either.

 

[sfx2000]

And that's what UPNP/NAT-PMP/PCP are for.

Yep, when it works properly

 

[greg50]

And that's what UPNP/NAT-PMP/PCP are for.

I don't know how it works exactly, but is there a way to not enable these solutions (like UPnP - and with that open those ports) but to log the ip and the port when a request like that comes in, so you can maybe open it for them manually? Or is there a way to enable these solutions only for a specific device (like a console)?

 

[RMerlin]

I don't know how it works exactly, but is there a way to not enable these solutions (like UPnP - and with that open those ports) but to log the ip and the port when a request like that comes in, so you can maybe open it for them manually? Or is there a way to enable these solutions only for a specific device (like a console)?

Ports required by the PS4 are already well documented.