Print

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

[N0STIE]

Ok all done.

The only thing that changed is Errors (Pkts) 12118 on Downstream. Is it something that I should be worried about?

Below is the screenshot.

edit:

Now the Errors (Pkts) are 12120.

Yes, I did factory reset of the router after installing the latest firmware.

[mlmclaren]

MIght be nothing, might be a firmware bug, have they got any worse?

Possibilty that its picking up FEC's as errors... FEC's are Forard Error Corrections and that would just show that Interleaving or G.INP is doing it work...

[N0STIE]

Yes, they are still couting. 12164 right now.

[ejs]

I think the errors reported there are CRC errors. All the previous firmware versions had the bug mentioned in the release notes, and they always displayed zero for the error count, not the actual number. So you can't really know if they have got worse or not.

[N0STIE]

Alright, thanks for explanation. Connection seems to be stable so I'll leave it alone.

Is there any way to monitor more advanced line stats like with HG612 3B? TD-W9980 shows only basic stats :/

[NewtronStar]

Is there any way to monitor more advanced line stats like with HG612 3B? TD-W9980 shows only basic stats :/

If you read the review by Kitz in the summary that was one of the drawbacks ->

Some line stats are available but none of the VDSL diagnostic information data is available.  This is very disappointing as the information is available from the chipset.  I feel TP-Link have missed a trick here by not including this information.

[ejs]

It's possible to upload a specially modified config file, and gain shell access, then you'll be able to get the data.

See TP-Link TD-W9980 shell access trick.

Once that's done, automatically monitoring the stats would require creating some program, script or some sort of system yourself, or perhaps helping the developer add support to their existing program.