Nope, it's been enabled on my line several times.

Link.

I think it quite likely you are misinterpreting something in the stats. Perhaps some time you will supply some. Taken since it was disabled.

Ok, so you see where it says 0.00 in this screenshot? That has been 50.00 before... https://i.gyazo.com/50a119b5f757209b8fbe13ed25e8374f...

Please stop presuming that I don't have a clue! I know a lot about how DSL works!

Edited by deleted (Sat 08-Apr-17 21:51:18)

Recently? Because I think Bob is talking historic.

Yeah, right! Show me, so we can see what the other stats are when it is 50. IIRC that line is not indicative of G.INP being enabled. It is also present on lines that clearly are not.

INP (Impulse Noise Protection) is present on ADSLx as well as VDSL2. Always has been.

Telnet stats are far more informative as they show G.INP definitively. Knowing as much as you do, no doubt next time you have an upstream figure you could give us those rather than a GUI-shot designed before Openreach implemented it.

> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 13600 Kbps, Downstream rate = 64643 Kbps
Bearer: 0, Upstream rate = 13596 Kbps, Downstream rate = 63790 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): 6.1 6.1
Attn(dB): 19.1 0.0
Pwr(dBm): 13.7 7.4

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 59
R: 10 16
S: 0.1218 0.5567
L: 16683 3650
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 51 0
TxQueue: 17 0
G.INP Framing: 18 0
G.INP lookback: 17 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 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 59095
OHFErr: 6 44
RS: 2591400024 869139
RSCorr: 1968444 374
RSUnCorr: 0 0
Bearer 1
OHF: 37627455 0
OHFErr: 0 0
RS: 376273930 0
RSCorr: 4 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 87741 0
rtx_c: 18811 0
rtx_uc: 23 0

G.INP Counters
LEFTRS: 267 0
minEFTR: 63783 0
errFreeBits: 588066598 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1127247475 0
Data Cells: 94941999 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: 5 44
SES: 0 0
UAS: 29 29
AS: 604466

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.24
OR: 0.01 31.05
AgR: 63855.32 13627.08

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 281347/301517 6808/6846

I had G.INP enabled about 2 days after activation back in mid-March 2017. First the DS G.inp was enabled at 16 interleave depth which went down to 8.

Then there were errors on the US which caused G.inp to be enabled at 8 interleave depth which eventually disappeared after a day to be replaced by fastpath.

So answer to your question is yes - it will most likely be enabled if you are on a Huawei line and DLM determines that your line would be better off with it (as opposed to fastpath.) Of course this is just 1 sample size out of many as Roberto has said.