Print

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

[jaggythistle]

Hi All - apologies if this is a really stupid question, but is the max connection speed reported via telnet in DSLstats what I could actually get from my line if I upgraded my BB package?

I'm currently on a BT 40/20 package (can't remember what is was called at the time), but from the so called upgrade offers for existing customers what's now called "Fibre 2" is £5 cheaper than taking the "Fibre plus Halo 1" option.  Don't really need the benefits (minimal as they are) of what you get with Halo, but unhelpfully the d/l speed range quoted by BT for both options is the same.

So I thought I'd check what DSLstats reports to see if there was anything that might help me decide if it's worth upgrading or not.  But I'm far from an expert in understanding line stats so I just wanted to check that the Max Connection Speed reported is what I could actually achieve if I upgrade to the Fibre 2 plan.

It may not actually be worth it as I'm getting good d/l and u/l speeds at the moment anyway - aging but solid HG612 and averaging around 38Mbps/18Mbps - although looks like I could get up to approx. 60Mbps (telnet reporting 63,000 Kbps).  So not sure I would really notice an appreciable difference, although an increase in speed can't be bad I guess.  Thanks.

[jelv]

What does https://www.broadbandchecker.btwholesale.com/#/ADSL say when you put in your phone number?

[jaggythistle]

Thanks for the link, result atatched and looks promising 

[j0hn]

I'm currently on a BT 40/20 package

There is no 40/20 package.

The packages are
40/2
40/10
55/10
80/20

If you get 18Mb upload then you must be on the 80/20 package already.

BT upgraded many customers to 80/20 for free some time ago.

"Upgrading" will cost you more but give no more speed.

Can you post the full connection stats from Dslstats?

Edit: I notice your price would drop if you "upgraded". Might be worth it for the saving but it still might not increase speeds.

Your line might be banded/capped.

[ktz392837]

It depends.  Post your telnet stats and people can give you an answer.

[jaggythistle]

Ok, thanks folks, will post the connection stats.

There is no 40/20 package.

Your line might be banded/capped.

I've never seen connection speed go above 37/38 Mbps for download so guess I lost out on getting a switch to 80/20.  Presume there is a cap in place then (I can't remember what the package was last time i renewed tbh).

[jaggythistle]

Ok, connection stats in the attached screenshot - advice much appreciated (let me know if any more stats will help).

[jaydub]

With a 9dB SNR and a sync rate of almost exactly 44 Mbps, I would have to say your line has been banded because of some past performance issue.

It would be useful to see your full stats.  Can you copy the full stats from DSLStats and paste them here.

[jaggythistle]

Thanks for the reply.  Hopefully this is what you're after:

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 20547 Kbps, Downstream rate = 60808 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 43998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 9.9 4.0
Attn(dB): 19.5 0.0
Pwr(dBm): 13.3 7.5
VDSL2 framing
Bearer 0
MSGc: -6 20
B: 179 239
M: 1 1
T: 0 64
R: 12 0
S: 0.1295 0.3819
L: 11861 5028
D: 4 1
I: 192 120
N: 192 240
Q: 4 0
V: 3 0
RxQueue: 135 0
TxQueue: 27 0
G.INP Framing: 18 0
G.INP lookback: 27 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 2182150
OHFErr: 6 680
RS: 3362090568 1353667
RSCorr: 96958543 0
RSUnCorr: 0 0
Bearer 1
OHF: 41565447 0
OHFErr: 0 0
RS: 249392312 0
RSCorr: 1 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 2247900 0
rtx_c: 990187061 0
rtx_uc: 423542 0

G.INP Counters
LEFTRS: 170957 0
minEFTR: 43966 0
errFreeBits: 2992172332 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 631146120 0
Data Cells: 604599903 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 5178 7117
SES: 83 33
UAS: 705 653
AS: 667644

Bearer 0
INP: 55.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 6.13
OR: 0.01 33.91
AgR: 44305.68 20033.74

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Bitswap: 322871/322871 15174/15213

Total time = 1 days 5 hours 14 min 26 sec
FEC: 128088088 20307
CRC: 9968 11850
ES: 5178 7117
SES: 83 33
UAS: 705 653
LOS: 5 0
LOF: 46 0
LOM: 0 0
Latest 15 minutes time = 14 min 26 sec
FEC: 142982 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 104826 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 5 hours 14 min 26 sec
FEC: 2195045 0
CRC: 0 4
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 19013718 0
CRC: 0 69
ES: 0 59
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 7 days 17 hours 27 min 23 sec
FEC: 96958543 0
CRC: 6 680
ES: 2 466
SES: 0 1
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#


[j0hn]

Ok, thanks folks, will post the connection stats.

I've never seen connection speed go above 37/38 Mbps for download so guess I lost out on getting a switch to 80/20.  Presume there is a cap in place then (I can't remember what the package was last time i renewed tbh).

You definitely got upgraded to 80/20.

You can't have an upload sync above 10Mb without being on 80/20.

From the stats the DLM has capped your line at 44Mb

[jaydub]

Thanks for the reply.  Hopefully this is what you're after:

You have GINP and interleaving on your line plus a lot of errored seconds.  I'm not familiar enough with GINP lines to comment, so will leave it to the more knowledgeable members to discuss the significance.

[j0hn]

You have GINP and interleaving on your line plus a lot of errored seconds.

2 ES in the last 7 days.

The "total time" shown is incorrect and is a common bug on the Broadcom CLI.
Total time is meant to show how long the modem has been on.

Total time = 1 days 5 hours 14 min 26 sec

I think (though not sure) it drops a digit off the days. So that could be 11 days or 91 days.

[roseway]

The 'days' figure never exceeds 1, and it continuously cycles through the hours, minutes and seconds. The AS figure (available seconds) is accurate - DSLstats uses this to calculate the DSL uptime shown at the bottom left.

[RealAleMadrid]

As others have stated the line is banded at 44Mbps and would sync much higher if this was removed. Not sure if BT support will have a clue about this, I know PlusNet will request a DLM reset on a banded line. The total time stats are historical and show the modem has not been rebooted for a long time. The unavailable seconds figure shows that there have been possibly around 30 resyncs. (My HG612 shows 23 or 24 seconds for single resync). So there have been problems with the line previously but it looks pretty good now with only 2 error seconds since the last sync over 7 days ago. Good luck with getting the banding removed.

[Jaggies]

Didn't BT do a 40/20 product a few years back, being basically the 80/20 service capped at half speed download?
I'm sure Plusnet also offered the same package. It was withdrawn in favour of the 40/10 option some time later.
In that case the OP is probably on that legacy package.