General Discussion
  >> Broadband Quality Monitor


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | (show all)   Print Thread
Standard User GrampaSimpson
(newbie) Fri 05-May-17 17:44:53
Print Post

VDSL2 link with massive packet loss


[link to this post]
 
Hi All

I'm on here from Ireland, and am a first timer here, so please excuse any unwitting netiquette bloopers.

I have a VDSL2 connection from my Technicolor MediaAccess TG588v v2 router to a local telecoms cab (approx 300 metres away). It is set at 90 down/20 up.

Since the service was installed in February, replacing an older ADSL service, it has been quite flaky in terms of responsiveness, requiring many router re- boots, DSL and PPP disconnects etc. In March, I came across the excellent thinkbroadband BQM (Thanks thinkBB, BTW) and have been monitoring my service ever since.

I'm getting massive packet loss at certain (random) times according to the BQM. I have independently verified the accuracy of the BQM charts by running pingtests directly from the router (to take any internal latency issues, such as WiFi) out of the equation.

I've had the router and its fly-lead to the wall-box replaced, and have also had a telecoms engineer out. My line has tested fine on his Megger appliance. At my request, he changed the wall- box and changed the port to which my service is connected at the cabinet. The net effect of all of this is that while all involved are being very helpful, there's been no improvement.

As the thinkbroadband website is undergoing an update, I cant link directly to my previous BQM graphs. However, here are a few to illustrate the situation:

1. A reasonably OK connection, which is fine (mostly) for TV streaming, poor on gaming and not great for Skype:

[img]http://i.imgur.com/S1Nj2mq.jpg[/img]

2. A reasonably OK connection that turned into a proper dog and required a disconnect/reconnect of the PPP connection:

[img]http://i.imgur.com/q5gksOl.jpg[/img]

3. A re- connection that started out a bit iffy, but got very bad for a while and then recovered itself a bit.

[img]http://i.imgur.com/Yhvsm9q.jpg[/img]

4. A re- connection that started out badly and got worse:

[img]http://i.imgur.com/jIlZ2Xt.jpg[/img]

In 9 out of 10 cases, a simple disconnect and re- connect of the PPP connection get things back to 'usable' albeit with issues. in the 1 out of 10 cases where its still unusable even after the PPP re- connect, a router re- boot is needed.

Sorry for the long post. I'm wondering if any of the experts on here can deduce anything from this tale of woe that might help me in my ongoing discussions with the provider.

Thanks in advance.
Administrator MrSaffron
(staff) Fri 05-May-17 17:48:39
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Packet loss like this without a corresponding rise in average latency (green/blue/yellow) areas is odd, and may just be issues with the router dropping lots of the BQM packets.

What does a sequence of out bound pings look like? Especially to the first IP hop outside of your LAN.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User GrampaSimpson
(newbie) Fri 05-May-17 18:10:12
Print Post

Re: VDSL2 link with massive packet loss


[re: MrSaffron] [link to this post]
 
Pings from inside out have been very much mirroring the BQM graphs.

For example, right this minute,
BQM is graphing in the range of 10-15% packet loss,

while immediately afterwards,

a ping test from my laptop is showing a Min/Max/Avg of 13/17/14 with 17 packets lost out of 104 packets sent (=16% loss).


Register (or login) on our website and you will not see this ad.

Standard User GrampaSimpson
(newbie) Fri 05-May-17 18:14:02
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Dump of ping from inside out:

