When i was on 19.07.x
In status > overview there was informations about my line (download/up errors, my line attenuation, noise margin etc.).
Now im on 21.02.x but in Status > overview i cant see anything..
Maybe removed to another section? maybe do i need to download any package?
How to find that again?
lol.. i clean everything all time..
also tried to log in from another browser.
what device are you using?
I quickly installed 21.02.1, 21.02.3 and 22.03.0-rc3 onto spare HH5a and I can see DSL stats. Factory Reset.
Has DSL_Control been disabled (LuCI > System > Startup), as that will remove the DSL stats from LuCI in 22.03.0-rc3 and probably 21.02.x?
Its enable but it wont show anything...
I dont want to factory reset i have many settings and if i take a backup and then i restore it then it will be the same as now.
fwiw, perhaps perform a selective restore if no one can come up with any suggestions?
If you are a Windows user, use WinSCP and restore or copy/paste contents of individual configuration files. Here are some key files to get up and running:
/etc/config/network
/etc/config/firewall
/etc/config/dhcp
/etc/config/wireless
Perhaps it is the 19.07 /etc/config/luci file that is causing problems in 21.02?
As far as I can recall, there was a LuCI bug in 21.02.0, but I don't think this is your issue. See section 7.40 of installation guide.
https://openwrt.ebilan.co.uk/viewtopic.php?t=266
...no 
I will factory reset to to see if that will fix the problem and i will setup EVERYTHING from start
I reset and setup everything again...
I can't see my DSL Stats on 21.02.3 (DGN3500)
Is there any package or any other way to fix that???
Just to ask, you do get DSL sync and internet access, but the LuCI GUI does not show the DSL stats?
What is the output of ubus call dsl metrics on the command line?
I have DSL sync and internet access fine. luci gui wont show me DSL stats.
ubus call dsl metrics????? whats that? what command line?
Im only using luci gui.
Yes, that is a command you should issue in a terminal after first using ssh to log into the router, here are instructions:
https://openwrt.org/docs/guide-quick-start/sshadministration
Ah, your choice, but it would be interesting to learn whether you get more information on the command line.
ok i login via powershell and cmd, ubus call dsl metrics return stats but the stracture is vertical and its not clear to see/read.
Great! So there is something.
Yes, that is IIRC JSON formatted output intended to be consumed by software, but it also is human readable. Could I convince you to copy and past the content here into the forum, please?
Just make sure you "sandwich" the copied text between two rows of backtick characters ` (which will be invisible) looking something like this in the editor:
```
Your Pasted Text as preformatted text with fixed width font
1
1111 (note with fixed-width fonts the numbers are right-aligned)
```
and like this in the forum:
Your Pasted Text as preformatted text with fixed width font
1
1111 (note with fixed-width fonts the numbers are right-aligned)
As a quick fix, I would probably go and build the following go-dsl utility so you can check the DSL statistics from a remote computer in a reasonably readable way, while figuring out what hapened to the DSL section in the overview LuCI-page.
{
"api_version": "3.24.4.4",
"firmware_version": "4.4.4.0.0.1",
"chipset": "Ifx-AR9",
"driver_version": "5.0.0",
"state": "Showtime with TC-Layer sync",
"state_num": 7,
"up": true,
"uptime": 69987,
"atu_c": {
"vendor_id": [
181,
0,
73,
70,
84,
78,
113,
197
],
"vendor": "Infineon 113.197",
"system_vendor_id": [
0,
0,
0,
0,
0,
0,
0,
0
],
"version": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"serial": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
]
},
"power_state": "L0 - Synchronized",
"power_state_num": 0,
"xtse": [
0,
0,
0,
0,
0,
1,
0,
0
],
"annex": "A",
"standard": "G.992.5",
"mode": "G.992.5 (ADSL2+)",
"upstream": {
"trellis": true,
"bitswap": false,
"retx": false,
"virtual_noise": false,
"interleave_delay": 250,
"data_rate": 1007500,
"latn": 9.100000,
"satn": 9.300000,
"snr": 8.800000,
"actps": -38.900000,
"actatp": 11.500000,
"attndr": 1080000
},
"downstream": {
"trellis": true,
"bitswap": false,
"retx": false,
"virtual_noise": false,
"interleave_delay": 250,
"data_rate": 17001746,
"latn": 16.900000,
"satn": 14.800000,
"snr": 6.000000,
"actps": -40.900000,
"actatp": 19.900000,
"attndr": 17012000
},
"errors": {
"near": {
"es": 281,
"ses": 1,
"loss": 0,
"uas": 22,
"lofs": 0,
"hec": 1017,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
},
"far": {
"es": 1,
"ses": 0,
"loss": 6,
"uas": 22,
"lofs": 0,
"hec": 0,
"ibe": 48,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
}
}
}
see?.. That's what I'm talking about.. i have to do a ton of thing just to see my dsl stats instead of open luci gui and show me nice and clear instantly.
That's why i want to "fix" the problem im my luci gui page.
@moeller0 - Hm, LuCI checks the presence of /sbin/vdsl_cpe_control to see if DSL support is present on the system. Are there DSL supporting targets shipping without this executable?
Edit: ah, apparently the ADSL units use /sbin/dsl_cpe_control instead (without v).
@seth - it is a bug in LuCI. As workaround you can run the following command once in your SSH terminal, followed by a reboot of the device:
sed -i -e 's#vdsl#dsl#' /usr/libexec/rpcd/luci
The fix will stick until you reset your device. I'll fix the bug in the repository now so that DSL stats work as expected with the next OpenWrt release.
Yes, those like the OPs that only use the https://github.com/etactica/openwrt-trunk/blob/master/package/platform/lantiq/ltq-adsl-app/Makefile
Skip that you found this yourself already...
I run via ssh
sed -i -e 's#vdsl#dsl#' /usr/libexec/rpcd/luci
and then reboot but when i log in to device in luci gui im still unable to see my dsl stats.
Strange.
What is reported by the following commands?
ls -l /sbin/dsl_cpe_control
and
ubus call luci getFeatures
-rwxr-xr-x 1 root root 140997 Apr 16 12:59 /sbin/dsl_cpe_control
{
"opkg": true,
"ipset": [
],
"wpasupplicant": {
"suiteb192": false,
"11r": true,
"owe": true,
"acs": true,
"eap": false,
"11n": false,
"wep": false,
"sae": true,
"wps": false,
"11ac": true
},
"odhcpd": true,
"cabundle": true,
"offloading": true,
"dropbear": true,
"dnsmasq": {
"gnu-getopt": true,
"tftp": true,
"dnssec": false,
"conntrack": false,
"dbus": false,
"ipset": false,
"cryptohash": false,
"ipv6": true,
"lua": false,
"inotify": true,
"dhcp": true,
"loop-detect": true,
"dumpfile": true,
"ubus": true,
"id": false,
"i18n": false,
"idn": false,
"dhcpv6": false,
"auth": false
},
"ipv6": true,
"firewall": true,
"hostapd": {
"suiteb192": false,
"11r": true,
"owe": true,
"acs": true,
"eap": false,
"11n": false,
"wep": false,
"sae": true,
"wps": false,
"11ac": true
},
"br2684ctl": true,
"sysntpd": true,
"swconfig": true,
"dsl": true
}type or paste code here
Hm, that looks fine ("dsl": true) - that should cause the DSL status section to be displayed on the main status screen...
If you logged into LuCI, see the main status page, press F12, open the Console tab and enter L.hasSystemFeature('dsl') - does it report true or false?