In reply to a post by RobertoS:

Following on from my original thought, was this sold with no mention of already being locked or unlocked?

There's a vague possibility it is unlocked and someone has set it to a different IP address than 192.168.1.1.

I suggest doing a factory reset on it. That will either set it to OR defaults or to the defaults of the flashed version. In other words it will ensure it is on 192.168.1.1. Then try again.

Good idea. As it was from eBay there was no indication it had been unlocked but I guess it's worth a try.

Latest update: I managed to unlock the HG612 today and get access to stats.

According to the TBB checker, my average download speed has gone down to 39.11 Mb/s and the upload is now 10.7Mb/s. When I was first connected back in July I was getting about 54Mb/s download, 8.5Mb/s upload on a HH5A only.

The info from the HG612 is appended. Does this look normal i.e. is the speed dropoff on download due to crosstalk and the increase on upload due to the HG612 supporting G.INP (the increase happenned when I started using the HG612, but the download has been getting slowly worse ever since lasy July)?



# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 12683 Kbps, Downstream rate = 51360 Kbps
Bearer: 0, Upstream rate = 12687 Kbps, Downstream rate = 43998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps



# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 12683 Kbps, Downstream rate = 51360 Kbps
Bearer: 0, Upstream rate = 12687 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): 8.1 6.1
Attn(dB): 20.4 0.0
Pwr(dBm): 12.4 7.5
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 89 227
M: 1 1
T: 0 0
R: 8 14
S: 0.0648 0.5716
L: 12108 3387
D: 8 4
I: 98 242
N: 98 242
Q: 8 4
V: 3 0
RxQueue: 135 21
TxQueue: 27 7
G.INP Framing: 18 18
G.INP lookback: 27 7
RRC bits: 24 24
Bearer 1
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
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 0
OHFErr: 0 0
RS: 21352688 2428343
RSCorr: 79 13
RSUnCorr: 0 0
Bearer 1
OHF: 21665 21690
OHFErr: 0 0
RS: 129619 86763
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 227561531 1
rtx_c: 15 4307
rtx_uc: 0 8202

G.INP Counters
LEFTRS: 0 98
minEFTR: 43989 12688
errFreeBits: 233508 86033498

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 29423105 0
Data Cells: 16661 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: 0 0
SES: 0 0
UAS: 31 31
AS: 349

Bearer 0
INP: 55.00 45.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 44305.29 12714.56

Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87

Bitswap: 106/106 18/18

Total time = 6 min 20 sec
FEC: 79 13
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 20 sec
FEC: 79 13
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 0 sec
FEC: 0 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 = 6 min 20 sec
FEC: 79 13
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 5 min 47 sec
FEC: 79 13
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

I haven't time to think about those stats in depth but notice a couple of things.

1) From your suspiciously close to 44000kbps sync and 8.1dB SNRM after 6 minutes uptime I think the line has probably been banded.

2) Not only is G.INP enabled, it is also operating on your upstream. That may be why the upstream interleaving D: line is set to 4 rather than the normal 1.

I believe that now you have the HG612 running that in a few weeks the banding will be removed and your speed increase.

So the reality in this thread seems to be that there's still no evidence to suggest the HH5a isn't capable of G.INP on the 'downstream' and that upstream G.INP is coming back,

However changing from the HH5a to the HG612 would show the line as being Fastpath/Interleaved (If it wasn't capable of G.INP) for little while whilst DLM determined the change and placed the line on a G.INP profile...

SO would this continue to lean towards saying the HH5a is indeed capable on 'downstream' and the small boost seen when the HG612 was connected was the configured G.INP being used to its full potential...

However what hasn't been mentioned is whether any decreases in latency has been seen since the swap?

In reply to a post by BatBoy:

Because if it did, there would be evidence. As someone pointed out, a GEA test result would show if retransmission was present on a line having a HH5A.

Have you got the results of a GEA test to hand... though I will probably see if someone on Plusnet could get such things though things on that ship have certainly changed since I was a customer so they might not share that stuff anymore.

The fact that the Plusnet Hub One is the same hardware as an HH5A doesn't mean the firmwares are the same.

Of course, however the likelihood of BT & Plusnet HH5a's having different DSL specification's is very unlikely surely?