[2017-5-5 18:07:44]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:43]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:41]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:41]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:07:35]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:07:35]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:07:29]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:29]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:07:23]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:23]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:07:18]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:07:13]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:11]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:10]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:08]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:07]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:05]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:07:05]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:06:59]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:06:58]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:56]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:06:55]Reply from I.P. of 1st Hop: bytes = 64 time = 17ms TTL = 255
[2017-5-5 18:06:53]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:52]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:50]Reply from I.P. of 1st Hop: bytes = 64 time = 13ms TTL = 255
[2017-5-5 18:06:48]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:48]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:06:43]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:06:41]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:40]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:38]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:37]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:35]Reply from I.P. of 1st Hop: bytes = 64 time = 13ms TTL = 255
[2017-5-5 18:06:35]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:06:29]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:28]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:26]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:06:25]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:23]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:23]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:06:18]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:06:12]Reply from I.P. of 1st Hop: bytes = 64 time = 16ms TTL = 255
[2017-5-5 18:06:11]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:09]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:06:08]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:06]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:05]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:03]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:02]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:06:00]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:59]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:57]Reply from I.P. of 1st Hop: bytes = 64 time = 13ms TTL = 255
[2017-5-5 18:05:56]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:54]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:53]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:51]Reply from I.P. of 1st Hop: bytes = 64 time = 16ms TTL = 255
[2017-5-5 18:05:50]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:48]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:05:47]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:45]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:05:44]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:05:42]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:42]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:05:36]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:35]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:33]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:32]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:05:30]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:28]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:28]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:05:23]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:21]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:21]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:05:15]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:14]Reply from I.P. of 1st Hop: bytes = 64 time = 16ms TTL = 255
[2017-5-5 18:05:12]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:05:11]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:09]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:08]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:06]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:05]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:03]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:05:03]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:04:58]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:04:52]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:52]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:04:47]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:45]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:44]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:42]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:41]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:39]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:38]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:36]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:35]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:33]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:33]Reply from I.P. of 1st Hop: Request timed out.
[2017-5-5 18:04:27]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:26]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:24]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:23]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:21]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:20]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:18]Reply from I.P. of 1st Hop: bytes = 64 time = 15ms TTL = 255
[2017-5-5 18:04:17]Reply from I.P. of 1st Hop: bytes = 64 time = 14ms TTL = 255
[2017-5-5 18:04:15]Reply from I.P. of 1st Hop: bytes = 64 time = 17ms TTL = 255
Administrator MrSaffron
(staff) Fri 05-May-17 18:27:58
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Very odd would expect to see some variation instead of good and then packet loss.

Error correction over the VDSL2 segment should see TCP/ICMP/UDP packets delayed even if errors on the VDSL2 part of the line. This looks more like something just not bothering to route packets randomly - broken or bad hardware.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User RobertoS
(elder) Fri 05-May-17 18:52:34
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Are you pinging from the router GUI, or from a computer connecting to the net through it?

Edit: Just read your post before the long string of pings.

What ping command are you using, as normally the first hop from a computer is the router itself? What do you get from a simple command line ping bbc.co.uk ?

My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 63086/13719Kbps @ 600m. BQMs - IPv4 & IPv6

Edited by RobertoS (Fri 05-May-17 18:56:14)

Standard User GrampaSimpson
(newbie) Fri 05-May-17 20:28:19
Print Post

Re: VDSL2 link with massive packet loss


[re: RobertoS] [link to this post]
 
I performed that ping to answer Mr Saffron's specific question in real time. And yes it was to the 1st hop outside my router as per his request, using a Ping Tool running on my laptop.

I use all the following ping tools & combinations:

- through the router's GUI itself to the next hop, to 8.8.8.8, to BBC.CO.UK etc.
- through ping tools on iPad, Android phone, laptop as well as a ping -t from the Command prompt under windows XP and Windows 10. Everything returns more or less the same result, which is mirrored very well by the BQM over time.

Right now, a ping to bbc.co.uk is returning a 40% loss on 10 packets sent., with a 24/25/24 Min/Max/Avg.
Standard User RobertoS
(elder) Fri 05-May-17 23:35:52
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Not happy!

What is this ping tool that produces that output that I have never seen before on the forums, and how do you specify what "Hop 1" is other than it being the router itself?

As I said, Hop 1 from your laptop is the router.

Given that in your list there you have done exactly what I requested, (a ping -t from the Command prompt under windows XP and Windows 10), why didn't you just repeat it and copy and paste the result.

Though thinking about it, better would be that plus (more importantly) a command prompt tracert bbc.co.uk

You came here for help, but won't do a requested test. ??

My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 63086/13719Kbps @ 600m. BQMs - IPv4 & IPv6
Standard User GrampaSimpson
(newbie) Fri 05-May-17 23:55:46
Print Post

