Topic: TP-Link TD-W9980 & G.INP (Read 33667 times)

kitz · « **Reply #45 on:** April 27, 2015, 11:57:58 AM »

Yep it had already crossed my mind to put the info on the main site and I'd added a note to my desktop. I have to go out now but will look again later.

jelv · « **Reply #46 on:** April 27, 2015, 12:25:33 PM »

Looking at Mere again, does 21CN WBC: 30th September 2013 mean TalkTalk LLU? I would not have expected so and for ADSL Mere is 20CN or TalkTalk LLU only.

If others are seeing a level of inaccuracy on that site, if it is linked it should have a big warning attached!

Edit: The exchange information from http://www.kitz.co.uk/adsl/adslchecker.php is correct.

burakkucat · « **Reply #47 on:** April 27, 2015, 04:12:28 PM »

If you would like inaccurate (but historic) information about the Mere exchange, I can look it up in my 1977 copies of the red and green books!

kitz · « **Reply #48 on:** April 28, 2015, 04:43:33 PM »

Quote from: kitz on April 27, 2015, 11:57:58 AM

Yep it had already crossed my mind to put the info on the main site and I'd added a note to my desktop. I have to go out now but will look again later.

New page added: Look up your Fibre cabinet

edjonesy · « **Reply #49 on:** May 05, 2015, 10:17:50 AM »

I've just installed the beta firmware, my dl has gone from 52 to 59mb and ul from 15 to 17mb, still some way to go though to reach my original stats before BT shafted the HH5 in Feb with a firmware 'upgrade', I was on dl 72mb and ul 19mb for 13 months.

here are the current stats from telnet

nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nChannel=0 nDirection=0 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0

nReturn=0 nChannel=0 nDirection=1 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0

nReturn=0 nChannel=0 nDirection=0 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0

nReturn=0 nChannel=0 nDirection=1 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0

nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=213472 bValid=1 nEftrMin=266680 nErrorFreeBits=196826795 nLeftr=59881

nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=213472 bValid=1 nEftrMin=4294967295 nErrorFreeBits=58924378 nLeftr=0

nReturn=0 nData="5008 0000 0001 0102 "

nReturn=0 nChannel=0 nDirection=0 ActualDataRate=16229000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=550 ActualNetDataRate=17000000 ActualImpulseNoiseProtectionRein=10 ActualImpulseNoiseProtectionNoErasure=40

nReturn=0 nChannel=0 nDirection=1 ActualDataRate=57362000 PreviousDataRate=59997000 ActualInterleaveDelay=14 ActualImpulseNoiseProtection=440 ActualNetDataRate=59997000 ActualImpulseNoiseProtectionRein=10 ActualImpulseNoiseProtectionNoErasure=40

rapid111111 · « **Reply #50 on:** May 05, 2015, 10:27:19 AM »

To report back, 3rd engineer came today.
turns out a new a pair was placed (old pair contacts were damaged according to engineer) in the building basement and my line is now full speed and better than before achieving full 80mbps and i'm seeing single digit pings on game servers which i haven't come across before. I guess that means interleaving is off.

So it had nothing to do with G.INP or TP-W9880 in this case.

licquorice · « **Reply #51 on:** May 05, 2015, 03:02:58 PM »

Quote from: kitz on April 25, 2015, 01:08:35 AM

Would ideally like to also see one from someone on BTretail as they dont use L2TP so we should see the path from backhaul -> RAS -> Internet.

Been on holiday, but if you are still looking for data from BT Retail customer, ping and tracert to BBC below.

Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * 9 ms 8 ms 31.55.186.193
4 10 ms 9 ms 9 ms 31.55.186.212
5 9 ms 10 ms 9 ms 195.99.127.54
6 10 ms 10 ms 10 ms host213-121-193-111.ukcore.bt.net [213.121.
11]
7 10 ms 10 ms 10 ms 194.74.65.42
8 * * * Request timed out.
9 * * * Request timed out.
10 10 ms 10 ms 10 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 11 ms 11 ms 11 ms 132.185.255.149
12 10 ms 10 ms 10 ms bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

Pinging www.bbc.net.uk [212.58.244.69] with 32 bytes of data:
Reply from 212.58.244.69: bytes=32 time=10ms TTL=53
Reply from 212.58.244.69: bytes=32 time=10ms TTL=53
Reply from 212.58.244.69: bytes=32 time=10ms TTL=53
Reply from 212.58.244.69: bytes=32 time=11ms TTL=53

Ping statistics for 212.58.244.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

