Now if only I could get routerstats or routerstats lite to work. I can telnet in but when I try all the TP-link models in lite I get

Wed 22 Mar 2017 19:55:41 HTTP/1.1 403 Forbidden
Wed 22 Mar 2017 19:55:41 HTTP/1.1 403 Forbidden

Routerstats full wont login at all what am I missing?

TP-Links telnet is a very cut down version.

Have a read of http://forum.kitz.co.uk/index.php/topic,17108.msg315...

use the just telnet.zip on the kitz post; it will enable a full proper telnet (on another port)

DSLstats and hg612 stats will then work with this modem/router (and I presume routerstats if you can change the telnet port)

Ian

Yes I have read that thread several times and it involves a hacked configuration file which I am not keen on. I can telnet in ok thats not the problem its collecting the data that is.

Can you hack your own config?

Just add that "telnetd" to the Device info tag.

Ian

Ok I can now telnet into the shell at port 1023 after uploading the telnetd hacked file but I am stuck on how to configure DSLStats as it just comes back timeout waiting for stats.

Think I have worked it out by re-reading the thread the command is xdslctl info --show. Getting stats now in DSLStats.

DSLStats now been collecting data for 10 hours although it was initially set to sample every 30 seconds, have changed that to 60 seconds sampling rate as it was missing the odd sample.

Amazed at the amount of configuration options DSLStats has including SNRM tweak. Someone must have put a lot of work into programming such a wonderful stats monitor.

Had a bit of a problem tonight. DSLStats started saying unable to login to modem. So I opened cmd prompt and telnet in after stopping DSLStats, the prompt response was very slow. I checked my wireless and it was at 13mbps.

So I am not sure if it was slow wireless as a local Sky Box had occupied channel 11, the router was on channel 10. So changed channel but had to reboot the router as the prompt was still slow. I added a secondary address to the LAN just in case it was because I was opening web page on the same IP.

Seems ok now but will run for a few days see if it falls over again. Not sure if it was just the wireless slow down or the router cant cope with being asked for stats so many times. Anyone else seen this?