Re: VDSL2 link with massive packet loss


[re: RobertoS] [link to this post]
 
A) I replaced the actual I.P. Address with the term "I.P. of 1st Hop" in Notepad to preserve privacy.
B) you asked that I would ping BBC. I did that and reported the result.

Frankly, your reply has confused me to say the least!
Standard User RobertoS
(elder) Sat 06-May-17 00:33:36
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Well your original posting of ping results was useless, with or without doctoring, for the reason I gave. Was the first hop 192.168.n.1 or 192.168.n.254? Where "n" is 0 or 1. Everyone else's defaults to that and few bother to change it. In particular, a ping to that is totally irrelevant to anything, except the norm is 1ms-3ms.

That's partly why I'm asking for more detail. A 14-16ms response from the router suggests an internal to your premises problem.

As I hinted in my second request, a tracert would be better than a ping.

My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 63086/13719Kbps @ 600m. BQMs - IPv4 & IPv6
Standard User GrampaSimpson
(newbie) Sat 06-May-17 00:42:08
Print Post

Re: VDSL2 link with massive packet loss


[re: RobertoS] [link to this post]
 
MrSaffron kindly responded and asked me:

What does a sequence of out bound pings look like? Especially to the first IP hop outside of your LAN.

Hence, my response together with the ping results, with the address of the 1st hop outside my LAN removed for privacy.
Standard User RobertoS
(elder) Sat 06-May-17 01:35:21
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
The first hop outside your LAN is Hop 2 of a tracert. Hop 1 is the entry/exit point of your LAN and part of it, I believe you have simply misunderstood what MrSaffron requested.

If the address you hid started with 192.168.... then it is part of your LAN. See this link. Endind with .254 instead of .1 is also very common. Ending in .0 is also frequently seen.

The router then assigns a LAN address to every piece of your kit that you connect to it to form your LAN. Think of the router being a tree with its root being the external internet and it's branches being your LAN. Because of that relationship all addresses on your LAN also start with 192.168.1 or 192.168.0.

If you took that 192.168. address to be the first hop outside your LAN, you were mistaken.

Anyway, if you still refuse to give a simple copy and paste of a tracert to bbc.co.uk with no pre-editing then nobody here can help. I won't even try any more.

My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 63086/13719Kbps @ 600m. BQMs - IPv4 & IPv6

Edited by RobertoS (Sat 06-May-17 01:36:00)

Standard User GrampaSimpson
(newbie) Sat 06-May-17 03:29:00
Print Post

Re: VDSL2 link with massive packet loss *DELETED*


[re: GrampaSimpson] [link to this post]
 
Post deleted by GrampaSimpson
Standard User GrampaSimpson
(newbie) Sat 06-May-17 06:26:13
Print Post

Re: VDSL2 link with massive packet loss


[re: RobertoS] [link to this post]
 
In reply to a post by RobertoS:
The first hop outside your LAN is Hop 2 of a tracert. Hop 1 is the entry/exit point of your LAN and part of it, I believe you have simply misunderstood what MrSaffron requested.

I believed that I had provided MrSaffron with the exact information he requested. I regret that you have misinterpreted my response to him, and have introduced tracert which was not part of his question. He asked for the ping to the 1st hop outside my LAN. That's what I posted.
In reply to a post by RobertoS:
If the address you hid started with 192.168.... then it is part of your LAN. See this link. Endind with .254 instead of .1 is also very common. Ending in .0 is also frequently seen.

The router then assigns a LAN address to every piece of your kit that you connect to it to form your LAN. Think of the router being a tree with its root being the external internet and it's branches being your LAN. Because of that relationship all addresses on your LAN also start with 192.168.1 or 192.168.0.

If you took that 192.168. address to be the first hop outside your LAN, you were mistaken.

I simply cannot understand why you are failing to accept what I have posted. At no point have I said that I took any 192.168.. address as being outside my LAN. The address outside my LAN was in the public domain- I removed it to protect my privacy. What is so difficult to understand about what I have said in that regard?

