Quote:
|
Originally Posted by Seph
SEPH: I don't know how you get to the "base poing" being 10 ms. What does "base ping" mean?
|
Minimum ping. The green line on his chart. London to Birmingham should take around 6ms, then to his cable modem from Birmingham, 4-5ms.
Quote:
I traced to Namesco's BBMAX speedtest site:
Tracing route to speedtest.bbmax.co.uk [85.233.160.167] over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 18 ms 33 ms 24 ms 10.159.48.1
3 9 ms 35 ms 39 ms winn-core-1a-ae1-955.network.virginmedia.net [62.253.121.77]
4 11 ms 27 ms 24 ms winn-bb-1a-so-130-0.network.virginmedia.net [62.253.184.113]
5 18 ms 20 ms 65 ms popl-bb-1b-as5-0.network.virginmedia.net [212.43.162.194]
6 34 ms 10 ms 11 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105.159.117]
7 10 ms 18 ms 27 ms linx-gw2.plus.net [195.66.236.164]
8 43 ms 20 ms 19 ms po4.ptn-gw01.plus.net [212.159.1.138]
9 33 ms 39 ms 15 ms ptw3-gi2-3.namesco.net [212.159.1.66]
10 23 ms 16 ms 16 ms gonzales.namesco.net [85.233.160.167]
No strange routing but the lowest ping time to the destination was 16 ms. The North of the UK stuff was a comlete red herring.
|
Not sure what you mean by that. Too much jitter on your trace to get anything meaningful, and you're tracing to a different server. Looks like your hop to Winnersh core is taking ~9-10ms when it should be taking 4-5, and from Winnersh to London is 1ms which is about right. Birmingham to London should be about 5-6ms, but RB's is taking 8+ and his first hop is 7ms+ when it should be <5
Quote:
|
SEPH: Aren't we trying to explain the humps? They were even larger in earlier posts. The context in which I mentioned the Core was the humps and your response was also in that context.
|
No, I was trying to explain why his base ping was so much higher than it should be. We already know the humps are localized pockets of congestion. That's the only plausible explanation.
Quote:
|
SEPH: So we are considering the humps. Route flapping is a plausible explanation because it builds queues in various places.
|
It's not the queues that matter, it's the fact the data is taking a longer route to avoid a shorter, more congested one. But that would show up on a traceroute when done at the time of the humps.
Quote:
|
SEPH: In the generic sense, it would have to be one of the three I listed. I too didn't think LAN in the specific case. So now you think it's TBB? You didn't think so earlier. Or have I misunderstood you?
|
I think I've said at least 3 times now it's NOT TBB.