Dear OpenWRT community,
I am having some problems with my internet connection. It is disconnecting 2-4 times daily. Which firmware versions are known to be stable with VDSL vectoring (G.993.5 Profile 17a)
Thanks!
Not known at the moment. I have a similar link, a VDSL50 link that used to be indoor without Vectoring and with the old 51/10 sync profile, Rock solid sync stayed for months at a row. Since switching to a new linecard with Vectoring enabled and a 109/40 profile I suffer sync losses multiple times a day. I just started using the VDSL blob from the just released fritzos 7.11 for the FritzBox 7490, and since then it looks like it is down to 1 resync per day. Much better, but still far from decent.
I also tried the VDSL Blogs from older firmwaresvofvthe same fb7490 with the mentioned multiplecresyncs per day....
That's exactly what I am experiencing. When I had 50/10 it was extremely stable, nut when it changed to vectoring it went shit.
Which version are you using? (you can run "/etc/init.d/dsl_control status"). I am currently using 5.9.0.12.1.7 and I had two disconnects in 10 h. The first thing I will try is to use a better (shorter) cable.
As I said, the mode firmware blog from AVM's fritzos 7.11 for the fritzbox 7490 (which is their highest-end model using the VR9 and that still sees some active development). But unfortunatelly this is not reflected in the /etc/init.d/dsl_control status output:
root@BTHH5A:~# /etc/init.d/dsl_control status
ATU-C Vendor ID: Broadcom 192.85
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200
Firmware Version: 5.9.1.4.0.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 7117
Errored seconds (ES): Near: 159 / Far: 2371
Severely Errored Seconds (SES): Near: 47 / Far: 719
Loss of Signal Seconds (LOSS): Near: 0 / Far: 0
Unavailable Seconds (UAS): Near: 3869 / Far: 3869
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 84 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 0.14 ms [Fast] 0.0 ms [Fast]
Data Rate: Down: 103.188 Mb/s / Up: 31.996 Mb/s
Line Attenuation (LATN): Down: 11.7 dB / Up: 9.7 dB
Signal Attenuation (SATN): Down: 11.7 dB / Up: 9.5 dB
Noise Margin (SNR): Down: 15.7 dB / Up: 14.0 dB
Aggregate Transmit Power (ACTATP): Down: 0.1 dB / Up: 14.5 dB
Max. Attainable Data Rate (ATTNDR): Down: 137.674 Mb/s / Up: 41.054 Mb/s
Line Uptime Seconds: 37724
Line Uptime: 10h 28m 44s
That firmware line shows 5.9.1.4.0.7 for all the different modem blobs I tried...
I am not sure a shorter cable is going to help with this specific issue (reducing cable length and improving cable quality is a good idea independent of this issue though), as I have heard reports of users switching to broadcom based modems having their resync problems "magically" disappear.
Just in case, I am running 18.06.2:
root@nacktmulle_BTHH5A:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="18.06.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 18.06.2"
VERSION_ID="18.06.2"
HOME_URL="http://openwrt.org/"
BUG_URL="http://bugs.openwrt.org/"
SUPPORT_URL="http://forum.lede-project.org/"
BUILD_ID="r7676-cddd7b4c77"
LEDE_BOARD="lantiq/xrx200"
LEDE_ARCH="mips_24kc"
LEDE_TAINTS=""
LEDE_DEVICE_MANUFACTURER="OpenWrt"
LEDE_DEVICE_MANUFACTURER_URL="http://openwrt.org/"
LEDE_DEVICE_PRODUCT="Generic"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="OpenWrt 18.06.2 r7676-cddd7b4c77"
most isp-dsl hardware is broadcom-based so it might not be unreasonable to infer better interoperation there.
on the other hand, i have switched from a broadcom-based modem on 50/10 to a lantiq-based one on 100/40 and have not noticed any sync problems yet.
1 Like
I have 5.7.5.6.1.7, which I extracted from the ISP provided modem. My uptime is 92 days, at the moment.
Line State: UP [0x0]
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Line Uptime: 92d 4h 26m 21s
Annex: B
Profile: 17a
Data Rate: 77.848 Mb/s / 23.120 Mb/s
Max. Attainable Data Rate (ATTNDR): 109.999 Mb/s / 31.796 Mb/s
Latency: 0.13 ms / 0.0 ms
Line Attenuation (LATN): 2.1 dB / 0.9 dB
Signal Attenuation (SATN): 2.1 dB / 0.8 dB
Noise Margin (SNR): 5.0 dB / 5.0 dB
Aggregate Transmit Power(ACTATP): -11.7 dB / 12.7 dB
Forward Error Correction Seconds (FECS): 0 / 53
Errored seconds (ES): 1 / 27
Severely Errored Seconds (SES): 0 / 14
Loss of Signal Seconds (LOSS): 4 / 1
Unavailable Seconds (UAS): 461 / 461
Header Error Code Errors (HEC): 0 / 0
Non Pre-emtive CRC errors (CRC_P): 0 / 0
Pre-emtive CRC errors (CRCP_P): 0 / 0
ATU-C System Vendor ID: Broadcom 192.244
Power Management Mode: L0 - Synchronized
When I am using my Fritz!Box 3370 with the latest available original firmware, I don't have any problems. Only with my homebox.
Mijzelf Wow, would you mind sharing the firmware? I'd like to try this one!
Sure. http://www.mediafire.com/file/ldvh9hhm09umx8o/vectoring-vdsl.bin/file
BTW, the file in your Fritz!Box should also be compatible.
2 Likes
Thanks Mijzelf. ATTNDR drastically went up, I don't know if this means something, but it definitely gives me hope 
I also changed my dsl cable from a none shielded cable to a frankensteined Cat6 cable I soldered today.
ATU-C Vendor ID: Broadcom 192.85
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200
Firmware Version: 5.7.5.6.1.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 836
Errored seconds (ES): Near: 0 / Far: 23
Severely Errored Seconds (SES): Near: 0 / Far: 2
Loss of Signal Seconds (LOSS): Near: 0 / Far: 0
Unavailable Seconds (UAS): Near: 46 / Far: 46
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 0.13 ms [Fast] 0.0 ms [Fast]
Data Rate: Down: 101.528 Mb/s / Up: 39.321 Mb/s
Line Attenuation (LATN): Down: 7.9 dB / Up: 6.2 dB
Signal Attenuation (SATN): Down: 7.9 dB / Up: 6.2 dB
Noise Margin (SNR): Down: 11.0 dB / Up: 6.0 dB
Aggregate Transmit Power (ACTATP): Down: -4.5 dB / Up: 14.4 dB
Max. Attainable Data Rate (ATTNDR): Down: 125.630 Mb/s / Up: 41.937 Mb/s
Line Uptime Seconds: 20
Line Uptime: 20s
i suspect this did not change anything?
because dsl is specifically designed to work over the crappiest of all, unshielded, two-wires.
ime it maybe save a dB of attenuation if one removes any inhouse connectors (TAE) from the dsl wiring. but telco support staff will not be overly entusiastic about it 
@Mijzelf 92 days DSL uptime is impressive. Not wishing to hijack this thread, but can you tell me what version of OpenWRT is installed and did you install or update any packages?
It's too early to draw any conclusion, but I notice at least one post on the ebilan forum reporting instability issues with 18.06.2 lately for HH5a which I'm monitoring.
The other issue is that ethernet cabling does not have the ideal impedance for dsl (or rather a different impedance than the actual "TAL" CO to home line) causing some signal reflection/degradation at the joint.
First, I'm not using a HH5a, but a ZyXEL P2812-HNU-F1. It's running 18.06.1, and yes I installed some packages. Mainly Asterisk&friends.
1 Like
Thanks again, I am using this since a few months now, and things got reasonably stable.
This was an improvement, I can totally live with my uptimes now. 10d 15h 22m 33s as of now. Thanks again!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.