In reply to a post by RobertoS:
Anyway, if you still refuse to give a simple copy and paste of a tracert to bbc.co.uk with no pre-editing then nobody here can help.

I've not "refused" to provide any information. Regrettably I have been trying to address your misunderstandings/misinterpretations of what I have written, and of MrSaffron's request for information, and have therefore not been able to move on to perform such a tracert, as your responses are confusing me at best, and appeared quite combative at worst. As to your assertion that "then nobody here can help", I trust/hope that you are not speaking for every thinkbroadband subscriber and member of this forum, and that your approach is not reflective of a resource that I had found very useful and which I assumed welcomed legitimate questions around what could be gleaned from the Broadband Quality Monitor. If, in fact, you are the "Supreme Leader" here, then I have clearly misunderstood the forum/site's level of helpfulness amd regret having bothered to present my enquiry in the first place.
In reply to a post by RobertoS:
I won't even try any more.

That would probably be best. Thank you.
Standard User GrampaSimpson
(newbie) Sat 06-May-17 12:06:51
Print Post

Re: VDSL2 link with massive packet loss


[re: MrSaffron] [link to this post]
 
Yeah, there's definitely something strange going on. If it was just some equipment throwing away ping packets that wouldn't be too bad, but the internet service is simply unusable much of the time. Already this morning, I've had to do 3 reconnects, streaming TV is buffering constantly and that's on an alleged 90/20 connection!

As to the physical wires etc., it's all been checked out and I'm told its all fine. The router's been changed out with a new replacement put in its place. The port in the cabinet to which I'm connected has been changed. All to no avail. I had hoped that there was some 'hidden' picture in the BQM graphs that someone might have been able to elicit. Alas, it seems not.

Ill leave it at that. Thanks for your efforts.
Administrator MrSaffron
(staff) Sat 06-May-17 12:10:53
Print Post

Re: VDSL2 link with massive packet loss


[re: GrampaSimpson] [link to this post]
 
Sorry for the lengthy cycle you got stuck in...

To illustrate precisely what I meant and what I believe you actually did...

C:\Windows\system32>tracert www.thinkbroadband.com

Tracing route to www.thinkbroadband.com
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  my-router [192.168.0.1]
  2    20 ms    20 ms    23 ms  telehouse-gw5-lo1.idnet.net [212.69.63.39] - first hop beyond the LAN
  3    20 ms    20 ms    20 ms  telehouse-gw8-v525.idnet.net [212.69.63.88]


I said 'first hop beyond LAN' because some people may have two or more LAN hops e.g. double NAT scenarios and the 14ms latency seen suggested to me that poster was pinging something outside their local LAN.

As for while its going from 14ms to packet loss with no delayed packets, cannot say for sure, if this was a UK user I'd say borrow someone elses hardware and test it, or if router has Ethernet WAN try a different VDSL2 modem. My feeling is that we may be seeing a router that is behaving oddly, could be the router in the home, or some other device since at the IP layer we don't see everything. If it was errors on the VDSL2 line, then one of the error correction methods should mean the odd packet gets corrected and arrives a little delayed, which is not happening.

One possibility is that an ISP has some congestion management that is VERY BAD, and rather than queuing and thus given varying performance before things timeout is actively rejecting some packets at peak time.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User GrampaSimpson
(newbie) Sat 06-May-17 12:33:38
Print Post

Re: VDSL2 link with massive packet loss


[re: MrSaffron] [link to this post]
 
Thanks for that very helpful reply.

Yeah, I got that abt. the 1st hop, and that's what I posted.

On your suggestion re. borrowing other gear, I do have a neighbour who is also on a VDSL2 service, albeit with a different provider. I may have a think about borrowing his gear one of the days he's at work next week. I handle his internal IT stuff for him anyway so it might just be 'payback time'. However, I'll need to ensure that its not locked down to his supplier like some of the router/modem equipment often is over here.

Unfortunately, your last para. is a distinct possibility but if that is the case, getting to the bottom of it will not be easy!
Pages in this thread: 1 | 2 | (show all)   Print Thread

Jump to