VDSL - weird packet loss issue

For the last 6 months or so, I've had a rock solid DSL connection, but the IPv4 and IPv6 connections have periodically dropped out

Zen have been unable to find anything wrong (I believe it's inside BTOR)

I was reminded that I'd setup BQM graphs and was somewhat surprised to see very high packet loss reports - and that they're following a sawtooth pattern repeating at about 6 hours. This pattern is almost unvarying for at least 6 months (That's as far back as I looked, could be more)

My Broadband Ping

5% packet loss is enough to cause issues, 20% is _extremely_ serious levels of packet loss and at 30% it's no real surprise that the PPP connection is failing occasionally

The link itself has been very lightly occupied for most of this time and the sawtooth doesn't reset when the router's rebooted (or when DSL resets or IP connectivity resets) - I'm pretty sure this is a BTOR issue but it'd be interesting to see if anyone else is suffering similar issues - particularly if you're in Surrey

==

Your using the frizbox, it has weird and wonderful ways of responding to ICMP

Ha! I too am seeing this. Zen FTTC, 54 from our Draytek router, rock solid for years and about 2 months ago, similar traces to you. I've tried a difernet Drayetk & also the Zen supplied Frits (horrid thing!) and all are prettty rubbish.

Zen have been v helpful and even OR who turned up were useful too. But despite best endeavours, no fix and the support case is still open.

Ongoing....

Yes, a 7590 and various versions of the firmware, however the sawtooth packet loss pattern is there during a period when I had a draytek plugged in as well as a Zen 7530 loaner

If it was the Fritzbox, then the sawtooth pattern would most likely reset on reboot and that's not happening. The other issue is those wild ping latency swings at times when the connection is quiet

That's why I suspect the issue isn't CPE and much more likely to be inside Openreach. I'm on an ancient ECI cabinet and given the issues they're known to have I suspect the issue is the local exhange's node controller, but BTOR simply won't talk to anyone about their issues

Matters aren't helped by wet cables, but my VDSL has been fairly solid for several months, vs previous link instability

I'm aware of Fritz ICMP flood control, but it seems to have been somewhat fixed in more recent versions

Have you seen the entry regarding sawtooth patterns on this website ?

Why does my graph have a sawtooth effect?

One unusual but common effect is shown in the sample graph below. The repeated rising edge with a sharp drop off gives rise to the waveform name of sawtooth.

BQM sawtooth pattern showing jitter affecting max latency caused by some routers

A graph of this sort appears to be common with users of the Sky LLU broadband service. It does not appear to represent an actual problem with the service, or affect any applications running across the connection. This is just one of those odd situations that a particularly router appears to cause.

Not the same sawtooth. In the OP's case, the sawtooth is of increasing packet loss over a 6 hour period that suddenly reduces and climbs again.

The FAQ example is a sawtooth pattern in the latency over a much, much shorter time period.

Definitely not the same thing.

Graph

So this is with a Fritz on a Zen FTTC line. Terrible performance, esp. with VOIP... not happy.

Edited by davidmatthewson (Fri 24-Jan-25 13:47:21)

This is... interesting... Zen have been telling me there are no similar cases

What part of the UK are you in (SE here, LSLEA) and what kind of cabinet are you connected to? (Huawei or ECI?)

If there are more people with similar issues it adds to the corpus that there's a very real issue they need to deal with properly, instead of just brushing people off

We are in SE UK - East Sussex - The Cab is ~50m from the router and identies as 'Broadcom' but maybe that's in the Exchnage rather than cab?

So, potentially a regional issue

The identfied chipset is what's in the DSLAM, not the controller (exchange)

Broadcom modems are Huawei cabinets. ECI uses Infineon - that rules out exchange node manager issues as they're different for each maker and pushes the issue further upstream

==