Print

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

[Bestgear]

Hi

I run two 612's with DSLstats and one instance has started "second stage login failure".

I can telnet into the box fine, but when you issue the "sh" - there is a longer delay on the "failed" box than the other one. Once the "sh" delay has passed, the response is as expected, as is the modem throughput.

These 612's have been running for years so one may be at fault?

I dont want to reboot the slow 612 for obvious reasons unless I *really* have to.

Is there a setting somewhere I can tweek to increase the timeout before the login error is triggered?


Thanks, as ever.

David

[roseway]

There's nothing you can do as a user to increase the timeout. In principle I could increase the timeout, but I'm not going to be able to do that quickly. It seems to me that your slow HG612 really does need a reboot, because this sort of symptom is typical of a device running out of free memory (or it could be a hardware fault of course).

[Bestgear]

Hi Eric

I was hoping it would be a setting somewhere that was reachable to me.

Given that I have read elsewhere of people with the same (or perhaps similar) to me, is there any mileage in bringing this setting into the GUI? (please!?).

I will have a search to see how to see the HG's memory usage - the other operations (web interface and WAN performance) dont appear to be affected at all... thus far.

David

[roseway]

It's certainly possible, but at the moment DSLstats development is on hold because of a problem which limits my time on the computer. Hopefully I'll be able to resume development fairly soon.

[Bestgear]

It's certainly possible, but at the moment DSLstats development is on hold because of a problem which limits my time on the computer. Hopefully I'll be able to resume development fairly soon.

Thanks Eric - it would be very much appreciated if you could find the time at some point.

Thanks - as ever!

[johnson]

I mean unless you have had several disconnects already today I would just restart the modem to rule it out no?

[Bestgear]

I mean unless you have had several disconnects already today I would just restart the modem to rule it out no?

Like many, I would really want to avoid rebooting the modem.... I have had a world of pain with my speed, and now that it is up at 70ish,  I dont want to do anything to return me to the days of 40mb.... which it ended up being...

Even during that time, I was never rebooting the modem...


David

[j0hn]

Providing your modem is at or near its target SNRM and it hasn't drastically dropped since the last sync (usually due to crosstalk) then a single reboot of the modem will have absolutely no negative effect on your line.

Like many, I would really want to avoid rebooting the modem....

Most don't want to reboot their modems multiple times. I don't believe "many" care about a single reboot, especially when features are hanging.

Given that I have read elsewhere of people with the same (or perhaps similar) to me, is there any mileage in bringing this setting into the GUI? (please!?).

Not an issue I've come across.

Rather than asking Eric to spend considerable time implementing a feature that may not even be needed could you post if rebooting the modem does fix it (when you eventually do).