Print

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

[Weaver]

See also https://forum.kitz.co.uk/index.php/topic,21273.msg452852.html#msg452852 - build request.

[Weaver]

[johnson]

Thank you for the data!

As far as I can tell the issue lies with xdslctls output. I was sure it must be something like an issue with parsing data under certain conditions resulting in subtracting a running total from zero (maybe when the length of the stats file output changes during resync), but from the data supplied it seem the total counters actually did reset to zero themselves. Summing the columns in the logfile I reach nearly (not sure why not exactly) the totals in the stats file listing here:

Total time = 2 days 1 hours 8 min 59 sec
FEC:      131978      5693
CRC:      57628      27
ES:      4249      10
SES:      1260      0
UAS:      13784      12700
LOS:      128      0
LOF:      287      0
LOM:      7      0

So including the spurious negative values we reach the same total, which means the modems totals must have reset to zero, something that normally never happens without a reboot, or issuing the command 'xdslctl stop'.

If we graph the sum of downstream FEC it makes the reset clear:


So the easiest fix would just be resetining to zero on a negative value for the FEC and CRC graphs.

[Weaver]

Thank you for that and for your research work!

On a different matter, a general question: using the http port 8000 API, is there a way to get hold of some values such as the attenuation, the link-uptime and o/s-uptime/time since boot? (One of these latter values might be available at the end of one of the long, long data listings though.)

[johnson]

Thank you for that and for your research work!

On a different matter, a general question: using the http port 8000 API, is there a way to get hold of some values such as the attenuation, the link-uptime and o/s-uptime/time since boot? (One of these latter values might be available at the end of one of the long, long data listings though.)

Attenuation and link uptime as displayed in the status page would need you to parse them out of :8000/data/stats just like the javascript in the page does, and unfortunately neither are stored in the log file if you mean finding historical values - i.e what was the attenuation before this resync - but could be added.

No way to get uptime with the modem as it is.

I've been playing with the httpd server included with busybox in the stock firmware (rather than the zyxel httpd that runs the normal web UI), its remarkably easy to get old school cgi scripts working for what ever you might want. If you were feeling adventurous you could try something like:

Code: [Select]

~ # cd /data
/data # mkdir -p www/cgi-bin
/data # busybox httpd -h /data/www/ -p 8001
/data # echo "#!/bin/sh" > www/cgi-bin/uptime
/data # echo "echo" >> www/cgi-bin/uptime
/data # echo "uptime" >> www/cgi-bin/uptime
/data # chmod +x www/cgi-bin/uptime

Visiting modemip:8001/cgi-bin/uptime you would be greeted by:
 08:54:26 up 40 min, load average: 1.03, 1.05, 1.00

The other values you mentioned could be awked out in similar scripts residing in /data/www/cgi-bin. Starting of this server could be added without issue to your processing of /data/boot-cmds.sh.

Edit:
I haven't forgotten about the ssh server btw, these additional values could be added to the normal stats server then. 

[johnson]

If you are bored and feel like testing:
https://www.dropbox.com/s/tdvgv6a9sb1anzr/1312-ssh-test.bin

No fix for the negative error graphs, but it does have:

• dropbear SSH server on port 2222
• sftp-server - scp/sftp browsing/mount sshfs
• nano - ease of editing for those who are vim challenged 

[Weaver]

[johnson]

[burakkucat]

[Weaver]