Would a change of modem/router help? I don't like the HH5, the wifi performance sucks, wondering if its worth shelling out for a Billion 8800axl...

A change from the HH5A would probably solve most if not all your problems, as long as the replacement has a Broadcom chipset (or at least support G.INP) like the Billion.

For a quick fix, you could buy a Huawei HG612 v3B from the Bay Of Fleas, load on the latest hacked firmware and monitor your connection. This can be connected to the phone line and then LAN1 on the modem to the red WAN port on the HH5A instead.

In reply to a post by keith969:

Would a change of modem/router help?

A new modem is unlikely to improve your sync speed by anything noteworthy.

Over 18 months, we've lost 40% of our speed, falling from 44 Mbps when FTTC first arrived, to just 26 Mbps today. No longer much improvement over our old LLU ADSL2+ service. From which we could squeeze up to 20Mbps just by tweaking the target SNR margin. Alas, such a tweak isn't possible with BT's VDSL2 offering.

Since our line is in otherwise 'good order' with very low DSL error rates, that drop in speed is due to crosstalk. Which is a problem across the board, as migrations from ADSL to FTTC gather pace.

Switching to a Broadcom-based device can perhaps see small gains. Maybe an increase of a megabit or two per second. Compared to devices with less-refined DSP chipsets. But nothing - short of full deployment of system-level or maybe even node-level vectoring - can recover much of what we've lost already to crosstalk.

And since full-blown vectoring will likely involve stripping-out and replacing the existing DSLAMs and linecards - definitely the ECI kit and likely Huawei's too - that ain't going to happen any time soon. Until BT pulls its finger out and invests, we're stuck with an ever degrading service.

Edited by deleted (Mon 02-Nov-15 00:51:42)

In reply to a post by BatBoy:

A change from the HH5A would probably solve most if not all your problems, as long as the replacement has a Broadcom chipset (or at least support G.INP) like the Billion.

For a quick fix, you could buy a Huawei HG612 v3B from the Bay Of Fleas, load on the latest hacked firmware and monitor your connection. This can be connected to the phone line and then LAN1 on the modem to the red WAN port on the HH5A instead.

I changed to a HG612 as the modem and the HH5 as the router / WAP. This improved the upload performance from about 8.5 to 10 Mb/s but the download did not change and is now down to 39Mb/s. BT, who I just called, said it was within 'acceptable range', the lower bound being 35Mb/s and they would not change my contract from Infinity 2 to Infinity 1 despite only getting Infinity 1 speeds. Told me to call their tech team instead...

When did you start using the HG612?

In reply to a post by BatBoy:

When did you start using the HG612?

Probably about a week ago.

It can take a couple of weeks for G.INP to be turned on. Is the HG612 unlocked?

In reply to a post by BatBoy:

It can take a couple of weeks for G.INP to be turned on. Is the HG612 unlocked?

yep its unlocked. As far as G.INP, the stats indicate for bearer 1:

G.INP Framing: 18 18
G.INP lookback: 27 7

does this mean G.INP is enabled? The upload speed went up by 10% or so when the HG612 was connected...

Yes G.INP looks to be enabled. More stats will help diagnosis.

In reply to a post by BatBoy:

Yes G.INP looks to be enabled. More stats will help diagnosis.

This was from a few days ago...

# 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
#