Print

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

[EasyTiger]

So I just bought a TP-LINK TD-W8968 v4 (bridge mode only) and while trying to setup stat logging with DSLStats I've noticed that access to Telnet will timeout for 10 minutes after 5 logins - even though the logins were successful. Telnet will return a message of:

Authorization failed after trying 5 times!!!
Please login after 600 seconds!

Even though the last 5 logins were successful 

Is there anything I can do about this? Something tells me this is a cynical move to prevent stat logging...

Also is it possible to get Busybox enabled on this? There isn't much info on the web about how to do so...

thanks!

[Dray]

Try unticking the DSLStats option to co-exist with HG612-Modem-Stats.

[EasyTiger]

Try unticking the DSLStats option to co-exist with HG612-Modem-Stats.

Had a look and the "HG612-Modem-Stats co-operation" checkbox is already unticked

[burakkucat]

I am wondering if DSLstats actually performs a logout once the required data is harvested. If it does not, then that may account for the message so returned.

Perhaps Eric could comment on the logic used by DSLstats, please? 

[roseway]

DSLstats doesn't actually log out after collecting the data. It just drops the telnet connection.

[burakkucat]

DSLstats doesn't actually log out after collecting the data. It just drops the telnet connection.

I see. Thank you.

So perhaps the device in question retains a count of logins without a corresponding logout and once five have occurred the reported error message is displayed. 

[EasyTiger]

DSLstats doesn't actually log out after collecting the data. It just drops the telnet connection.

I see. Thank you.

So perhaps the device in question retains a count of logins without a corresponding logout and once five have occurred the reported error message is displayed. 

I just logged in directly via terminal then immediately did a 'logout',  5 times. On the sixth time after logging in I got the same authorisation failed message again . So I'm not sure if it's counting still open sessions, honestly I don't know what the hecks going on. There's an 'exitOnIdle' program accessible via telnet, I used that to change the timeout value but it won't even save once the session is over.

[burakkucat]

Just sort of thinking out loud . . .

You are able to telnet into the device under precisely controlled conditions. Are you then able to access a Busybox shell? If not, then is it worth pursuing the five logins anomaly?   

[EasyTiger]

Just sort of thinking out loud . . .

You are able to telnet into the device under precisely controlled conditions. Are you then able to access a Busybox shell? If not, then is it worth pursuing the five logins anomaly? 

No busybox shell is available unfortunately. FWIW here's the programs available in telnet:

logout
exit
quit
reboot
adsl
xdslctl
xtm
brctl
cat
loglevel
logdest
virtualserver
ddns
dnsproxy
syslog
echo
ifconfig
ping
ps
pwd
sntp
tftp
wlctl
arp
defaultgateway
dhcpserver
dns
lan
lanhosts
passwd
ppp
restoredefault
route
save
swversion
uptime
cfgupdate
swupdate
exitOnIdle
wan
mcpctl
utility

[burakkucat]

The *ctl commands look promising.

[Weaver]

Welcome to the forums, EasyTiger.