They likely avoid it to prevent unnecessary interruptions and ensure stability during critical operations.
They likely avoid it to prevent unnecessary interruptions and ensure stability during critical operations.
I’d appreciate knowing if you have a wireless router or access point, or if you use it for tasks like downloading torrents to an external USB drive. It’s possible the device is consuming more memory or slowing down over time, and you might want to restart it periodically. Programmable outlets are available starting around $10–15, and you could set them to turn off at a specific hour each week.
Due to the protocol's limitations and its tendency to operate near the edge, adjustments have been made to ensure continued operation even when issues arise—reducing the chance of losing a connection. It works well during short-term disruptions. In the UK, interleaving isn't always standard; each line begins with it and is reviewed for a few weeks before removal if error rates are deemed acceptable. This tighter control allows more efficient management of bandwidth throughout the network. Preventing excessive traffic from local devices helps minimize packet loss and buffer growth on the network.
Everything is managed through protocol. Quality checks happen during the ascent; when issues arise, connections are cut to maintain stability and prevent errors until repairs are complete. Adding SRA helps restore channels without full retrains, even opening more after training. All standard procedures apply. Speed throttling only masks temporary interference. You need a reliable line, which means a clean setup is essential. On the ISP side, I’m aware how challenging repairs can be at times. I’m not sure what you’re aiming for. Please clarify before starting installation.
This perspective comes from hands-on experience in everyday network operations. The protocol alone couldn't meet the demands of real-world conditions. SRA on most routers falls short and isn’t compatible with the network, often worsening issues instead of fixing them. When a line experiences intermittent problems, do you prefer it to keep fluctuating or stall at a slower pace until someone fixes it? It’s far more practical to have automated systems that set optimal configurations for stability, rather than guessing and dealing with repeated complaints about ongoing failures.
It’s not just about occasional glitches; many customers are unknowingly stuck in lower-speed bands, like the 500Kbit offered when they first got ADSL. Over time, options improved—1Mbit followed, then 2Mbit—but sometimes changes were made without proper testing. This shows how unreliable relying solely on pre-installation data can be.
Once networks unlocked full capabilities, I still saw speeds like 5.5Mbit with decent signal quality. Even with limitations, DLM technology helped maintain performance better than older DSL standards. Some equipment, such as outdated ECI DSLAMs, struggles with even basic requirements like 3dB SNRm.
There are networks that have adopted SRA solutions, which work well for them, but many still stick to restrictive profiles instead of optimizing for each customer’s actual capacity. Openreach appears to have found a reasonable balance given their available hardware.
It's a modem protocol, it's quite reliable and straightforward. What do you mean it isn't working on the network? The modem and the blade must be compatible with it, that's all. So let me clarify: you seem to be experiencing slowdowns during interference and not recovering when the signal is clear? That makes sense. The reconnection process is essentially the restoration of your connection until a technician arrives.
DSL is vulnerable to interference from almost anything. It operates within the 5-900 (AM) radio band, making it susceptible to most forms of wide-area communication. Plus, its poor insulation is easily damaged by nearby electrical surges.
About the issues: 90% of problems stem from faulty connections, corroded copper at the block, and the impact of nearby lightning causing heating and brittleness. I’m not sure where you’re getting this information from—it seems mostly based on personal stories. As an ISP engineer with around 9k DSL lines, I can confirm it’s usually a physical problem. Special cases involving interference are rare. The situation isn’t about lack of planning; better protocols, channel recovery, and upgraded hardware are the real solutions. You’re questioning whether a 3dB SNR is acceptable? That’s below the standard industry level of 6dB. Understanding SNR and how ATM functions on DSL is crucial. If you’re unsure about these concepts, it might help to review them.
I’ve worked briefly in an ISP and been part of UK broadband discussions since ADSL became available. I’ve observed how the technology has changed over time. Openreach’s approach with DLM seemed like a way to address stability concerns, especially with the equipment they selected. My network is quite varied—ADSL uses LLU where ISPs operate their own DSLAMs. Most people didn’t use SRA, likely because end-user gear wasn’t reliable enough. In theory, it should have improved things, but in practice it didn’t.
This might be partly due to the trend of requiring customers to supply their own equipment rather than having ISPs provide it. That changed after VDSL became available; now most ISPs do offer equipment, though they still lease it from the telecom provider. With inconsistent interference, locking connections to a “worst-case average” seems safer than constantly resyncing due to line fluctuations. This decision is based on years of real-world performance data from Openreach.
It’s unlikely they built this complex DLM system by chance—it would have been extremely costly. If simply enabling SRA had been enough, they’d probably done that. In an ideal scenario, all network issues would be resolved quickly, but that’s not the case here. Our network is aging copper with a mix of modems and routers, possibly including some subpar DSLAMs or line cards, leading to this “solution.”
Regarding the 3dB SNR, I was highlighting how static profiles limited my line performance. I was lucky to have a stable 2+KM connection, especially since it was on aluminum. The system could do more than they assumed. They now aim for 3dB on good VDSL lines, but only on Huawei equipment because other vendors couldn’t reliably support it. This is managed through DLM, which adjusts profiles based on error monitoring and line conditions.
A strong line receives 3dB, a decent one 6dB, FastPath gets higher, and average lines get 6dB Interleaving—more interleaving as noise increases. Poor connections are limited to lower targets, which is a compromise to keep the line usable until repairs can be made. This approach reflects Openreach’s experience over time, not an ideal design.
We’re dealing with a nationwide network, not just a small area. The problems they faced were different from what I’ve seen.
You're referring to a broader network context across the UK, not your specific setup. I'm not sure what role you played—installer, NOC, engineer—or how many cases you reviewed. I won't debate with anyone who has limited information. DSLreports is best for diving into DSL topics; it doesn’t constantly refresh. After a channel shutdown, they listen and negotiate. No training required, but it’s effective. It doesn’t fix everything quickly. I understand the effort needed for repairs, costs involved, and time spent on other tasks. The solution often lies in fiber. Engineers identify issues, not just apply fixes to copper. Most problems stem from physical factors, even if you think interference or faulty hardware is the cause.
Openreach controls most of the UK’s telephone network. This covers the bulk of the DSL connections, which ISPs lease from the DSLAM port through Openreach backhaul to their PoP. ADSL functions are similar, though some larger providers operate their own DSLAM at the exchange. For reasons unclear, they’re still only testing SRA with a limited customer base. As I mentioned earlier, they reportedly faced significant compatibility problems with it on ADSL2+, so they never adopted it. They appear to have finally started focusing on FTTP, but such changes take time. The issue is especially pronounced in rural areas where laying fiber costs far exceed expected returns. There are instances where a single line fault causes constant re-syncing. While occasional severe cases exist, capping the line won’t fix everything. I suspect some specific frequency bands are affected, so narrowing the band can help stabilize the connection. I’ve gathered numerous testimonials over the years about network performance. I won’t deny that poor equipment choices might contribute, but SRA was intended to resolve this problem. For whatever reason it didn’t work on their network, they didn’t roll it out. I often wondered why an ISP with its own DSLAM at the exchange wouldn’t enable SRA for ADSL2+—I’m not sure where I heard it, but I recall reading that it simply didn’t function well.