kitz · « **Reply #52 on:** May 05, 2015, 11:55:48 PM »

Thanks guys.

@Licquorice

Thanks for that ping. It confirms that there is no delay downstream.. as per this from your earlier figures.

Quote

Return=0 nChannel=0 nDirection=0 ActualDataRate=9989000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=470 ActualNetDataRate=10000000 ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=40

What I'd also be interested in seeing is your upstream latency - because I see this on your earlier results:

Quote

nReturn=0 nChannel=0 nDirection=1 ActualDataRate=39950000 PreviousDataRate=39998000 ActualInterleaveDelay=16 ActualImpulseNoiseProtection=440 ActualNetDataRate=39998000 ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=40

For that you'd need to do the test at erik.co.uk as outlined in this post to get a reverse ping.

TIA

licquorice · « **Reply #53 on:** May 06, 2015, 03:59:14 PM »

Reverse ping below. ActualInterleaveDelay=16 still.

PING : 56 data bytes
64 bytes from : icmp_seq=0 ttl=49 time=11.267 ms
64 bytes from : icmp_seq=1 ttl=49 time=11.122 ms
64 bytes from : icmp_seq=2 ttl=49 time=10.885 ms
64 bytes from : icmp_seq=3 ttl=49 time=11.352 ms
64 bytes from : icmp_seq=4 ttl=49 time=11.176 ms

hacktrix2006 · « **Reply #54 on:** May 06, 2015, 04:45:45 PM »

ADSL2+ WBC Customer here.

Here is what my W8980 Modded to W9980 says using said command.

Code: [Select]

nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nChannel=0 nDirection=0 nNFEC=248 nRFEC=16 nLSYMB=264 nINTLVDEPTH=2 nINTLVBLOCK=248 nLPATH=0

nReturn=0 nChannel=0 nDirection=1 nNFEC=255 nRFEC=4 nLSYMB=1847 nINTLVDEPTH=32 nINTLVBLOCK=255 nLPATH=0

nReturn=0 nChannel=0 nDirection=0 nTp=1 nMp=8 nSEQ=76 nBP=28 nMSGC=70 nMSGLP=0

nReturn=0 nChannel=0 nDirection=1 nTp=1 nMp=1 nSEQ=63 nBP=250 nMSGC=57 nMSGLP=0

nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=8513 bValid=1 nEftrMin=4294967295 nErrorFreeBits=0 nLeftr=0

nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=8513 bValid=1 nEftrMin=0 nErrorFreeBits=0 nLeftr=0

nReturn=0 nData="5008 0000 0001 0000 "

nReturn=0 nChannel=0 nDirection=0 ActualDataRate=953000 PreviousDataRate=0 ActualInterleaveDelay=400 ActualImpulseNoiseProtection=20 ActualNetDataRate=953000 Ac
tualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=4

nReturn=0 nChannel=0 nDirection=1 ActualDataRate=7243000 PreviousDataRate=0 ActualInterleaveDelay=900 ActualImpulseNoiseProtection=2 ActualNetDataRate=7243000 A
ctualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=2

Not sure what all that means which makes a change however the connection seems very stable now on this firmware.

edjonesy · « **Reply #55 on:** May 08, 2015, 09:56:48 PM »

some more stats from a BT Infinity II end user, as far as I know I'm connected to a Huawei cabinet.

Traceroute to www.bbc.net.uk, ping test and a reverse ping, plus my router stats which show my upload speed has increased from when I ran the router stats on the 5th May.

Router stats from telnet
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nChannel=0 nDirection=0 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0

nReturn=0 nChannel=0 nDirection=1 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0

nReturn=0 nChannel=0 nDirection=0 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0

nReturn=0 nChannel=0 nDirection=1 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0

nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=141372 bValid=1 nEftrMin=526120 nErrorFreeBits=4081378700 nLeftr=4294967207

nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=141372 bValid=1 nEftrMin=4294967295 nErrorFreeBits=40941709 nLeftr=0

nReturn=0 nData="5008 0000 0001 0102 "

nReturn=0 nChannel=0 nDirection=0 ActualDataRate=18169000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=550 ActualNetDataRate=19000000 ActualImpulseNoiseProtectionRein=10 ActualImpulseNoiseProtectionNoErasure=40

nReturn=0 nChannel=0 nDirection=1 ActualDataRate=57362000 PreviousDataRate=59997000 ActualInterleaveDelay=14 ActualImpulseNoiseProtection=440 ActualNetDataRate=59997000 ActualImpulseNoiseProtectionRein=10 ActualImpulseNoiseProtectionNoErasure=40

