O2BB speed

owitemisermusa

New stats after reset/resynch:

Uptime: 0 days, 0:02:14
DSL Type: G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]: 1,222 / 4,549
Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00
Output Power (Up/Down) [dBm]: 12.0 / 19.0
Line Attenuation (Up/Down) [dB]: 25.5 / 45.0
SN Margin (Up/Down) [dB]: 6.0 / 6.5
Vendor ID (Local/Remote): TMMB / BDCM
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): 0 / 0
FEC Errors (Up/Down): 0 / 2,738
CRC Errors (Up/Down): 0 / 1
HEC Errors (Up/Down): 412 / 1


Thanks MKD! Speedtest is now showing 3.89mbps download!

Thanks again, man!

Woby_Tide

owitemisermusa wrote: »

Stats:

Loss of Framing (Local/Remote): 20 / 0
Loss of Signal (Local/Remote): 2 / 0

Something is up with the connection at your place with those figures, and probably why your SNR creeps out

According to
http://be.nfshost.com/go.php
4 of your stats seem OK, the rest highlight potential issues

2 Loss of Signal Local errors. These are okay as rare one-offs, but should not occur regularly. Expected download speed at your current sync rate: 271.17 KB per second (or 2169 kbit) Expected upload speed at your current sync rate: 130.43 KB per second (or 1043 kbit) The average upstream sync speed attained by other users with the same upstream attenuation as you (25dB) is 1075 kbit (151 kbit or 14 percent slower than your connection). If you are using Fast Path, then that would explain the increase. Downstream sync speed of 2549 kbit is 4578 kbit slower or 36 percent of the average for connections with the same downstream attenuation of 44.5dB. Signal Noise Margin Down (14dB) is extremely high. Be* may have put you on this profile to compensate for a high error rate. If you know that your line is actually reliable, lowering the value to the average of 6dB should give a sync speed increase. Call Be* to change it (3dB steps only). There are some FEC Up errors. FEC errors are *corrected* errors, so these are probably nothing to worry about. Speedtouch routers have a habit of misreporting FEC errors anyway. Zillions (20) of Loss of Framing errors, which should ideally never or rarely occur. There must be (or have briefly been) a problem with your line.

owitemisermusa

Thanks woby, the losses seem to have settled down after the restart.
I'll watch things and see.
Thanks again.