MTU Setting

[#1]

I think you are still missing the point.

The default MTU set in the router is simply the maximum packet size allowable on YOUR network.

The default value in the router is not necessarily the BEST setting for your connection.

The MTU value can be anything from 576 to 1500.

1492 is not a magic number which makes things work, it is just the max for PPPoE on old routers.

The router MTU should be set to a value which doesn't cause ping fragmentation.

You should measure this using How to find the proper MTU size for my network

If the router MTU can't be set, then all the devices on your network should manually be configured to the next lower MTU that doesn't result in ping fragmentation.

Setting MTU to 1492 isn't a magic cure all,  on my network I have had routers that perform best with MTUs of 1430, 1458, 1472, or 1478.  MTUs of 1492 or 1500 {or 1488} are just the maximum that hardware is capable of, and not necessarily the optimum value for YOUR connection.  As an example when I used a Netgear DG834GT, that had a maximum settable MTU of 1500, but my network had problems if MTU was set above 1468, but for absolute fastest and reliable performance, setting MTU to 1430 gave the best results.

By all means buy a new router, but get one that performs better than the HH5, not just to change the MTU.

At this time, if you are going to spend hard-earned money on a new router, then make sure it supports "baby jumbo frames" on the WAN PPPoE ethernet connection, because that will allow you to set an MTU of 1500 when coupled with a compatible modem on a  BT FTTC fibre connection.

[#2]

@Anonymous

Thanks for your reply. And your help.

As I mentioned, I've measured the MTU size for my network

Manually changing it on anything except the router does not resolve the issue in question.
I'm quite happy with both the HH5 and PNH1 they both seem basically the same and work well for me apart from in this instance.
At this point I think my only option it to try a different router.

Jumbo frames, got it. Will take a look.

Edit: The Netgear D6400 is around £40 less than it was yesterday so I've opted for that, it has to be worth a try.
Couldn't find any info on whether it does baby jumbo frames though.

[#3]

Good luck with the new router, please let us know how it goes.

While you're waiting for the new router, have you tried rebooting the hh5? This will cause a gateway change which may or may not help with your present problems -- always worth a try.

Also you could try assigning google dns settings in the PS, don't think you can change the dns in the hh5, changing dns sometimes help with obscure problems.

Google dns settings

Primary dns: 8.8.8.8

Secondary dns: 8.8.4.4

[#4]

I have just spent half-an-hour googling this issue, and I'm not convinced that this is an MTU issue at all, and many people who have changed routers have said that doing so didn't fix their issue.

Many people are saying that their Playstation setup WAS working perfectly for years, then something changed and this error started occurring.  Many have tried optimizing MTU without success.

Most people are blaming a Sony update, as issues simultaneously appeared worldwide.

The Playstation software seems unreasonably intolerant to fragmentation which will occur from time to time.

Others have noted that BT's network has periods where fragmented UDP packets get blocked on their core-network and cause PSN and VPN traffic to either fail, or to report errors.

Unfortunately I have not discovered any reliable solution to your problem so I don't know what to suggest (other than get an Xbox )

[#5]

---

@npr wrote:

Good luck with the new router, please let us know how it goes.

While you're waiting for the new router, have you tried rebooting the hh5? This will cause a gateway change which may or may not help with your present problems -- always worth a try.

Also you could try assigning google dns settings in the PS, don't think you can change the dns in the hh5, changing dns sometimes help with obscure problems.

Google dns settings

Primary dns: 8.8.8.8

Secondary dns: 8.8.4.4

---

Will do, it should be here tomorrow so not too long to wait.
Yeah I tried restarting HH5 and even swapping it back to the Hub One and factory resetting both but no joy.
Your right, I can't change the dns in the HH5 or Hub One but tried using google dns settings across the PS devices, no change

[#6]

The Playstation software seems unreasonably intolerant to fragmentation which will occur from time to time.

I think that's spot on.

Unfortunately I have not discovered any reliable solution to your problem so I don't know what to suggest (other than get an Xbox Cheesy)

I have an Xbox One, it won't surprise you that it works fine

I have just spent half-an-hour googling this issue, and I'm not convinced that this is an MTU issue at all, and many people who have changed routers have said that doing so didn't fix their issue.

Really appreciate your time. Over the last 2 plus weeks I must have read every post on the matter that has made me  bit Doesn't seem to be a solution.
The only success I've had is trying it on a mates network, fingers crossed I get some joy with a replacement modem/router I have to try it at least.

[#7]

As we're all out of ideas, you could test a tracert to the PS network to see what that throws up

This is mine from a BT connection:

C:\Users\npr>tracert auth.api.sonyentertainmentnetwork.com

Tracing route to e883.b.akamaiedge.net [173.223.184.104]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  ZyXEL.Home [192.168.1.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    22 ms    21 ms    20 ms  31.55.185.184
  5    21 ms    21 ms    21 ms  core2-hu0-17-0-1.colindale.ukcore.bt.net [195.99.127.156]
  6    22 ms    21 ms    21 ms  peer6-hu0-1-0-1.telehouse.ukcore.bt.net [195.99.127.25]
  7    19 ms     *       21 ms  195.99.126.154
  8    20 ms    20 ms    20 ms  ae00.core02.lon01.uk.as5580.net [78.152.53.226]
  9    21 ms    20 ms    21 ms  ae00.edge01.lon02.uk.as5580.net [78.152.44.163]
 10    22 ms     *       22 ms  78.152.55.62
 11    20 ms    20 ms    21 ms  a173-223-184-104.deploy.static.akamaitechnologies.com [173.223.184.104]

Trace complete.

[#8]

No idea what that is but here's what it came up with.

[#9]

Nothing there, sorry.

Is the PS permanently switched on?
If so try switching off for 30 minutes.

[#10]

Was worth a look, thanks.
Yeah kept them unplugged for almost a full day though just to try.

[#11]

I for one would like some clarification on what the MTU on the Hub One and the HH5A is? I think @bobpullen may know and be able to tell us.

[#12]

There have been topics on this before, and it appears that the MTU is 1488 by default.

Regardless of whether the maximum MTU is 1488 or not, 

I would like to know whether it really the case, that the MTU can't be altered, because if it can't then network MTU discovery (by other devices on the LAN) will be a disaster if the default MTU happens to cause fragmentation on a customers internet connection.

[#13]

Do you have a link where @bobpullen has stated what it is?

[#14]

No.

Google has a lot of results for HH5 MTU 1488,  so this isn't a problem restricted to Plusnet.

I'm not sure that 1488 is a problem, but not being able to change it is (if true).

[#15]

Well the HH5B is 1492, the 2704n is 1492, I'm baffled as to why the Hub One should be different - rebadged HH5A but with Plusnet skinning and some minor changes like no BT WiFi hotspot. Whilst I accept it might be different, I'd rather hear it from the horse's mouth, so to speak.