Menu
Reply
Highlighted
  • 1.16K
  • 69
  • 185
Nex
Knows their stuff
293 Views
Message 1 of 4
Flag for a moderator

Packet loss to TBB

This is a bit of a strange issue that I'm getting on my TBB graph.

 

It started yesterday at 6am on the dot.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/e9e548f0fd9fe7b1d85953c4e1eb861df1...

Then today from 5am-12pm it was OK. And then back to packet loss.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4d45ceb25b0035b2aaa47fb9fa8925296f...

tracert 80.249.99.164

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.1
2 9 ms 9 ms 15 ms 10.229.64.1
3 17 ms 11 ms 12 ms pres-core-2b-xe-735-0.network.virginmedia.net [62.255.120.241]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * 19 ms 18 ms eislou2-ic-2-ae0-0.network.virginmedia.net [62.254.84.62]
8 18 ms 18 ms 17 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
9 18 ms 18 ms 17 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 19 ms 17 ms 17 ms pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

 

>tracert 80.249.99.164

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.1
2 11 ms 10 ms 9 ms 10.229.64.1
3 19 ms 11 ms 11 ms pres-core-2b-xe-735-0.network.virginmedia.net [62.255.120.241]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 21 ms 26 ms 17 ms eislou2-ic-2-ae0-0.network.virginmedia.net [62.254.84.62]
8 18 ms 18 ms 19 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
9 * 19 ms 20 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 * 18 ms 25 ms pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

 

I've bought a managed switch that I could put between the SH3 (which is in modem mode) and my personal router, and then port mirrored the traffic to a separate machine which had wireshark running to monitor the ICMP packets arriving/leaving. (I can provide this if you want?)

 

Out of 705 pings, only 1 packet had no response sent (the last packet), due to me stopping wireshark at the time. So, my router is responding fine, the SH3 is getting the pings TO my router

fine, the sequence numbers are incrementing normally (nothing lost on the way to me).

Expert information results: 705 ICMP: No response seen to ICMP request

 

I think there is a peering issue, or a problem at EISLOU2 - Internet core router. Also, I've rebooted both the SH3 and my own router, issue persists.

 

Anyone else having issues with their TBB graph?

 

To set the record straight, everything ELSE is fine, my download speed is acceptable (not 500 meg like it should be, but it's good enough), pings are fine elsewhere.

Pinging the bbc:

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



Random signature here... I'll get back to this some day!
0 Kudos
Reply
  • 12.63K
  • 483
  • 1.13K
legacy1
Alessandro Volta
275 Views
Message 2 of 4
Flag for a moderator

Re: Packet loss to TBB

With wireshark put in the main filter before running

host 80.249.99.164

then filter

ip.src== 80.249.99.164

in main bar > view > time display format set to

seconds since previous displayed packet

and in milliseconds

Under time you see 1.000 ~0.999 when this gap goes to 2.000 ~ 1.999 its downstream packet loss.

 

 

0 Kudos
Reply
  • 1.16K
  • 69
  • 185
Nex
Knows their stuff
249 Views
Message 3 of 4
Flag for a moderator

Re: Packet loss to TBB

Hey Legacy1,


All ICMP requests had a valid ICMP reply, and all within a milisecond.

 

So from my kit to the Hub, it's all fine. As I said in my original post, this appears to be an issue with TBB (or peering router) only. Everything else, like the bbc, gaming etc, is fine. I was merely indicating to VM that they need to check that peering router doesn't have packet loss / congestion / queue congestion (drops).

 

I already had the traffic filtered to the pingbox. Inbound, I receive every single ICMP request. It's my traffic going TO TBB that's the issue.

 

The sequence numbers I got from TBB were ALL sequential, and not a single drop. All the ICMP packets were responded to, as per the expert information.

 

Ping statistics for 80.249.99.164:
Packets: Sent = 168, Received = 157, Lost = 11 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 28ms, Average = 17ms

 

I've narrowed down the issue being egress from my hub (either dropped in the core, highly unlikely), or dropped egress at the peering between VM and LINX.



Random signature here... I'll get back to this some day!
0 Kudos
Reply
  • 1.16K
  • 69
  • 185
Nex
Knows their stuff
209 Views
Message 4 of 4
Flag for a moderator

Re: Packet loss to TBB

And then as of midnight, it's cleared up. Still think this was a link/peering issue.

 

736ffb640e59b93a26ee9f4f985ab5c1a172b5fe-28-09-2019



Random signature here... I'll get back to this some day!
0 Kudos
Reply