Traceroute www.bbc.net.uk via Network Utlity Mac OSX
traceroute: Warning: www.bbc.net.uk has multiple addresses; using 212.58.246.90
traceroute to www.bbc.net.uk (212.58.246.90), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3.761 ms 4.394 ms 9.965 ms
2 * * *
3 * * *
4 31.55.186.140 (31.55.186.140) 19.691 ms 13.129 ms 13.563 ms
5 195.99.127.38 (195.99.127.38) 13.784 ms 14.331 ms 28.132 ms
6 peer2-xe8-1-0.telehouse.ukcore.bt.net (109.159.255.101) 19.539 ms 22.341 ms 25.423 ms
7 194.74.65.42 (194.74.65.42) 13.479 ms 13.642 ms 24.681 ms
8 * * *
9 ae0.er01.cwwtf.bbc.co.uk (132.185.254.93) 17.505 ms 15.360 ms 18.272 ms
10 132.185.255.165 (132.185.255.165) 19.273 ms 21.148 ms 20.252 ms
11 bbc-vip011.cwwtf.bbc.co.uk (212.58.246.90) 20.475 ms 22.776 ms 20.292 ms

Ping www.bbc.net.uk via Network Utlity Mac OSX
PING www.bbc.net.uk (212.58.244.71): 56 data bytes
64 bytes from 212.58.244.71: icmp_seq=0 ttl=53 time=11.098 ms
64 bytes from 212.58.244.71: icmp_seq=1 ttl=53 time=10.549 ms
64 bytes from 212.58.244.71: icmp_seq=2 ttl=53 time=10.631 ms
64 bytes from 212.58.244.71: icmp_seq=3 ttl=53 time=10.928 ms
64 bytes from 212.58.244.71: icmp_seq=4 ttl=53 time=10.996 ms
64 bytes from 212.58.244.71: icmp_seq=5 ttl=53 time=10.787 ms
64 bytes from 212.58.244.71: icmp_seq=6 ttl=53 time=10.979 ms
64 bytes from 212.58.244.71: icmp_seq=7 ttl=53 time=10.616 ms
64 bytes from 212.58.244.71: icmp_seq=8 ttl=53 time=10.778 ms
64 bytes from 212.58.244.71: icmp_seq=9 ttl=53 time=10.891 ms

--- www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 10.549/10.825/11.098/0.174 ms

Reverse Ping
PING: 56 data bytes
64 bytes from 81.140.163.177: icmp_seq=0 ttl=49 time=11.081 ms
64 bytes from 81.140.163.177: icmp_seq=1 ttl=49 time=10.987 ms
64 bytes from 81.140.163.177: icmp_seq=2 ttl=49 time=11.564 ms
64 bytes from 81.140.163.177: icmp_seq=3 ttl=49 time=11.057 ms
64 bytes from 81.140.163.177: icmp_seq=4 ttl=49 time=11.016 ms

--- ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.987/11.141/11.564/0.214 ms

Hope they help

Mooingall · « **Reply #56 on:** May 10, 2015, 01:57:33 AM »

Here are my BT Infinity stats also:

Code: [Select]

nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=0 b20BitSupport=0

nReturn=0 nChannel=0 nDirection=0 nNFEC=95 nRFEC=16 nLSYMB=5949 nINTLVDEPTH=251 nINTLVBLOCK=95 nLPATH=0

nReturn=0 nChannel=0 nDirection=1 nNFEC=80 nRFEC=16 nLSYMB=19758 nINTLVDEPTH=933 nINTLVBLOCK=80 nLPATH=0

nReturn=0 nChannel=0 nDirection=0 nTp=59 nMp=1 nSEQ=18 nBP=78 nMSGC=12 nMSGLP=0

nReturn=0 nChannel=0 nDirection=1 nTp=21 nMp=1 nSEQ=10 nBP=63 nMSGC=4 nMSGLP=0

nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=103306 bValid=1 nEftrMin=4294967295 nErrorFreeBits=0 nLeftr=0

nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=103306 bValid=1 nEftrMin=4294967295 nErrorFreeBits=0 nLeftr=0

nReturn=0 nData="5008 0000 0001 0102 "

nReturn=0 nChannel=0 nDirection=0 ActualDataRate=19686000 PreviousDataRate=18702000 ActualInterleaveDelay=800 ActualImpulseNoiseProtection=20 ActualNetDataRate=19686000 ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=20

