G.INP

[#1]

So FortKnox has
- Downstream interleaving matrix of 4x238 = 952
- Downstream FEC overhead of 10 bytes per 238 bytes = 4%
- Upstream interleaving matrix of 4x163 = 652
- Upstream FEC overhead of 16 bytes per 163 bytes = 10%
Compared with npr:
- Downstream interleaving matrix of 473x64 = 30,272
I'd guess that DLM has indeed intervened using G.INP for FortKnox - these figures are wildly different from a "normal" intervention. It is a guess as to what everything means though, as no-one has a lot of experience interpreting these things.
Do you have the lower half of the Netgear page? I'm looking specifically for the sections about bearer 1 and the section containing INP, INPrein and delay.

[#2]

Here is the rest of the Netgear page as requested.

[#3]

Did the new pictures help in any way WWWombat?

[#4]

Sorry to post in your thread, but not sure if this has to do with G.INP. Since i had fibre about 4-5 months ago i have always been on 80/20 fast path. However i checked my router stats and even though it seems i havent realy had any disconects its reporting that its now on 16 acording to the linestats program. G.INP also now seems active.

Quote

xdslcmd info --stats xdslcmd: ADSL driver and PHY status Status: Showtime Retrain Reason: 1 Last initialization procedure status: 0 Max: Upstream rate = 38593 Kbps, Downstream rate = 103048 Kbps Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 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): 12.3 17.9 Attn(dB): 12.3 0.0 Pwr(dBm): 13.6 1.9 VDSL2 framing Bearer 0 MSGc: -6 -6 B: 130 97 M: 1 1 T: 0 0 R: 8 8 S: 0.0518 0.1554 L: 21468 5457 D: 16 8 I: 139 106 N: 139 106 Q: 16 8 V: 14 2 RxQueue: 60 39 TxQueue: 20 13 G.INP Framing: 18 18 G.INP lookback: 20 13 RRC bits: 24 24 Bearer 1 MSGc: 186 58 B: 0 0 M: 2 2 T: 2 2 R: 16 16 S: 5.3333 16.0000 L: 48 16 D: 3 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: 2734095472 528284 RSCorr: 24893 6707 RSUnCorr: 0 0 Bearer 1 OHF: 47402272 401648 OHFErr: 0 0 RS: 568826521 1371711 RSCorr: 3 6 RSUnCorr: 0 0 Retransmit Counters rtx_tx: 1326 138 rtx_c: 1185 125 rtx_uc: 0 0 G.INP Counters LEFTRS: 9 2 minEFTR: 79999 19997 errFreeBits: 929025460 232226050 Bearer 0 HEC: 0 0 OCD: 0 0 LCD: 0 0 Total Cells: 1173293021 0 Data Cells: 4255707463 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: 1135 97 SES: 22 0 UAS: 328 306 AS: 761402 Bearer 0 INP: 48.00 47.00 INPRein: 0.00 0.00 delay: 0 0 PER: 0.00 0.00 OR: 0.01 0.01 AgR: 80614.82 20102.08 Bearer 1 INP: 4.00 4.00 INPRein: 4.00 4.00 delay: 3 0 PER: 16.06 16.06 OR: 95.62 31.87 AgR: 95.62 31.87 Bitswap: 570441/570442 632/634 Total time = 1 days 28 min 47 sec FEC: 24893 6707 CRC: 0 0 ES: 1135 97 SES: 22 0 UAS: 328 306 LOS: 2 0 LOF: 19 0 LOM: 0 0 Latest 15 minutes time = 13 min 47 sec FEC: 24 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: 30 2 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 = 28 min 47 sec FEC: 54 2 CRC: 0 0 ES: 0 0 SES: 0 0 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 Previous 1 day time = 24 hours 0 sec FEC: 2558 142 CRC: 0 0 ES: 0 0 SES: 0 0 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 Since Link time = 8 days 19 hours 30 min 1 sec FEC: 24893 6707 CRC: 0 0 ES: 0 0 SES: 0 0 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 HELLO HG612 xdslcmd info --pbParams xdslcmd: ADSL driver and PHY status Status: Showtime Retrain Reason: 1 Last initialization procedure status: 0 Max: Upstream rate = 38593 Kbps, Downstream rate = 103048 Kbps Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps Discovery Phase (Initial) Band Plan US: (7,32) (871,1205) (1972,2782) DS: (33,859) (1216,1961) (2793,3959) Medley Phase (Final) Band Plan US: (7,32) (871,1205) (1972,2782) DS: (33,859) (1216,1961) (2793,3959)   VDSL Port Details   Upstream   Downstream Attainable Net Data Rate:     38593 kbps   103048 kbps Actual Aggregate Tx Power:       1.9 dBm     13.6 dBm ====================================================================================   VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3   Line Attenuation(dB): 4.6 15.0 20.4   N/A   N/A 7.6 17.6 26.0 Signal Attenuation(dB): 4.6 14.1 19.5   N/A   N/A 9.5 17.4 26.0 SNR Margin(dB): 18.0 17.9 17.9   N/A   N/A 12.3 12.3 12.3 TX Power(dBm): -12.3 -28.6 1.8   N/A   N/A 10.8 7.8 6.9 Good Bye HG612

However my pings seems to be the same as seen here; if i am correct being on interleave you most likely would not see pings under 20?

Quote

C:\Users\>tracert google.co.uk Tracing route to google.co.uk [216.58.210.35] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  router.asus.com   2    17 ms    16 ms    16 ms  lo0.10.Central10.ptw-bng02.plus.net [195.166.130 .203]   3    20 ms    16 ms    15 ms  irb.10.PTW-CR02.plus.net [84.93.249.2]   4    16 ms    16 ms    16 ms  72.14.223.32   5    16 ms    16 ms    15 ms  209.85.252.188   6    16 ms    16 ms    16 ms  72.14.238.21   7    16 ms    17 ms    16 ms  lhr14s23-in-f3.1e100.net [216.58.210.35] Trace complete.

Was wondering if you guys that know more about line stats could tell me what you think? THanks.

[#5]

G.INP is that new we are all still learning what to expect from the stats. Thanks for posting yours, they're only the second with, G.INP enabled, that we've seen here.
It's reassuring to know your ping times have not gone up but as you were on fastpath before I would guess G.INP is not working very hard on your line.
I assume that's from a unlocked HG612 modem?

[#6]

Hey, yes its from an unlocked HG612
If anyone was wondering which firmware its running with G.INP actually working (that's unlocked) i'm running V100R001C01B030SP08 made by H-WOLF.
I did try looking around too npr but as you said no one really knows at the moment with G.INP. I'm not bothered anyway what the interleaving / fast path says on the modem as long as its not increasing my pings. Which it does not seem to be.

[#7]

Do you know the version number of the broadcom modem driver?
the command  xdslcmd info --version  will show it.
eg  my router uses 039e:
ADSL PHY: AnnexA version - A2pv6F039e.d24h
I wouldn't be concerned that the stats show a very small interleaving depth, it's a different system which I don't think related to interleaving as we know it.
I'm looking forward to seeing it on my line, hoping it will reduce some of the impact of aluminium cables.
Have a look at this link if you're looking for more reading on this:
http://forum.kitz.co.uk/index.php?topic=14867.0

[#8]

Hey it comes back saying: DSL PHY: AnnexA version - A2pv6C038m.d24j
Thanks ill take a look at the link

[#9]

Reading through this thread I'm a bit confused how I'd tell if this is enabled on my line?
I'm using the Huawei modem so can check stats etc, and can only see INP = 3.

[#10]

I would say it's G.INP is not active on your line.
In the above stats posted by carlmagic, look for:
"G.INP Framing:      18      18"
"G.INP lookback:      20      13"
Not sure of the significance of the numbers yet, but it appears to only show when G.INP is active.
also
"Bearer 1"
Bearer 0 is the standard connection, Bearer 1 is the path used by G.INP and is only shown when G.INP is active.
also a less convincing indication.
look at the interleave depth for Bearer 0
😧      16      8
A small number (>1 but <100's) appears to indicate G.INP may be active.

[#11]

Would like to just let anyone else who notices G.INP is also now enabled on their line they might find that HG612_Modem_Stats program fails to work (Crashes). This is due to the extra fields that are used in G.INP and the program not knowing how to deal with it, this is known by the author now and I am helping him try his new version / providing error logs. So he is working on fixing it

[#12]

Quick update to carlmagic's post
Thanks to carlmagic's assistance & testing etc. I now have HG612 Modem Stats working both with G.INP enabled & G.INP not enabled connections & am busy writing the code to graph these new/additional stats.
It is not enabled on my connection, so it's a bit of a slow process to get it right as I can't test anything immediately.
At the moment, I'm concentrating on the Huawei HG612, but the code for modems such as Billion & ZyXel will also follow in due course.

[#13]

Does anyone know if DSLstats v5.3 support G.INP ?

[#14]

As far as I can tell it doesn't seem to have anything to show if G.INP is active or not. It shows Interleaving but nothing about G.INP. Maybe it will be added in future updates?

[#15]

Quote from: npr

Does anyone know if DSLstats v5.3 support G.INP ?

It doesnt report any of the G.INP values. Its also showing my connection as interleaved when really its running G.INP. So its not supported properly. However other features still work.