They don't.
These do:
- Errored Seconds
- Severely Errored Seconds
- Re-synchronisations
- SNRM delta
Does dslstats show those above ones?
Thanks for the information.
Excuse my ignorance but why is everyone concerned with CRC errors if they count towards nothing?
On the ASUS, sadly not.
The only way to find out the ES/SES statistics is by using a debug tool called TC Console. Send me a 'trust' message and I should be able to email you some instructions and the tool itself.
CRC errors cause either or both errored seconds/severly errored seconds. Unfortunately ASUS, for some reason, neglected to include two vital metrics in the statistics on the web UI.
I can't say what's a good CRC error count as it's the ES and SES that DLM looks at.
Fritz!Box 7490 is running considerably better, even compared to the HG612, in terms of error statistics. So far, 124 ES DS and 9 ES US on nearly 9h 30m uptime. On the HG612 I'd have at least 500 ES DS with the same uptime. I can't eliminate the second router for now as using a LAN IP on the Fritz!Box 7490 - while it works fine - it doesn't allow me to access any public IPv4 address I've been allocated, only other LAN IP's or the internet in general.
Pleased to hear you finally got it working, have you had any reboots doing it this way?
So far, no. The rate of errors have increased during daytime it seems, so presumably I get more noise on the line during daylight hours than I do at night. The rate of errors is still lower than the HG612 however. My attainable might be lower at the moment due to power cutback too. There's a setting in telnet which can be adjusted to attempt to change the power cutback offset but for the moment I won't touch it or anything else until I'm absolutely certain the router's not going to crash or reboot randomly on me.
How long do PC world give you to return the ASUS?
I'm pretty sure the guy who served me mentioned 30 days but was unsure.
I think I've still got my HG612 in the loft but not sure if it's the correct version for G.INP.
What put me off the Netgear was the fact it didn't look like it was worth the same cost as the ASUS, I presume WIFI is a lot worse on it without any antenna's and the GUI is meant to be awful.
So far, no. The rate of errors have increased during daytime it seems, so presumably I get more noise on the line during daylight hours than I do at night. The rate of errors is still lower than the HG612 however. My attainable might be lower at the moment due to power cutback too. There's a setting in telnet which can be adjusted to attempt to change the power cutback offset but for the moment I won't touch it or anything else until I'm absolutely certain the router's not going to crash or reboot randomly on me.
One other thing I was told is to attempt to use the previous version of DSL firmware (a setting on the DSL settings page), this might boost attainable but may have a negative effect on the rate of errors.
I've just made myself a new Y cable for the Fritzbox using a RJ11 shielded data cable, a phone cable and a tool-less RJ45 connector. I've just gained an additional 4mbps DS so I'm guessing the Y cable provided from Fritz are of lesser quality.
I've just made myself a new Y cable for the Fritzbox using a RJ11 shielded data cable, a phone cable and a tool-less RJ45 connector. I've just gained an additional 4mbps DS so I'm guessing the Y cable provided from Fritz are of lesser quality.
Yeah, well I'm not even using the supplied Y cable at the moment, just a standard adslnation RJ11 shielded cable. In the past I've used an RJ45 to RJ45 (since the new current SSFP's can take an RJ45 or RJ11). Past experience with the Y cable has yielded worse statistics.
I'm pretty sure the guy who served me mentioned 30 days but was unsure.
I think I've still got my HG612 in the loft but not sure if it's the correct version for G.INP.