nReturn=0 nChannel=0 nDirection=1 ActualDataRate=62932000 PreviousDataRate=62472000 ActualInterleaveDelay=700 ActualImpulseNoiseProtection=30 ActualNetDataRate=62932000 ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=30

Code: [Select]

TP-LINK(conf)#adsl show info

INDEX=1
{
enable=1
status=Up
modulationType=VDSL2
X_TPLINK_CurrSupportLinkType=2
lineEncoding=
allowedProfiles=
currentProfile=
dataPath=
interleaveDepth=0
lineNumber=0
upstreamCurrRate=19686
downstreamCurrRate=62932
upstreamMaxRate=19320
downstreamMaxRate=71975
upstreamNoiseMargin=59
downstreamNoiseMargin=55
upstreamAttenuation=83
downstreamAttenuation=103
upstreamPower=129
downstreamPower=-13
ATURVendor=
ATURCountry=
ATUCVendor=
ATUCCountry=
totalStart=533512
showtimeStart=409
quarterHourStart=0

Does everything seem in order here? To make a long story short I had the full 80mbit for over two years. I recently had lost 10mbit before moving to the TP-Link unit and by the time I had finished setting it up I had lost another 10mbit and my pings have gained 12ms. Interleaving? Can we tell if G.INP is working from my stats?

Yesterday I accidentally forced a reconnect after 5days of being connected with no drops etc. My downstream SNR was jumping between 6 and 6.1, not that it means much to me. I don't have any stats from when I was hitting the full 80mbit either.

Do any projects exist to log this useful info like I see for other devices, pretty graphs and such?

I hope I will slowly creep back up to at least 70mbit, how quickly would/should that happen?

Perhaps I should make a new thread?

edjonesy · « **Reply #57 on:** May 11, 2015, 09:04:43 AM »

Obviously there are no guarantees, but, since installing this beta firmware 8 days ago, my upstream speed has gone from 15mb to 19mb and my downstream from 53mb to 66mb, so it's all heading in the right direction for me. I've had no disconnects, uptime keeps going up and the WiFi is stable too.

Fo me, it's all good.

Device Information

Firmware Version:0.6.0 1.10 v0021.0 Build 150409 Rel.40749n

Hardware Version:TD-W9980 v1 00000000

System Up Time:8 day(s) 10:19:48

DSL

Line Status:Connected
DSL Modulation Type:VDSL2
Annex Type:Annex A/B/L/M

Upstream
Downstream
Current Rate (Kbps)
19000
66997
Max Rate (Kbps)
22913
70978
SNR Margin (dB)
8.6
7
Line Attenuation (dB)
18.1
15.4
Errors (Pkts)
0

Mooingall · « **Reply #58 on:** May 13, 2015, 06:21:45 PM »

Ohh does this confirm interleaving on my line?

Quote

nINTLVDEPTH=251
nINTLVDEPTH=933

Only twigged on when I saw someone mention "interleaving depth".

ejs · « **Reply #59 on:** May 13, 2015, 06:40:24 PM »

The bReTxEnable=0 indicates G.INP (a.k.a. ReTx) is not in use.

Are you connected to an ECI cabinet? If the output of this command contains IFTN, then that indicates an ECI cab.

Code: [Select]

/firmware/dsl_cpe_pipe.sh g997listrg 1
ECI cabs haven't had G.INP enabled yet, and when they it it sounds like they will only support G.INP on the downstream (the up to 80Mb part).

News:

Author Topic: TP-Link TD-W9980 & G.INP (Read 33667 times)

kitz

Re: TP-Link TD-W9980 & G.INP

jelv

Re: TP-Link TD-W9980 & G.INP

burakkucat

Re: TP-Link TD-W9980 & G.INP

kitz

Re: TP-Link TD-W9980 & G.INP

edjonesy

Re: TP-Link TD-W9980 & G.INP

rapid111111

Re: TP-Link TD-W9980 & G.INP

licquorice

Re: TP-Link TD-W9980 & G.INP

kitz

Re: TP-Link TD-W9980 & G.INP

licquorice

Re: TP-Link TD-W9980 & G.INP

hacktrix2006

Re: TP-Link TD-W9980 & G.INP

edjonesy

Re: TP-Link TD-W9980 & G.INP

Mooingall

Re: TP-Link TD-W9980 & G.INP

edjonesy

Re: TP-Link TD-W9980 & G.INP

Mooingall

Re: TP-Link TD-W9980 & G.INP

ejs

Re: TP-Link TD-W9980 & G.INP