In reply to a post by RobertoS:

As I said, mine is set to 1500 by Three, who have full updating access so they would change it if they thought that was needed.

Curious. My B535 was supplied in mid-July on a 30-day contract, set to 1440.

I can confirm 1500 did not report ICMP fail with DF when I tested before Monday (Sept 7), but did fail when tested after (including just now).

Edited by richi (Mon 14-Sep-20 15:07:23)

My 5G Huawei is also 1440

In reply to a post by kams19:

Looks like Three got the hint of whats wrong from your post
IN any case, three subscribers are happy if the network remains like this!

I know plenty of people were hammering on them since before I started having problems back in May.

I did spend some considerable time and effort sending them results of tests, as requested by the techs. It became clear that things were much improved when using a Huawei router, rather than the TP-Link I was using (but the random stalls weren't fixed). On my todo list is to dust off my TP-Link and see if whatever they've changed has fixed it for that hardware too.

I know, but even streaming that uses multiple streams doesn’t make dozens of TCP connections in a fraction of a second like loading a complex (but typical) webpage.

I still see this issue on 4G, but not with 3G, which makes me thing they still need to make this change throughout the core. It's not a cell capacity issue either, as 4G speed tests easily achieve 50-60mbps.

3's mixed bag of vendors for the 3,4 adn 5G RAN might have something to do how long it took them to identify where this issue was.

Location: Essex.

Edited by Anonymous1337 (Tue 15-Sep-20 09:02:20)

In reply to a post by Anonymous1337:

I still see this issue on 4G, but not with 3G

That's consistent with what I was seeing, too. When the problem went away for me, it was just after the signal from my mast went up/down a lot over the weekend. And Three sent me a text to say "we're working on your local mast." That's why I assume the fix needs to be rolled out mast by mast (or perhaps by area).

"ping -f -l 1412 richi.uk" now does not cause frags. Perhaps they made some other fix?

In reply to a post by Appy:

"ping -f -l 1412 richi.uk" now does not cause frags. Perhaps they made some other fix?

Not here. Still 1400.

Did you set that on your router? Did you increase it again before you tested?

In reply to a post by Appy:

Did you set that on your router? Did you increase it again before you tested?

Thanks for asking. Yes. And reset the stack. And rebooted just in case.

Edited by richi (Wed 16-Sep-20 13:54:13)