PS4 Connection Errors and How To Reduce Packet Loss - MTU Setup (Advanced)

The Frontier support webpage details steps to resolve connection issues by means of optimising MTU setttings, but it appears the link provided in step 3 (http://www.letmecheck.it/mtu-test.php) is not responding.

Luckily, you can perform this check by using the DOS prompt in Windows as follows:

1. Right-click on Start, select run and type cmd to open the prompt.

2. In the DOS prompt, type ping www.google.com -f -l 1492 and hit return - you should see similar results to the following:

Pinging www.google.com [172.217.23.36] with 1492 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

3. Press the upwards arrow on your keyboard to duplicate the previous prompt entry, but lower the number of bytes sent by 50, so that it reads ping www.google.com -f -l 1442, then hit return to display the results:

Pinging www.google.com [172.217.23.36] with 1442 bytes of data:
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 21ms, Average = 21ms

You will notice there is now 0% packet loss.

4. Press the upwards arrow again to duplicate the prompt, this time increasing the number of bytes sent in small increments until you find the highest number of bytes sent with 0% loss:

Pinging www.google.com [172.217.23.36] with 1472 bytes of data:
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=21ms TTL=57

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 21ms

5. Once you have established the largest lossless packet size, add 28 to this number (for IP/ICMP headers) and you will have your optimal MTU setting. In the example above the packet size is 1472, so adding 28 makes the optimal MTU 1500.

6. Check the WAN settings on your router admin page and ensure that MTU is set to this figure.

7. Open the PS4 network settings and create a custom connection:

IP settings Automatic

DHCP host Do Not Specify

DNS Settings Manual
Primary DNS 8.8.8.8
Secondary DNS 8.8.4.4

MTU Settings Manual
MTU nnnn (nnnn being the optimal MTU setting)

Proxy Server Do Not Use

8. Finished!

Hopefully your connection will now be a little more stable.
 
The Frontier support webpage details steps to resolve connection issues by means of optimising MTU setttings, but it appears the link provided in step 3 (http://www.letmecheck.it/mtu-test.php) is not responding.

Luckily, you can perform this check by using the DOS prompt in Windows as follows:

1. Right-click on Start, select run and type cmd to open the prompt.

2. In the DOS prompt, type ping www.google.com -f -l 1492 and hit return - you should see similar results to the following:

Pinging www.google.com [172.217.23.36] with 1492 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

3. Press the upwards arrow on your keyboard to duplicate the previous prompt entry, but lower the number of bytes sent by 50, so that it reads ping www.google.com -f -l 1442, then hit return to display the results:

Pinging www.google.com [172.217.23.36] with 1442 bytes of data:
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1442) time=21ms TTL=57

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 21ms, Average = 21ms

You will notice there is now 0% packet loss.

4. Press the upwards arrow again to duplicate the prompt, this time increasing the number of bytes sent in small increments until you find the highest number of bytes sent with 0% loss:

Pinging www.google.com [172.217.23.36] with 1472 bytes of data:
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=22ms TTL=57
Reply from 172.217.23.36: bytes=64 (sent 1472) time=21ms TTL=57

Ping statistics for 172.217.23.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 21ms

5. Once you have established the largest lossless packet size, add 28 to this number (for IP/ICMP headers) and you will have your optimal MTU setting. In the example above the packet size is 1472, so adding 28 makes the optimal MTU 1500.

6. Check the WAN settings on your router admin page and ensure that MTU is set to this figure.

7. Open the PS4 network settings and create a custom connection:

IP settings Automatic

DHCP host Do Not Specify

DNS Settings Manual
Primary DNS 8.8.8.8
Secondary DNS 8.8.4.4

MTU Settings Manual
MTU nnnn (nnnn being the optimal MTU setting)

Proxy Server Do Not Use

8. Finished!

Hopefully your connection will now be a little more stable.
Great, now all I need learn is how to right click on a ps4 and I'll have it made in the shade.
 
Strange if I place the 8.8.8.8 and the 8.8.4.4. on ps4 I've got only 32mb download and 2 upload but if I leave it like it was I've got my normall 167mb download and 2.3 upload so in my case IT is seems to be not a good case .
 
Strange if I place the 8.8.8.8 and the 8.8.4.4. on ps4 I've got only 32mb download and 2 upload but if I leave it like it was I've got my normall 167mb download and 2.3 upload so in my case IT is seems to be not a good case .
Weird...changing your DNS settings should not affect your bandwidth in any way, shape or form that I know of.
 
There's a speed test after setting up a network on the PS4. I always take it with a pinch of salt.
Yes i think you are right ,is there any change some how to found out what my real up and download is on PS4 ?

Sorry, I meant: how do you know what you up/download bandwidth is? (although I think dangerzone has answered that)
No sorry thanks for your help yes what dangerzone mention .
 
Last edited:
Yes i think you are right ,is there any change some how to found out what my real up and download is on PS4 ?
I use www.dslreports.com/speedtest in the PS4's built in browser. Its more accurate than speedtest.net. It shows you what your buffer bloat rating is which is whether your routers buffer is being flooded with data. Maybe BT routers have this problem causing lag and disconnections. I'm using a Asus N66U router so I don't have that problem thankfully.
 
Last edited:
Top Bottom