Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DaveG6HNI]

I can't see a difference as of yet, but there were very few losses today anyhow, best I monitor it for a day or two...
https://www.thinkbroadband.com/broadband/monitoring/quality/share/a9f8c2d515d025d3353be201a6d6b1313ba8132d-09-11-2022

I found this on AVM site which confirms I should disable Stealth Mode
--------------------------
If the FRITZ!Box should reject unsolicited requests from the internet instead of replying with ICMP control messages, enable the option "Firewall in stealth mode" under "Internet > Filters > Lists > Global Filter Settings" in the FRITZ!Box user interface.
--------------------------

So what about the other currently enabled filters, NetBIOS packets, Teredo packets and WPAD packets ?

[Chrysalis]

You can leave those alone unless you actually need Teredo (xbox use).

Firewall should be by default in deny all mode on the WAN anyway except ICMP (with holes pocked through for NAT port forwarding), so these are only extra filters on top of those rules.

[DaveG6HNI]

You can leave those alone unless you actually need Teredo (xbox use).

Firewall should be by default in deny all mode on the WAN anyway except ICMP (with holes pocked through for NAT port forwarding), so these are only extra filters on top of those rules.

OK thanks, I can still see the odd little red spike on TBB graph, but Fritz box stats look fine at present, so let's hope they stay that way, then I can ask PN to reset DLM/DSLAM back to max (40Mbps)

I will dig out my BT modem in the meantime just in case...

[Chrysalis]

Ok, this problem wont have caused you to get DLM affecting your line, the suggestion was just to make sure TBB was more accurate in giving an idea of packet loss levels.

[DaveG6HNI]

Interestingly DLM/MAX DSLAM has recovered slightly this AM, back to 35Mbps so now I'm thinking that disabling Stealth Mode may have affected DLM somehow ? as I have never seen it recover, it has always just dropped ?
TBB graph remains pretty good and Fritzbox reports no uncorrected DTU and just a few corrected DTU (21 per min) not sure how good or bad that is ?

[tubaman]

Interestingly DLM/MAX DSLAM has recovered slightly this AM, back to 35Mbps so now I'm thinking that disabling Stealth Mode may have affected DLM somehow ? ...

It can't possibly make any difference as Stealth Mode is a firewall function (ie TCP level) that DLM neither knows nor cares about.

[j0hn]

Interestingly DLM/MAX DSLAM has recovered slightly this AM, back to 35Mbps so now I'm thinking that disabling Stealth Mode may have affected DLM somehow ? as I have never seen it recover, it has always just dropped ?

The DLM only monitors the xDSL link. It can't see anything internet related like tcp/udp/pings etc.

It's the Error seconds (ES) that shot up that caused the DLM to lower the banding level used, reported as MAX DSLAM on the Fritzbox.
The DLM increasing this limit would be because it has seen the line performing better, which will be in the form of low Error Seconds, or something similar.

What you do with your internet connection doesn't effect the xDSL circuit. The xDSL is just the link between you and the cabinet and your data runs transparently over this.
You get the same ES not using your connection as you do downloading/uploading at full rate.

Your issue is the DLM is seeing ES which can only be down to the modem, the DSLAM or the copper pair running between the 2.
ES can be caused by all manner of things from failing modems, bad joints in the copper, a dodgy DSLAM port or electrical interference from faulty equipment in your home or anywhere in close proximity to your line between you and the cabinet.
Water pumps/sewage pumps/high wattage machinery/even faulty electric fences anywhere between you and the cabinet can cause ES on a line.

The only thing you are in control of that can improve things is your modem and your internal wiring (extension wiring) at the master socket.
That's why trying another modem was suggested.
If your Fritzbox was failing/developing a fault then substituting it for the other Fritzbox would help.

I'd recommend unlocking your HG612 and running dslstats as it gives excellent graphs of everything xdsl related.
The HG612 also has a different vendor chipset in it which might play nicer with your DSLAM.
Your DSLAM is a Huawei made DSLAM with a Broadcom chipset inside. The HG612 also has a Broadcom chipset.

Dslstats can run on Windows, Linux or a raspberry pi.

This would likely be tricky for Openreach to identify due to the intermittent nature of it.
Ideally you catch this during the burst of errors and if it's caused by electrical interference, tracking down the source.

I mentioned further up the thread that kitz had something somewhat similar. ES would start out of nowhere, cause unknown, and would continue until the DLM resynced her line.
However a simple resync by kitz stopped the ES immediately, until the next episode days or weeks later.
Try resyncing your modem if you catch the error bursts happening to see if they stop.
Dslstats has the ability to alert you via email when an ES burst happens.

[Black Sheep]

This would likely be tricky for Openreach to identify due to the intermittent nature of it.
Ideally you catch this during the burst of errors and if it's caused by electrical interference, tracking down the source.

OR's NATO diagnostic tool, is fantastic for scrutinising this kind of potential interference fault.

One can filter down to the serving DP and compare all circuits against each other, to drill down to how many circuits are experiencing the same issue, with the same timings.

Thing is, there's a lot more protocols to satisfy before it gets to that stage, as you say, the internal wiring/router/copper pair could well be knackered.

[DaveG6HNI]

So what constitutes good or bad error seconds ?
Looking at my router it says I have had 42 seconds with errors since it resynced 18 hours ago ?

With ref to other recent suggestions, I have no internal wiring, the Master Skt and feed back to the telephone pole were replaced about a year ago, I have been "Lifted & Shifted" to a new port several times each new port being worse than the last. I am on my 2nd Fritzbox 7590 which is on a filtered UPS and most times the interference/Errors occurs at night when nothing of mine is switched on other than my Fridge/Freezer which I can't easily switch off.

I have found my BT HG612 so will look at your suggestions involving trying that and report back.

[Chrysalis]

I agree with the modem swap to help you figure out whats going on.

42 errored seconds in 18 hours is pretty good.

[Black Sheep]

42 ES in 18hrs is pretty much a perfect circuit.

[RealAleMadrid]

Mine's a bit better than that

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status:   0
Max:    Upstream rate = 32383 Kbps, Downstream rate = 80680 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        2.0             9.1
Attn(dB):        15.6            0.0
Pwr(dBm):        13.0            6.6

Since Link time = 29 days 12 hours 51 min 35 sec
FEC:            73674111                0
CRC:            0               1781
ES:             0               1477
SES:            0               5
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

Don't get any ES here! The short link time is only caused by power outages.

[adslmax]

here is mine

xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 27306 Kbps, Downstream rate = 86871 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        6.9             10.5
Attn(dB):        12.2            0.0
Pwr(dBm):        12.5           -0.2

Total time = 111 days 3 hours 33 min 18 sec
FEC:            14844           0
CRC:            0               5494
ES:             0               4754
SES:            0               1
UAS:            43              43
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
HostInitRetr:   0
FastRetr:       0
FailedRetr:     0
FailedFastRetr: 0

Since Link time = 111 days 3 hours 33 min 18 sec
FEC:            14844           0
CRC:            0               5494
ES:             0               4754
SES:            0               1
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
HostInitRetr:   0
FastRetr:       0
FailedRetr:     0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>

[tubaman]

Mine's a bit better than that

...

Is the cabinet in your sitting room?   

[RealAleMadrid]

@tubaman  No, it is approx 450 to 500 metres away, I only get full 80 Mbps sync after a power cut when my HG612 syncs up quicker than other modems on the cabinet, that's why the SNRM is low but it doesn't seem to cause any problem with errors.