RiderSite.com - Motorcycle Forums

Just as I was about to log in and post about a query I have with Broadband.. and I have problems logging onto RS! Methinks it was a cookie problem, so no drama. Anyway..

Does anyone uderstand ADSL information?

If so, would you say from reading the figures below that I am suffering a problem with broadband? Any ideas on a cure?

My down speed is 8400mbps and upstream is 400mbps ish.. but I seem to suffer download problems, streaming problems a bit like ping on a multiplayer videogame and the pooter seems to have general malaise with anything to do with the internet.

ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.1
Latency type Interleaved
Noise margin (Down/Up) 5.9 dB / 24.0 dB
Line attenuation (Down/Up) 22.0 dB / 11.5 dB
Output power (Down/Up) 19.8 dBm / 12.3 dBm
Loss of Framing (Local) 236
Loss of Signal (Local) 162
Loss of Power (Local) 0
FEC Errors (Down/Up) 130728 / 35
CRC Errors (Down/Up) 195 / 2147480000
HEC Errors (Down/Up) nil / 14
Error Seconds (Local) 579

Do you know how long a period the stats cover? I ask because there are some very high errors shown but is the period if over several months, it could be old data. Best to reset your router, check the FEC / CRC error counters are near zero, then try a download and upload and see what the figures are.

Your download and upload speeds look fine but that's just a measure of raw data throughput and doesn't mean the data your getting is actually any good.

The FEC (forward Error Correction) is a system of sending a code with the data so that the receiving end can check the code and apply correction to any of the data that may have been corrupted - say due to noise on the line. The higher the count, the more correction is being applied and there's a fairly high count being shown.

The CRC (Cyclic Redundancy Check) is a system where a block of code is sent with the data. The code is specific to the data packet being sent and is calculated from the data in the packet so, at the receiving end, the calculation is performed again and the result checked against the CRC sum - if they don't match - maybe due to data corruption over the line - it throws a CRC error. In many systems, this causes a re-transmission of the data which, of course, slows everything down. There are some very high CRC errors in your list.

In addition, there's quite a high number of errored seconds - this is a cumulative count of periods of time where the data was considered unuseable.

It could be down to a noisy line although the noise margin, while not great, should be sufficient (it can vary through the day so would be worth a check when you're having partcular problems - lower figure=worse).
Sorry it's bit long winded but hope it helps.

(Edit: why do I feel like a geek?)

Now that is what I call a comprehensive reply (I don't understand a bit of it Dave but it sounds sooooooooooooooooooo impressive

F9

Very impressive answer!!

The uptime is 9 and a half days, so those figures were for that kinda time I assume as the figures reset when it goes down?

And yes, it does help a bit. Cheers

Falco9 wrote:Now that is what I call a comprehensive reply (I don't understand a bit of it Dave but it sounds sooooooooooooooooooo impressive

F9

It's an old adage...... if you're gonna talk b**locks, do it with style and conviction. It's worked all my life