In reply to:

---

]ust to show what I had before I fitted the filtered faceplate

---

Yes the filtered faceplate makes a difference.

p.s. your line is better than mine as you have the same attenuation as me and can sync 512 Kb higher and still have the same SNR margin as me!

I never said error rates dont increase with higher speeds, of course they do I just said they known to misreport exact error counts.

If I synch extremely low on the speedtouch, about 1mbit instead of 5mbit crc errors then go down to maybe a few dozen a day but there is no noticeable difference on anything other than slower downloads.

Incidently my billion 7402 that I am using now has some weird error counts as well.

crc errors for both upstream and downstream on atm are both reported as 0.

errors on the ppp interface is approx 30% of what I got on the speedtouch on adsl1 for the same synch, however there is considerably more upstream errors reported. I am not sure if these are the proper crc errors tho but when they do go up I seem to get restransmits (unlike the speedtouch). Also unlike the speedtouch these ppp errors go up depending on what bandwidth I am using, eg. my upstream errors I had 0 for many hours, then during a single upload speedtest on thinkbroadband there was approx 30 errors. Downloading seems to also increase the downstream error count in the same manner. Of course to make it more confusing on this router the ethernet page reports errors as well.

Your upstream errors look high curly considering your upstream is interleaved, you have 18db noise margin and only synched at 448kbit.

In reply to:

---

Your upstream errors look high curly considering your upstream is interleaved, you have 18db noise margin and only synched at 448kbit.

---

I know that my upstream channel is interleaved but even so are the upstream errors high on an uptime of 30 days (latest router stats)


Uptime: 30 days, 1:37:10
Modulation: G.992.1 Annex A
Bandwidth (Up/Down) [kbps/kbps]: 448 / 3,520
Data Transferred (Sent/Received) [MB/GB]: 750.02 / 11.05
Output Power (Up/Down) [dBm]: 11.5 / 18.0
Line Attenuation (Up/Down) [dB]: 31.5 / 55.0
SN Margin (Up/Down) [dB]: 18.0 / 8.5
Vendor ID (Local/Remote): TMMB / 
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 18,117 / 0
FEC Errors (Up/Down): 4,352 / 6,138,875
CRC Errors (Up/Down): 2,416 / 60,859
HEC Errors (Up/Down): 1,702 / 53,667


p.s. I think they are quite low because of the 30 days uptime, should they be lower than this then?

yeah all my adsl1 synchs on ukonline I had 0 crc errors, and of course 0 fec as no interleaving on a 768kbit synch with 13db noise margin. Thats with the 6.2.29.2 firmware, I know on 6.1.4.3 I did get some upstream errors but they werent in the thousands.

However you got 0 remote errored seconds which I consider a more accurate figure than the crc errors on the speedtouch.

Edited by Chrysalis (Mon 14-Jul-08 19:03:22)

In reply to:

---

yeah all my adsl1 synchs on ukonline I had 0 crc errors, and of course 0 fec as no interleaving on a 768kbit synch with 13db noise margin. Thats with the 6.2.29.2 firmware

---

I wonder if the SpeedTouch firmware is correctly showing the CRC errors as surely you would have some upstream CRC errors?

In reply to:

---

However you got 0 remote errored seconds which I consider a more accurate figure than the crc errors on the speedtouch.

---

I don't think that I've seen anyone with remote errored seconds

I believe the upstream CRC and HEC errors and also the upstream FEC errors and, as these are corrected, there's nothing to worry about (I think so anyway)

well I would actually find it unusual having upstream crc errors because it is 10db+ snrm on a part of the line that should typically not be affected by am radio.

On the billion I have now found the proper error counts in the cli, from what I see even on a 950kbit upstream I have no crc errors, I am getting approx 200 crc errors per hour tho during the night on the downstream. On the billion the errored seconds appear to be going up whenever there is a crc error, there is also a seperate severely errored seconds counter which is staying on 0.

At the end of the day if the connection is fine, no packet loss, no missing images on pages etc. its best just to ignore the errors because they always going to be there and what matters is how the connection performs.