In reply to a post by vimto_girl:

Can you post results of TBB speed test using your Mac (doesn't matter that over WiFi)? And the Terminal command "ping -s 1400 -c 100" for both 8.8.8.8 and your router? I assume you have already tried a factory reset of the HomeHub.

On PC over ethernet (for comparison)
Speedtest
http://www.thinkbroadband.com/speedtest/button/14714...

Ping to 8.8.8.8
Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 71, Lost = 29 (29% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 26ms

Ping to router 192.168.1.254
Ping statistics for 192.168.1.254:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

On Macbook over wifi
Speedtest
http://www.thinkbroadband.com/speedtest/button/14714...

Ping 8.8.8.8
--- 8.8.8.8 ping statistics ---

100 packets transmitted, 82 packets received, 18.0% packet loss

round-trip min/avg/max/stddev = 26.884/30.763/31.659/0.887 ms


Ping router 192.168.1.254
-- 192.168.1.254 ping statistics ---

100 packets transmitted, 99 packets received, 1.0% packet loss

round-trip min/avg/max/stddev = 3.091/5.742/6.607/0.567 ms

Seems to be more packet loss on PC over ethernet but to be honest I think that's just pot luck as there are times when the performance all of a sudden improves - seemingly at random.

Yes I have tried a factory reset on the router.

Using ping -l 1400 -n 100 8.8.8.8, connected wirelessly to my router which goes through an HG612.

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 39ms, Average = 25ms

pinging www.thinkbroadband.com is a good one, since we can cross check our actual network and the BQM from many providers to see if there is a provider wide issue, i.e. insight not available from picking random box on le internet

If its a dead home hub, I'd take a free replacement and then worry about the upgrading and putting the HomeHub away in a cupboard for dealing with any fault handling.

In reply to a post by legume:

Years ago when ADSL max came out my exchange developed a strange fault where line stats would show no crc errors but aal5 sar stats were showing loss, the inference being atm cells were being lost somewhere at/beyond the exchange. It soon go fixed, searching at the time came up with a description of "exchange out of sync". Though I guess this was when atm went deeper into network than now with 21cn.

Unless I'm very much mistaken, 21CN is an MPLS network, with no ATM links. DSL users can use PPPoA if they wish (arguably it's a better option on ADSL than PPPoE, especially on sub-10 Mbit/s links), but that's the only place AAL5 is used. The traffic from the MSAN onwards is MPLS.

This might be a hardware/config issue on the local BT network side. If you have BTWiFi/Fon enabled can you connect to see what results you get? Do you have a new Hub coming in the post or have they left it to the engineer to replace?

In reply to a post by David_W:

In reply to a post by legume:

Years ago when ADSL max came out my exchange developed a strange fault where line stats would show no crc errors but aal5 sar stats were showing loss, the inference being atm cells were being lost somewhere at/beyond the exchange. It soon go fixed, searching at the time came up with a description of "exchange out of sync". Though I guess this was when atm went deeper into network than now with 21cn.

Unless I'm very much mistaken, 21CN is an MPLS network, with no ATM links. DSL users can use PPPoA if they wish (arguably it's a better option on ADSL than PPPoE, especially on sub-10 Mbit/s links), but that's the only place AAL5 is used. The traffic from the MSAN onwards is MPLS.

Yea, AFAIK the only ATM is on the wire now, which is what my last sentence above was supposed to mean - though It wasn't very clear.

I think PPPoE on ADSL is really PPPoEoA so still using AAL5 but with more overhead than PPPoA, which means it's still the best option (unless you can do IPoA). I think TR069/whatever will choose it first.

IIRC from many years ago it was said that BTW only enabled PPPoE(oA) on DSL because AOL lobbied them as they had loads of kit from the US that couldn't do PPPoA. Don't know if it's true or not, but the fact AOL were "players" shows how long ago it was

In reply to a post by MrSaffron:

pinging www.thinkbroadband.com is a good one, since we can cross check our actual network and the BQM from many providers to see if there is a provider wide issue, i.e. insight not available from picking random box on le internet

ping -l 1400 -n 100 www.thinkbroadband.com

Ping statistics for 80.249.99.130:
Packets: Sent = 100, Received = 80, Lost = 20 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 26ms, Average = 25ms

In reply to a post by vimto_girl:

This might be a hardware/config issue on the local BT network side. If you have BTWiFi/Fon enabled can you connect to see what results you get? Do you have a new Hub coming in the post or have they left it to the engineer to replace?

Yes I have that enabled. Just connected to it and ran a speedtest on my Samsung Galaxy S5. Slightly improved results.
http://www.thinkbroadband.com/speedtest/button/14714...

They aren't sending me a new home hub as far as I know, I guess that depends on what the engineer finds. Last time they sent me a new HH4 straight away and that fixed it for a while.

Edited by deleted (Wed 17-Aug-16 19:49:19)

Okay now try this

ping -l 1400 -n 100 31.55.186.184

This is the IP address from the first hop on a traceroute you posted earlier I believe.

Alas due to daft home hubs we cannot do any pings or traceroutes to your home hub as a reverse trace can be useful.