Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Ragnarok on May 01, 2014, 06:41:43 PM
-
http://uk.tp-link.com/products/details/?model=TD-W9980B
Chipset unknown at the moment, fingers crossed it's a lantiq VDSL2/ADSL2+ chip as TP-link usually have a comprehensive statistics on their DSL status pages.
I believe here in the UK we require annex b compatibility though i'm not 100% sure on that.
----
Edited by admin to change topic title
-
A very similar TP-Link product (Archer D7) is on sale in Australia, and has a Broadcom chipset. See http://forums.whirlpool.net.au/archive/2234830
We use Annex A in the UK, by the way.
-
I believe here in the UK we require annex b compatibility though i'm not 100% sure on that
Its BT's Annex B Plan 998 ADE17-M2x-A Band Plan B8-11 in
BT SIN 498
http://www.sinet.bt.com/sinet/SINs/pdf/498v5p1.pdf
{corrected-link-address-}
-
Op's link not available; have they pulled it?!
-
Op's link not available; have they pulled it?!
Maybe this helps http://uk.tp-link.com/products/?categoryid=203
Looks like there will be 2 models, looks like in the UK, should you buy one when available, you should get the Annex A version.
----
admin note
Edited correct annex version for the UK to avoid confusion.
-
Same again!
-
Looks like there will be 2 models, looks like in the UK, should you buy one when available, you should get the B version.
Annex A is ADSL over PSTN (as used in the UK)
Annex B is ADSL over ISDN (as used in Germany)
-
http://uk.tp-link.com/products/details/?model=TD-W9980B
Chipset unknown at the moment, fingers crossed it's a lantiq VDSL2/ADSL2+ chip as TP-link usually have a comprehensive statistics on their DSL status pages.
Thank you for bringing that to our attention, at the current time the only VDSL2 modem that ticked all my boxes was the ZyXEL VMG8324 B10A, which looks like it may have a competitor.
Ive just fired off an email to a contact at TPlink to see if they have any more info, such as date, retail price and chipset. Unsure what they will say, but worth a shot as they owe me a favour.
-
b*cat purrs that both Eric and HighBeta are correct . . . but the interpretation of that Beattie SIN can cause confusion.
When considering a modem for use in the UK, one should always look for an Annex A device. (That is POTS and xDSL mode.)
A close look at Beattie's SIN 498 (http://www.sinet.bt.com/sinet/SINs/pdf/498v5p1.pdf) shows in Section 3.2.2 that
R.VDSL2.5 The modem shall support 17MHz operation using band plan B8-11 (i.e.
plan 998ADE17) as defined in Annex B of G.993.2 [3].
and in Section A.4.2.2.2 that
Description – The Modem shall support 17MHz operation using band plan B8-11 (i.e.
plan 998ADE17) as defined in Annex B of G.993.2 [3].
Those two mentions of "Annex B" are just pointers to the Annex so lettered of the third reference, which is
[3] | ITU-T G.993.2 | Very high speed Digital Subscriber Line | 2 Dec 2011
That document can be obtained via this link (https://www.itu.int/rec/T-REC-G.993.2/en). ;D
-
Ive heard back from TPLink (UK) and after confirmation with their HeadOffice "it appears that we can expect it to be on sale at the end of this calendar year." No information on pricing yet either.
-
For those awaiting release, it finally looks like soon could actually be soon.
Looks like there will be 2 models, looks like in the UK...
Rather than models, there will be a UK firmware version with quick start info for UK ISPs.... but even in its basic state it allows you to configure the Annex Type. I would assume that in the case of 'foreign' models it would be more important to check the pins on the power plug.
afaik.. TPlink modems have 'Multimode' for DSL modulation & annex whereby it should automatically pick up the correct annex setting. ;)
These however can be specified manually
DSL Modulation Type : Multimode
Annex Type : Annex A/B/L/M
DSL Modulation Type : VDSL2
Annex Type : Annex A/B/L/M
As with any other VDSL modem/router to manually configure for BToR FTTC would be to ensure that you select PPPoE and Enable VLAN and using the VID 101.
-
Tplink TD-W8980 crossflashed to TD-W9980. Both are the same hardware but 8980 doesn't have VDSL support in firmware.
Tested with a VDSL2 line ( GVT Brasil ) downstream 55Mb/s and upstream 6Mb/s. Profile 17a.
(https://www.mediafire.com/convkey/f537/bwbb2rs7pggs8h37g.jpg) (https://www.mediafire.com/view/?bwbb2rs7pggs8h3)
-
Thanks for that screen cap :)
Firmware Version 0.6.0 1.6v0021.0 Build 140613 Rel.50511n
Thats interesting - different firmware version for UK. Plus there will be a newer version before it goes on release.
Where did you get that FW from? afaik there may be some issues with 0.6.0 1.6
Out of interest, have they disabled telnet on that version?
Both are the same hardware but 8980 doesn't have VDSL support inf firmware.
In what way doesnt it support VDSL? You seem to be syncing fine.
Oops misunderstood. I think youre correct aside from a few tiny cosmetic changes.
-
TD-W8980 is sold as ADSL2+ wireless modem.
TD-W9980 is sold as VDSL2 wireless modem.
Original TD-W8980 firmware doesn't have VDSL2 support.
Firmware for TD-W9980: http://www.tp-link.com/resources/software/TD-W9980_V1_140613.zip
Telnet is enabled but with a very limited set of commands. I already used firmware modification kit to look at the filesystem.
-
Thanks for that link, I had looked on the (uk) site but couldnt see anything. :)
TD-W8980 is sold as ADSL2+ wireless modem.
TD-W9980 is sold as VDSL2 wireless modem.
Yep that was my conclusion too. Just stick a new plastic grey port socket in that says VDSL rather than ADSL.
-
Just seen your edit
Telnet is enabled but with a very limited set of commands.
Very limited :(
Access to the shell has also been removed
Welcome To Use TP-LINK COMMAND-LINE Interface Model.
-------------------------------------------------------
TP-LINK(conf)#sh
Command not found:sh
TP-LINK(conf)#shell
Command not found:shell
TP-LINK(conf)#SH
TP-LINK(conf)# <------------- indicating that the facility to enter the shell has been removed?
Highly disappointed that versions 0.6.0 1.7 and above has telnet access removed completely >:( >:( >:(
I already used firmware modification kit to look at the filesystem.
Good luck :)
-
Just seen your edit
Telnet is enabled but with a very limited set of commands.
Very limited :(
Access to the shell has also been removed
Welcome To Use TP-LINK COMMAND-LINE Interface Model.
-------------------------------------------------------
TP-LINK(conf)#sh
Command not found:sh
TP-LINK(conf)#shell
Command not found:shell
TP-LINK(conf)#SH
TP-LINK(conf)# <------------- indicating that the facility to enter the shell has been removed?
Highly disappointed that versions 0.6.0 1.7 and above has telnet access removed completely >:( >:( >:(
I already used firmware modification kit to look at the filesystem.
Good luck :)
telnetd is a link to busybox.
telnetd is invoked at /etc/init.d/rcS without any argument.
After google searching about telnetd and busybox found that syntax:
telnetd -l /bin/sh
Monday I will test to see if this syntax will help.
Forgot to mention that the FMK could reassemble a working firmware. I alter and include some text files and it flashed ok.
This device will be almost perfect if openvpn and ssh server could be included in the firmware.
-
Does echo $SHELL return anything?
-
Does echo $SHELL return anything?
Thanks Boost, TBH I didnt try that and I dont have the router on now to try it as Ive gone back to my Zyxel.
Aside from that, the firmware version now on... I cant even access telnet at all :(
I found something somewhere that indicated the command was #SH for the W8980.
I found it strange that any other command would return "Command not found". Yet if I used #SH it just totally ignored the command and went straight back to the prompt.
-
I doubt if the command was actually '#SH'. This is common Unix terminology for typing a command when logged in as root (that's what the # means). The command was probably 'SH'. If you type the # as well, the command is ignored - I expect it has some significance, but I don't recall offhand what it is. Remember also that Unix commands are case sensitive.
If you see a $ prompt (indicating an ordinary user), one thing you can try is to type 'su' (substitute user) which is the normal way to upgrade a user to root. If you're asked for a password, it will probably be the same password as you use for the first login.
-
If you type the # as well,
Sorry if I misled, I did type SH. The # is there as the command prompt. I also tried the lower case sh.
It was SH that was totally ignored and looped straight back to the command prompt. Other attempts at possible commands (such as sh) returned "Command not found".
Welcome To Use TP-LINK COMMAND-LINE Interface Model.
-------------------------------------------------------
TP-LINK(conf)#sh
Command not found:sh
TP-LINK(conf)#shell
Command not found:shell
TP-LINK(conf)#SH
TP-LINK(conf)#
I dont know if its co-incidence or not, but removing shell access could possibly be TPlinks response to the discovered tplink backdoor trojan that was discovered last year (http://www.dslreports.com/forum/r28102272-TP-Link-Routers-Contain-Treacherous-Backdoor). :(
-
Tested invoking telnetd with "telnetd -l /bin/sh" . First I kill the telnetd process ( kill -s 9 processnumber ).
Works and a telnet from my PC shows a console without authentication.
Now I'm looking how to put authentication back ...
-
If you type the # as well,
Sorry if I misled, I did type SH. The # is there as the command prompt. I also tried the lower case sh.
It was SH that was totally ignored and looped straight back to the command prompt. Other attempts at possible commands (such as sh) returned "Command not found".
Welcome To Use TP-LINK COMMAND-LINE Interface Model.
-------------------------------------------------------
TP-LINK(conf)#sh
Command not found:sh
TP-LINK(conf)#shell
Command not found:shell
TP-LINK(conf)#SH
TP-LINK(conf)#
I dont know if its co-incidence or not, but removing shell access could possibly be TPlinks response to the discovered tplink backdoor trojan that was discovered last year (http://www.dslreports.com/forum/r28102272-TP-Link-Routers-Contain-Treacherous-Backdoor). :(
I wonder if the shell 'sh' was renamed to 'SH' and you are simply reinvoking the shell each time? All sounds pretty bizarre.
Why lock the EU out? 90% don't care and the 10% that do will despise your product and/or brand.
-
I wonder if the shell 'sh' was renamed to 'SH' and you are simply reinvoking the shell each time?
That sounds very plausible. If this is the case, then the shell is still available but some of the useful commands have been removed.
-
I wonder if the shell 'sh' was renamed to 'SH' and you are simply reinvoking the shell each time?
That sounds very plausible. If this is the case, then the shell is still available but some of the useful commands have been removed.
sh is still present and usable. See my previous post.
Just change rcS file to run telnetd with -l /bin/sh .
-
To invoke a login screen in telnetd the syntax is :
telnetd -l /bin/login
-
Highly disappointed that versions 0.6.0 1.7 and above has telnet access removed completely
I registered my dismay on this a couple of weeks ago and Ive now been sent a new version that has telnet access enabled. :)
------
To invoke a login screen in telnetd the syntax is :
Code: [Select]
telnetd -l /bin/login
Sorry if Im being thick, but Im a windows users who knows little about linux cmds, so dont know how to proceed :-[ :(
-
Highly disappointed that versions 0.6.0 1.7 and above has telnet access removed completely
I registered my dismay on this a couple of weeks ago and Ive now been sent a new version that has telnet access enabled. :)
------
To invoke a login screen in telnetd the syntax is :
Code: [Select]
telnetd -l /bin/login
Sorry if Im being thick, but Im a windows users who knows little about linux cmds, so dont know how to proceed :-[ :(
I access the modem by TTL serial adapter conected to the header J7. ( user admin / password 1234 ).
I changed the way that telnetd is invoked.
The original rcS file calls telnetd without any parameters.
Changing the file to telnetd -l /bin/sh produces a root console via telnet without login screen.
Changing the file to telnetd -l /bin/login produces a sh console with classic login screen.
The changes was made using FMK.
Since the new Tplink firmwares for Lantiq are signed, the update page doesn't accept the files.
The changed firmware could only be flashed using U-BOOT + tftp.
http://wiki.openwrt.org/toh/tp-link/td-w8970
-
Cant make upgrade on 8970.... after tftp load... i try bootm and gets: lzma uncompress or overwrite error 1 must RESET board to recover... i see the adress is different ... normally it is 0x7a0000 and here is different...how to make it proper ??
and ideas ?
-
I access the modem by TTL serial adapter conected to the header J7.
Ahh thank you for the explanation. I think I'll pass on that :-[
-
i cant install software fom 9980 on my 8970..... after tftpboot....
VR9 # tftpboot 0x80800000 9980.image
Using vr9 Switch device
TFTP from server 192.168.2.100; our IP address is 192.168.2.1
Filename '9980.image'.
Load address: 0x80800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
################################################
done
Bytes transferred
bootm
and i get
Uncompressing Kernel Image ... LZMA: uncompress or overwrite error 1 - must RESET board to recover
-
i cant install software fom 9980 on my 8970..... after tftpboot....
Sorry I dont know anything about flashing the TD-W9980 firmware on to other models.
I notice your model is the 8970 which is a different model than the 8980 which zhadoom managed to upgrade.
The 8980 and 9980 are similar dual band routers and both badged N600. The 8970 isnt dual band, which could be why the firmware wont work on yours :-\
-
For those awaiting release, it finally looks like soon could actually be soon.
Should be on sale in the UK 18/09/2014. Expected retail price range £75 - £80
-
i cant install software fom 9980 on my 8970..... after tftpboot....
VR9 # tftpboot 0x80800000 9980.image
Using vr9 Switch device
TFTP from server 192.168.2.100; our IP address is 192.168.2.1
Filename '9980.image'.
Load address: 0x80800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
################################################
done
Bytes transferred
bootm
and i get
Uncompressing Kernel Image ... LZMA: uncompress or overwrite error 1 - must RESET board to recover
The firmware image from the file at Tplink website don't boot in memory ( bootm ) since it is assembled to run from flash.
Before flash you must stripe the U-Boot part of the file. dd is a linux command. Original.bin is the renamed original firmware from tplink. 9980.bin is the striped file ( without U-boot ).
dd if=original.bin of=9980.bin skip=257 bs=512
The striped file must be 7995392 ( 0x7a0000 ) bytes long.
http://www.mediafire.com/download/uzztekgcxx5175s/tplink9980.bin
Then you can flash the device ( all operations in U-Boot serial console )
tftpboot 0x80800000 9980.bin
sf erase 0x20000 0x7a0000
sf write 0x80800000 0x20000 0x7a0000
This firmware could work partially with TD-W8970 since the xdsl hardware is the same but the wireless chip was not.
All functions ( usb, media server, ftp etc ) could work except wifi.
-
For those awaiting release, it finally looks like soon could actually be soon.
Should be on sale in the UK 18/09/2014. Expected retail price range £75 - £80
I was told that the router is EOL (End of Life) in South Africa from the suppliers. This really does not make any sense considering you guys are only getting it later this month and TP Link do not have any other VDSL router to take it's place. ???
-
I was told that the router is EOL (End of Life) in South Africa from the suppliers. This really does not make any sense considering you guys are only getting it later this month and TP Link do not have any other VDSL router to take it's place. ???
Hi PsyClown and welcome :)
That certainly does seem rather strange. How long has it been available for in South Africa do you know?
-
As this router is now for sale at broadbandbuyer for £68.32, then I guess I can now release this
TP Link TD-W9980 - Review (http://www.kitz.co.uk/routers/tplink_TD-W9980_review.htm)
-
Mine is coming tomorrow as order today for next day delivery from broadbandbuyer.
Can't wait to check compare this router against BT Openreach Modem.
-
I put the TD-W9980 back on a couple of hours ago to check something... so may as well post these for comparison
These are my stats on the TD-W9980 - this is all the info I can get as telnet is blocked on this f/w version :(
ine Status:Connected
DSL Modulation Type:VDSL2
Annex Type:Annex A/B/L/M
Upstream Downstream
Current Rate (Kbps) 20000 79995
Max Rate (Kbps) 28369 82534
SNR Margin (dB) 9.8 6.7
Line Attenuation (dB) 16.2 16.4
Errors (Pkts) 0 0
This is from the Zyxel immediately before I put the TPlink on.
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 30373 Kbps, Downstream rate = 88710 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 8.1 12.7
Attn(dB): 0.0 0.0
Pwr(dBm): 14.2 6.1
BCM chipsets perform so much better on my line despite being on an ECI cab.
-
So, BT Openreach Modem is higher on Max Rate than the TP-Link TD-W9980. As for telnet as I do hate when company blocked it. There isn't much extra information on it, like the error count, interleaving etc.
Kitz what firmware was it on your TP-link W9980?
-
On my line yes. If you look on the review page the figures are side by side for the tplink and the Openreach modem.
The above figures are the tplink compared with my zyxel vmg8324-10a.... Which most people find gives them a higher sync/max attainable than the hg612 anyhow.
I can't recall the firmware version atm but it was a beta version. It should likely show though in one of the images on the review page.
-
You could try getting the FEC/HEC/CRC ES/SES counts out of the TD-W9980 via http in a similar way to what I posted here (http://forum.kitz.co.uk/index.php?topic=14377.0).
Alternatively, you should be able to spot some of them if you look in wireshark while accessing the router's web interface.
-
kitz - are the setting for VDSL2 are automatically itself? Or must enter some settings. As I cannot get VDSL2 working with plusnet FTTC?
What are the correct setting for FTTC Plusnet below:
Isp list: ADSL_BT
PVC: 0/38
Connection Type: PPPoE
Encapsulation Mode: VCMUX
L2 Interface Type: VDSL2
Enable Vlan: Enabled
VID: (1-4094): 101
PPPoE or PPPoA: PPPoE
with plusnet username and password and still won't work? Cannot get my head round it.
Edit: got it connected ok. My fault got wrong telephone cable into LAN port. Should be on DSL port. Silly me.
The max rate is bit lower on TP-Link than Openreach Modem.
TP-Link:
Line Status:Connected
DSL Modulation Type:VDSL2
Annex Type:Annex A
Upstream Downstream
Current Rate (Kbps) 19999 79995
Max Rate (Kbps) 33830 98787
SNR Margin (dB) 15 11.5
Line Attenuation (dB) 12.7 11.3
Errors (Pkts) 0 0
BT Openreach HG612:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 36672 Kbps, Downstream rate = 104316 Kbps
Path: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 13.2 23.0
Attn(dB): 0.0 0.0
Pwr(dBm): 12.5 -0.3
-
Hi, glad you sorted out what the problem was :)
The max rate is bit lower on TP-Link than Openreach Modem.
Upstream rate = 36672 Kbps, Downstream rate = 104316 Kbps
-v-
Max Rate (Kbps) 33519 97876
Thats quite a bit :(
-
You could try getting the FEC/HEC/CRC ES/SES counts out of the TD-W9980 via http in a similar way to what I posted here (http://forum.kitz.co.uk/index.php?topic=14377.0).
Alternatively, you should be able to spot some of them if you look in wireshark while accessing the router's web interface.
Thank you ejs, I'll try having a look a go at that when I get a mo :)
-
kitz - are the setting for VDSL2 are automatically itself? Or must enter some settings. As I cannot get VDSL2 working with plusnet FTTC?
What are the correct setting for FTTC Plusnet below:
Isp list: ADSL_BT
PVC: 0/38
Connection Type: PPPoE
Encapsulation Mode: VCMUX
L2 Interface Type: VDSL2
Enable Vlan: Enabled
VID: (1-4094): 101
PPPoE or PPPoA: PPPoE
with plusnet username and password and still won't work? Cannot get my head round it.
>>> Isp list: ADSL_BT
Hmmm disappointed - you seem to have an older firmware version. :( The shipping out version is supposed to have VDSL options and specifically VDSL_Plusnet. afaik the new UK firmware is why they were waiting for the release 'any time soon'. Im wondering if broadbandbuyer being the first to have these still have the old firmware.. and if so... being as you are on a short line, watch your SNRm closely.
-----
PS - How to set up the TP-Link TD-W9980 for VDSL (http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup)
-
My firmware below as I select ADSL_Plusnet but it won't let connected to plusnet gateway. Have to choose Other and select VID 101 as they should add VDSL_Plusnet in the first place!
Anyway I cannot get Broadband Quality Monitor as it not response icmp. Do u have any idea how to enable it?
-
Updated: I have managed to get Broadband Quality Monitor as it now response icmp!
Do the follow setting:
1) log on 192.168.1.1 and enter your username and password to log in
2) on the left side panel, go to system tools
3) on the system tools, click manage control
4) tick the box Enable on the remote management with port 80 and tick the box ICMP(ping) Remote and click save!
-
New firmware for TD-W9980.
http://www.tplink.com/resources/software/TD-W9980_V1_140819.rar
-
New firmware for TD-W9980.
http://www.tplink.com/resources/software/TD-W9980_V1_140819.rar
I already got that! My firmware is: Firmware version: 0.6.0 1.7 v0021.0 Build 140819 Rel.50339n
Software firmware - 0.6.0_1.7_up_boot(140819)_2014-08-19_14.15.39
-
Have to choose Other and select VID 101 as they should add VDSL_Plusnet in the first place!
Hence my assumption that you have an older firmware version. The newer ones are supposed to have the UK VDSL info in (I supplied a list for them)
If you need to connect using 'other' then you can follow my guide I posted yesterday
http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup
I cannot get Broadband Quality Monitor as it not response icmp.
See the guide - How to enable ICMP on the TD- W9980 (http://wiki.kitz.co.uk/index.php/TD-W9980_System_Tools#Manage_Control)
-
kitz can you please post screenshot firmware so I can check if it matched?
-
I already got that! TD-W9980_V1_140819
Thats the same version I have - which is supposedly the pre-release version ???
I was told that there would be a new version which includes all the VDSL information and I would get sent a copy as soon as it was available. :-\
-
I had the same version as you. I use this following step what u did here: http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup#Select_ISP but when I select ISP. It say ADSL_Plusnet as it no good because L2 Interface Type / VID setting is missing. So, I choose Other instead and it worked.
I wish the VDSL status are addition: INP, CRC, HEC, ES, and FEC and WAN connection time. I did try DSLstats v 5.0.2 but it won't work. :(
-
I already got that! TD-W9980_V1_140819
Thats the same version I have - which is supposedly the pre-release version ???
I was told that there would be a new version which includes all the VDSL information and I would get sent a copy as soon as it was available. :-\
My first test with 8980@9980 uses TD-W9980v1_0.6.0_1.6_up_boot(140613)_2014-06-13_14.14.54.bin firmware. This is older than the yesterday published TD-W9980v1_0.6.0_1.7_up_boot(140819)_2014-08-19_14.15.39.bin .
-
The VDSL information is pretty less! Overall disappointed. It only showing current rate, max rate, snr margin, line attenuation and that was it. TP-Link should have addition features like this INP, CRC, HEC, ES, and FEC Errors and WAN ongoing connection time.
-
I had the same version as you. I use this following step what u did here: http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup#Select_ISP but when I select ISP. It say ADSL_Plusnet as it no good because L2 Interface Type / VID setting is missing. So, I choose Other instead and it worked.
No . Look again - You can see I selected "others" in that set-up guide and I show where to put in the VID.
As I keep saying its only newer version software that will have VDSL_Plusnet. ADSL_Plusnet wont work because thats for ADSL
I will edit it to clarify, but its only because I was told the new f/w would contain this info that I'm surprised. Theyve had the info for weeks. :(
I wish the VDSL status are addition: INP, CRC, HEC, ES, and FEC and WAN connection time.
Yep an so do I - if you read the review you can see Im very disappointed too.
I did try DSLstats v 5.0.2 but it won't work. :(
No it wont - The router contains a Lantiq chipset.
DSLstats only works on Broadcom based routers.
Aside from the overwhelming fact that if I cant get into the CLI, then DSLstats isnt going to be able to get in there either to magic up the figures . :(
-
You could try getting the FEC/HEC/CRC ES/SES counts out of the TD-W9980 via http in a similar way to what I posted here (http://forum.kitz.co.uk/index.php?topic=14377.0).
Alternatively, you should be able to spot some of them if you look in wireshark while accessing the router's web interface.
Thank you ejs, I'll try having a look a go at that when I get a mo :)
Thank you ejs. Ive just had a bit of time to play. Ive posted in the other thread, but thought it may also be worthy posting in here that Ive sucessfully been able to get the following info from wireshark, but thats as far as Ive been able to go on that front.
134
[1,0,0,0,0,0]0
status=Up
modulationType=VDSL2
X_TPLINK_AdslModulationCfg=Multimode
upstreamCurrRate=20000
downstreamCurrRate=79995
X_TPLINK_AnnexType=Annex A/B/L/M
upstreamMaxRate=28292
downstreamMaxRate=82665
upstreamNoiseMargin=98
downstreamNoiseMargin=66
upstreamAttenuation=162
downstreamAttenuation=164
b1
[2,0,0,0,0,0]1
ATUCCRCErrors=70
CRCErrors=619
ATUCFECErrors=1305
FECErrors=12809
severelyErroredSecs=0
X_TPLINK_US_SeverelyErroredSecs=0
erroredSecs=0
X_TPLINK_US_ErroredSecs=0
b1
[3,0,0,0,0,0]1
ATUCCRCErrors=70
CRCErrors=619
ATUCFECErrors=1305
FECErrors=12809
severelyErroredSecs=0
X_TPLINK_US_SeverelyErroredSecs=0
erroredSecs=0
X_TPLINK_US_ErroredSecs=0
-
I know that adslmax is duplicating some of the info over on the plusnet forums, but to save me logging in there and in order to keep everything in this one thread..
I thought that ejs and zhadoom may be interested in some other info Ive been able to spy whilst playing with an older firmware version
VRX - 200 <---- Chipset?
Vectoring:off, Bonding On/off: Not available, SRA <---- suggesting that although I cant see anything in the current format, that is not to say that further firmwares may support these features?
US nb of bands:2
DS nb of bands:3
USO Yes/No: Not available
Profil: 17a
Putting into pbParams speak, Suggesting Im using bands U1, U2, D1, D2 & D3 but not U0?
Via my usual router, I normally have very little bitloading in this band as it is heavily shaped by PSD masks. Ive just referred back and U0 covers tones 12-31 with a grand total of 119 bits loaded.
-
@adslmax
Have you tried to telnet into the router?
The only reason I ask, is that it allowed me access just after I'd upgraded the firmware. But hasnt since.
-
@adslmax
Have you tried to telnet into the router?
The only reason I ask, is that it allowed me access just after I'd upgraded the firmware. But hasnt since.
No telnet won't work.
-
I am going to fired away email TP Link and ask them to add features on the VDSL router below:
Enabled for telnet
Wan connection (how long connected online)
INP (interleaving), CRC, HEC, ES, and FEC errors stats
-
Wan connection (how long connected online)
Make sure you separate that from System UpTime which can be found on the Status Page.
You should also request that access via telnet should give you SNRm per tone and bitloading. I know this information should be easy for them to get.
I feel there is a lot more info that should be available. Theres tons of VDSL information that isnt :(
-
Look what I have :clap:
Welcome To Use TP-LINK COMMAND-LINE Interface Model.
------------------------------------------------------------------------
TP-LINK(conf)#help
normal mode commands:
clear --- clear screen
exit --- leave to the privious mode
help --- help info
history --- show histroy commands
logout --- logout cli model
config mode commands:
config --- enter config mode
adsl --- config adsl
igmp --- igmp config
wan --- wan config
wlctl --- wireless config
lan --- lan config
dev --- device control
TP-LINK(conf)#
Very limited but better than nothing
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=20000
downstreamCurrRate=79995
upstreamMaxRate=28484
downstreamMaxRate=82936
upstreamNoiseMargin=99
downstreamNoiseMargin=66
upstreamAttenuation=162
downstreamAttenuation=164
upstreamPower=143
downstreamPower=42
ATURVendor=
ATURCountry=
ATUCVendor=
ATUCCountry=
totalStart=229251
showtimeStart=537
quarterHourStart=0
X_TPLINK_Bitswap=On
X_TPLINK_SRA=On
X_TPLINK_AdslModulationCfg=Multimode
X_TPLINK_AnnexType=Annex A/B/L/M
X_TPLINK_SupportAdslMode=VDSL2:A,B,A/B;T1.413:A;G.dmt:A;ADSL2:A,A/L/M;ADSL
,A/L/M;Auto Sync-up:A/B/L/M
X_TPLINK_PtmMainIfName=ptm0
}
cmd:SUCC
TP-LINK(conf)#
LAN port 2
-
Am I dreaming? Can't believe this VDSL router are the best quality look here: The Broadband Quality Monitor with low ping http://www.thinkbroadband.com/ping/share/e25b09a2afe76bdc9ff6372a1923e701.html
-
Am I dreaming? Can't believe this VDSL router are the best quality look here: The Broadband Quality Monitor with low ping http://www.thinkbroadband.com/ping/share/e25b09a2afe76bdc9ff6372a1923e701.html
I cant see how your router could affect latency - thats more to do with your routing, and traffic between the exchange and packet destination... and of course your ISP's gateway. You can check latency by doing a tracert.
That said I too have got brilliant routing (and my best ever) atm.
C:\Users\kitz>tracert www.kitz.co.uk
Tracing route to kitz.co.uk [185.24.98.37]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 11 ms lo0.12.central12.ptw-bng01.plus.net [195.166.128.172]
3 11 ms 11 ms 10 ms irb.12.ptw-cr02.plus.net [84.93.249.34]
4 12 ms 12 ms 12 ms 195.66.237.228
5 12 ms 13 ms 13 ms switch-004.sl5.misp.co.uk [91.198.165.76]
6 12 ms 12 ms 12 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Trace complete.
This has only happened in the past few days. I certainly didnt notice it before and Ive been testing the TD-W9980 on and off for a few months now. Routing via ptw-bng01 seems pretty good, and also implies something has happened on the backhaul between my exchange/Preston/Manchester/London. I therefore wonder if its anything to do with this (http://forum.kitz.co.uk/index.php?topic=14412.0)
-
Update
Ive been saying to TP-Link for several weeks that the lack of line statistics on this router lets it down :(
As agreed, I wasnt able to release a review until the product was actually for available in the UK. I was under the impression that the TP-link TD-W9980 would be available for sale in the UK from 18th of Sept, but I noticed on the 10th Sept broadband buyer was making these units available so I released my review on the same day TP-Link TD-W9980 Review (http://www.kitz.co.uk/routers/tplink_TD-W9980_review.htm).
TP-Link weren't aware of what I was going to post as the review is entirely independent and based on my own opinion.
Some line stats are available but none of the VDSL diagnostic data is available. This is very disappointing as the information is available from the chipset. I feel TP Link have missed a trick here by not including this information.
Today I got an email from TP-link saying they are going to review this and are looking at adding some further VDSL diagnostic parameters.
I will be corresponding with them direct with my suggestions. Not sure how much notice they will take, but its looking like there will at least be some of the more basic parameters available in a future firmware release. :fingers:
Thought people may like to be aware of this.
-
In the meantime
- Ive posted in this thread how you can now access the CLI via telnet to get some basic stats.
- ejs has kindly written a small java program that allows you to access some further stats. - Getting further stats from the TP-Link TD-W9980 (http://forum.kitz.co.uk/index.php?topic=14377.0)
-
Mine TP Link TD-W9980 already go back to broadbandbuyer and got full refunded today. They only offer me minus -10% refunded. Cheek of them! Overall disappointed with TP-Link with not good on VDSL, cause more errors on the line.
-
This is to do with the chipset. You, like me have a shortish run to the cab.. in which case the Broadcom chipsets seem to time and time again out-perform. The Lantiqs seem to fair quite well and be favoured by those with longer lines, but they aint too hot for some short lines.
Its one of those things that you never can really tell how its going to work until you have it set up on your line. :(
Its also why some people on here prefer to use the BT supplied ECI modem (lantiq) and some prefer the BT supplied Huawei (BCM)
-
Hey folks!
Got a TD-W9980 here and it's working pretty good on our very poor VDSL line (2.2km length by road says the kitz ADSL checker), although I could not get a working connection when the mode was set to A/B it had to be set to use just A, I'm not sure why it would not work in A/B mode, it managed to get a connection but nothing would load, it also sync'd slower.
Current Rate (Kbps) 4833 22084
Max Rate (Kbps) 4793 25763
SNR Margin (dB) 6.4 6.1
Line Attenuation (dB) 31.5 27
Errors (Pkts) 0 0
Although from the logs it has dropped a few times.
1 2014-09-16 15:58:31 DSL Notice xDSL Enter Showtime!!
2 2014-09-16 15:58:30 DSL Notice xDSL Leave Showtime!!
3 2014-09-16 07:29:23 DSL Notice xDSL Enter Showtime!!
4 2014-09-16 07:29:02 DSL Notice xDSL Training!!
5 2014-09-16 07:29:00 DSL Notice xDSL Handshake!!
6 2014-09-16 07:28:56 DSL Notice xDSL Ready!!
7 2014-09-16 07:28:52 DSL Notice xDSL Leave Showtime!!
8 2014-09-16 07:28:49 DSL Notice xDSL Leave Showtime!!
When it has dropped it'll leave/train/enter showtime most of the time but it will sometimes just leave and enter again without training etc, is this normal?
Both the ECI and Huawei performed OK on our line, I'd even reflashed the Huawei for linestats but we had a problem on our line and the BT Engineer swapped it out for the ECI (no idea why ~ it worked fine, our line was just screwed up), I guess I shouldn't have shown him the linestats page! :lol:
Overall it's a great little modem/router - just a shame it doesn't support the JetDirect Protocol for printers but instead you have to use some crappy app that's Windows only!
I can't wait for Openwrt to add support for it (I assume they will add support seeing as they've got it running on a TD-W8970 :angel:).
-
Hi mpmc and welcome to the forums.
Thank you for adding your comments.
I could not get a working connection when the mode was set to A/B it had to be set to use just A, I'm not sure why it would not work in A/B mode,
Which setting was that, is that the Annex? Sorry I dont have the TPlink on atm so I cant check.
The following steps are how I set the connection up and I dont recall having to set the annex as by default it went into multi-mode, which should auto-detect the correct annex mode.
http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup
it also sync'd slower.
How much? With your line being longer I would have hoped that the lantiq chipset may have been of some benefit. If its not performing as well on the longer lines then it would suggest that broadcom chipsets still have the edge. Your observations would certainly be of interest.
This is a tricky area because the lantiq/broadcom chipset preference is one that many will debate. I make no bones that the BCMs always seem to work best on my own line and I prefer them.. but some others on longer lines seem to prefer lantiq.
I guess I shouldn't have shown him the linestats page!
Damn! :( Unless you can pick up another cheap on ebay.
-
Hi mpmc and welcome to the forums.
Thank you for adding your comments.
I could not get a working connection when the mode was set to A/B it had to be set to use just A, I'm not sure why it would not work in A/B mode,
Which setting was that, is that the Annex? Sorry I dont have the TPlink on atm so I cant check.
The following steps are how I set the connection up and I dont recall having to set the annex as by default it went into multi-mode, which should auto-detect the correct annex mode.
http://wiki.kitz.co.uk/index.php/TD-W9980_QuickSetup
it also sync'd slower.
How much? With your line being longer I would have hoped that the lantiq chipset may have been of some benefit. If its not performing as well on the longer lines then it would suggest that broadcom chipsets still have the edge. Your observations would certainly be of interest.
This is a tricky area because the lantiq/broadcom chipset preference is one that many will debate. I make no bones that the BCMs always seem to work best on my own line and I prefer them.. but some others on longer lines seem to prefer lantiq.
I guess I shouldn't have shown him the linestats page!
Damn! :( Unless you can pick up another cheap on ebay.
Sorry I should have been a bit clearer :) I set it up exactly as your wiki link at first and it connected under Annex A/B mode and obtained an IP address but it refused to load anything. (this is where it sync'd slower). So I tried again in just Annex A mode and it just worked, it sync'd at about the same as the ECI modem it replaced (judging from the speedtest results.)
-
Ahh.. thank you for clarifying that. Sorry if Id misinterpreted what you meant :)
it sync'd at about the same as the ECI modem it replaced
Which isnt too much of a surprise.
Its extremely likely that it contains the same Lantiq chipset as the TD-W8980 and ECI modem which is a VRX 268 (http://www.lantiq.com/uploads/media//Lantiq_XWAY-VRX268_Product-Brief_02.pdf)
The only definite info I do have is that the TD-W9980 identifies itself as containing one of the "VRX-200" series chipsets.
-
I came across this thread following Kitz's "Combined VDSL2 Modem Routers" list. I'm presently using a TP-Link TL-WDR3600 along with an ECI modem, and the connection is very stable, but slower than the estimates, due to interleaving being on high (I was previously running on an unlocked HG612).
I see from earlier posts that it should be possible to flash a TD-W8980 with the TD-W9980 firmware - is there an idiot's guide anywhere, or is it simply a question of downloading the firmware and using the router's built-in firmware upgrade tool to load it on? I just happen to have a TD-W8980 sitting here gathering dust, so would be happy to give it a try, especially as the copper portion of my line is fairly long - my line is synching at around 55Mb/15Mb.
-
vs1 kindly gave instructions How to crossflash the TP-Link TD-W8980 to a TD-W9980 (http://forum.kitz.co.uk/index.php?topic=14461.0).
Good luck :)
-
Thanks for that - I could probably do that, and may come back to it some time in the future, but there's little hope that if I don't spend the time I haven't got to do it properly, I'll probably end up bricking it. So, stick with the two boxes for now.
I may buy a TD-W9980 in the not too distant future. 8)
-
I have successfully installed a W9980 such that I can access the internet, but I am struggling with port forwarding. I believe I have set it up properly (I use other TP-Link routers with the same basic firmware and do port forwarding no problem). Can anyone give me a pointer to what I might be doing wrong ?
-
Panic over. My ip address had changed.
-
Hi, first i don't have the 9980 yet but there is a new firmware out TD-W9980_V1_140925, not clear what is the fix
One question please
The draytek 2760 which use the same Lantiq chipset they have add an snr tweak value (for adsl & vdsl - here my test but with adsl line)
http://i1167.photobucket.com/albums/q631/babis3g/2760Dsnrchangesuccess_zpsffa68a47.png
... any one knows if will be added to the 9980? i am very sure the chipset can be tweaked (like other Lantiq based netgear dgn 3500, draytek 2760, some Lantiq friztboxes such 3390 etc) ... but will tp link add it?
So anyone is in touch with tp link can get any info for it? Thanks
-
Picked up a few tips of getting my W9980 here, I was thrown for some time by BT using a generic login on the Home Hub 5 with no password. I want to change from the Home Hub 5 because it crashes every time that I connect a Windows 8 PC.
Just to get the YouView box working with the W9980 now.
-
Hi, first i don't have the 9980 yet but there is a new firmware out TD-W9980_V1_140925, not clear what is the fix
One question please
The draytek 2760 which use the same Lantiq chipset they have add an snr tweak value (for adsl & vdsl - here my test but with adsl line)
http://i1167.photobucket.com/albums/q631/babis3g/2760Dsnrchangesuccess_zpsffa68a47.png
... any one knows if will be added to the 9980? i am very sure the chipset can be tweaked (like other Lantiq based netgear dgn 3500, draytek 2760, some Lantiq friztboxes such 3390 etc) ... but will tp link add it?
So anyone is in touch with tp link can get any info for it? Thanks
Im still trying to get them to add decent line stats that outputs vdsl SNRm bands and proper CLI access. They are supposed to be reviewing it, but I havent heard anything recently. Until we get proper line stats for this router and proper CLI access then the tweak is going to be impossible. :(
-
I take it that the TD-W9980 or TD-W8980 doesn't support SRM tweaking? Currently using a Billion 7800N which is Ok but i am looking to get another router ready just case it plays up. I am on a long Aluminium line (Line Attenuation(Upstream) 26.9
Line Attenuation(Downstream) 43.0) Would this router work well.
I can get the TD-W8980 easy enough and looking at the Open_WRT site for Serial it seems it will be easy enough to solder a pin header on unless there is something on the back of the PCB where the Serial header is should i upgrade from ADSL2+ to VDSL.
Any reviews on this would be nice.
-
I take it that the TD-W9980 or TD-W8980 doesn't support SRM tweaking?
No. The CLI is very limited and practically useless. :(
I dont know about the Open_WRT firmware though.
I am on a long Aluminium line (Line Attenuation(Upstream) 26.9
Line Attenuation(Downstream) 43.0) Would this router work well.
All lines differ and some routers work better on some lines than on others. The chipset is the same as on the BT HH5 and the BToR ECI modem so that may give you some indication. Personally I think you'd be better with a Broadcom chipset based router (http://wiki.kitz.co.uk/index.php/BCM_routers)
Any reviews on this would be nice.
TP-Link TD-W9980 review (http://www.kitz.co.uk/routers/tplink_TD-W9980_review.htm)
Theres some stats on there comparing it to the HG612 which has the same chipset as your existing router.
Also TP-Link TD-W9980 information (http://wiki.kitz.co.uk/index.php/TPLink_TD-W9980)
I started to give information on the WebGUI, but unfortunately Ive now taken it off my line.
I recently got hit by a bad crosstalk disturber and the only router which will now give me the full 80/20 sync is my Zyxel VMG8324 (http://www.kitz.co.uk/routers/zyxel_VMG8324-B10A_review.htm). :(
DSL chipsets:-
BCM 6358 = Billion 7800N / Huawei HG612
BCM 63168 = Zyxel VMG8324 / Billion 8800NL
Lantiq VRX-268 = ECI modem / HomeHub5 / TP-Link TD-W9980/8980
-
Thanks for the reply @kitz, The BT Home Hub 3a was ok on this line and the Exchange is on TSTC:0x0510 / v0x0510 according to dslstats.
SNR Tweaking is not that important to me currently just want a stable router, with an option of VDSL when the FTTC cabs goes live in my area.
-
The TPlink is stable and because it performs to the same standard as the ECI modem, then I class it as a good buy for the money. The GUI is quite nice..
....but if you want a router that is going to be able to do the under the hood stuff or want detailed line stats.. or want to push your line to its limits then its not the router for you and you'd perhaps be best sticking with a BCM.
For future proofing for vdsl and if you are techie, then IMHO it would have to be one of the following: HG612 (modem only), Billion or Zyxel
-
PS
Should have added a link to this page which lists the current available vdsl modem routers available for purchase in the UK.
http://forum.kitz.co.uk/index.php?topic=14436.0
-
Thanks for the reply @kitz, I will sticking stock GUI. Details stats i see no point in as ISP's ignore them. So tomorrow i shell go pick up a TD-8980 and when FTTC comes live i will use my TTL cable to cross flash it with the 9980 firmware.
-
Thanks for the reply @kitz, I will sticking stock GUI. Details stats i see no point in as ISP's ignore them. So tomorrow i shell go pick up a TD-8980 and when FTTC comes live i will use my TTL cable to cross flash it with the 9980 firmware.
Woaaaaah. Ive just seen your other thread about packet loss. I havent responded to it yet, but I will in a bit.
Big warning you wont be able to use anything like DSLstats with the TD-W9980. You need a router with a BCM chipset to be able to get diagnostics.
-
Currently using the Router TD-W8980, so far a great router however there is a few firmware issues (Currently on the latest) i have noticed. I have CWMP disabled yet the port is still open and looking on the TP-Link forums this has been a issue since 2013.
The other issue i have noticed is that PPPoA doesn't have NAT but PPPoE does which i find strange as all the other routers i have had has a NAT option so it does seem strange.
I have also found that the Remote Management option even disabled is still accessible.
So there seems to be some security concerns. If you haven't already make sure for now that you setup a firewall rule to block access to the default CWMP port which is 7547 and change the username and password in the CWMP area even if its off. Then change the URL to https:\\127.0.0.1 . On top of this disable Connection Request Authentication by unchecking the box.
Thought i'd give everyone a heads up on this issue.
If you want to test it use the following http://router_wan_ip:7547/tr069 default pass is the same as username which is admin.
-
I'm using a TD-W9980, and even blocking port 7547, and changing both the username, password etc, I still get "Connection Request OK" from http://router_wan_ip:7547/tr069
Will I need to reboot the router or something? There's no suggestion it's required when clicking "Save" after making the changes.
-
Have you checked the external IP, not the internal one. It works still on Internal IP for me but not via the external IP which is what it is ment to do.
-
It's the external IP I am checking - I'm on a fixed IP, so going to http://80.nnn.nn.nnn:7547/tr069 gives me "Connection Request OK".
-
Wonder if there is a direct route to contact TP-Link this TR069 issue is over a year old it seems strange it hasn't been patched out by now.
-
Perhaps try checking from an external location by using http://canyouseeme.org/ in case it's doing nat loopback or something like that, and you're not really accessing the external IP.
-
Good point, @ejs - I did wonder about that. I'll test it from work if I get the chance tomorrow.
[ETA.]
canyouseeme.org gives Error: I could not see your service on 80.nnn.nn.nnn on port (7547)
Reason: Connection timed out
-
Hi all,
I have a 9980 but I can't manage to connect it to my Sky Fiber. Can anyone help me?
thanks!
-
New firmware for TD-W9980 at Tplink website.
http://www.tplink.com/resources/software/TD-W9980_V1_141215.zip
New Features/Enhancement：
(1)Added some new ISP information.
(2)Improved the compatibility with ISP OTE in Greece.
Bug Fixed：
(1)Fixed the bug that sometimes Youview can't be played in UK.
(2)Fixed the bug that Internet can't work normally when PPP password was blank.
(3)Fixed the bug that Diagnostic page may not be shown correctly sometimes.
-
New firmware for TD-W9980 at Tplink website.
http://www.tplink.com/resources/software/TD-W9980_V1_141215.zip
New Features/Enhancement：
(1)Added some new ISP information.
(2)Improved the compatibility with ISP OTE in Greece.
Bug Fixed：
(1)Fixed the bug that sometimes Youview can't be played in UK.
(2)Fixed the bug that Internet can't work normally when PPP password was blank.
(3)Fixed the bug that Diagnostic page may not be shown correctly sometimes.
Flashed today and so far all is well. The diag page works now at least.
I'm waiting for the openwrt guys release a firmware for it now..
-
I picked up a TD-W8980 and used vs1 and zadoom's info provided http://forum.kitz.co.uk/index.php?topic=14461.0 (http://forum.kitz.co.uk/index.php?topic=14461.0) to cross flash to a W9980.
I bought it from a stationary retailer (Begins with S and you use them to staple paper togeather) in the UK delivered for £49.99 (dont forget your quidco)
I had a shock when I went to install it on Friday and couldn't get it to PPOE to my ISP, turned out they were having authentication issues and had to wait for them to resolve the issue :)
Imp
-
Wondering if someone can shed some light on whether I need to worry about some advanced settings for the W9980 in a BT Infinity environment please ?
I put this in about a week ago to replace a BT Homehub 5 that had just started an endless cycle of rebooting (cycling between blue/green/amber flashing lights). Anyway, I downloaded the latest firmware, and used the Quick Setup for a BT install as per guidance. It all works but since I connected it all up my sync speed has gradually slowed down from 80Mbps to 40 and upload has gone down to about a third of what it was to 8Mbps.
To be honest, the slowdown started before I got the new router (it started when the HH5 started going loopy - about 5 days before I put in the TP-Link) but I thought the slow-down would have stopped and started to recover to what it used to be as I've "fixed" the router issue ????
BT is coming to check things out but before they do (and before I get charged for it being the fault of a poorly configured router), anyone have any idea what might be going on ? I've seen some discussions about SRA and Bit Swapping and Annex's. Should SRA and BitSwapping be On or Off ? (I've tried both - currently both off). And it's set up for "Annex A/B/L/M". Is that correct ? I've attached screenshots of my settings and status. Would REALLY appreciate any insight you might have please...
-
Bit swap and SRA should both be enabled. Bit swapping is such a basic feature of ADSL nevermind VDSL2, that I think it would be very unusual for there to be a need to disable that. I expect the Annex A/B/L/M setting is fine.
I don't know why TP-Link don't enable that "SPI Firewall" by default. A statefull firewall is a pretty basic feature of a router, it seems like such a glaring omission if it really doesn't have a proper firewall by default.
-
Agreed. Bitswap should definitely be On. SRA doesn't work yet so doesn't matter but On won't hurt.
Turn Bitswap on and do a resync.
-
Thanks very much ! So whatever else is wrong is likely on the line or at least BT's problem ! I can call them out with confidence :-) Cheers....
-
have just installed a W9980, very impressed, everything works pretty nice
but one thing that worries me a little is if Vectoring is going to be added to the firmware by TP-Link anytime soon ??
http://www.ispreview.co.uk/index.php/2014/08/bt-start-uk-phase-2-vectoring-trials-boost-fibre-broadband-speeds.html
-
The 141215 9980 firmware contains dsl_cpe_control version 4.16.6-pa1 with vectoring related commands, which it refers to as dsm - Digital Spectrum Management.
dsmcg DSM_ConfigGet
dsmcs DSM_ConfigSet
dsmsg DSM_StatusGet
dsmstatg DSM_STATisticsGet
dsmmcg DSM_MacConfigGet
dsmmcs DSM_MacConfigSet
I can't tell if it's actually enabled since I don't have a 9980.
-
that seems a positive step in the right direction
as does this snippet
the second phase (Summer 2014) of Openreach’s Vectoring trial will once again focus on the same three street cabinets [26, 41 and 42] in Barnet (London) and these three [12, 39 and 74] in Braintree (Essex)
I wonder when the third phase will ??
anybody have more info on the Vectoring trials, six cabinets seems a bit tentative to me ?
-
I don't know where the information about the 100 cabinet vectoring trial (http://forum.kitz.co.uk/index.php?topic=14968.0) came from, but the R2850 EIP3 PDF from this openreach page (http://www.openreach.co.uk/orpg/home/updates/eipcommunications/eipcommunications.do) refers to "the pilot of vectoring in Q4 across 100 DSLAMs".
-
I found the reference to the 100 cabs
http://www.thinkbroadband.com/news/6811-openreach-vectoring-trial-to-expand-to-100-cabinets.html
looks like it is still early days for UK nationwide roll out - but a good start none the less :-)
-
The 141215 9980 firmware contains dsl_cpe_control version 4.16.6-pa1 with vectoring related commands, which it refers to as dsm - Digital Spectrum Management.
dsmcg DSM_ConfigGet
dsmcs DSM_ConfigSet
dsmsg DSM_StatusGet
dsmstatg DSM_STATisticsGet
dsmmcg DSM_MacConfigGet
dsmmcs DSM_MacConfigSet
I can't tell if it's actually enabled since I don't have a 9980.
What about G.inp does it support it or not ?
-
@ tommy45
I asked the G.INP and vectoring question of TP-Link support, and got the following reply:
This 9980 supports G.INP while not for the G.vector. And the G.vector feature will be add in the second quarter, the exact time can't confirm.
I've had the symptom of G.INP significantly dropping my synch rate, and that is an indication to me that TP-Link support don't actually have a clue...
-
Ive just had a look on the box which lists all the ITU specifications (http://wiki.kitz.co.uk/index.php/TPLink_TD-W9980#TD-W9980_Technical_Specifications) and theres no mention of G.998.4... nor is there on their site. :(
-
Yeah, I think it's time for a new router. Google, here I come... :fingers:
-
Ive just had a look on the box which lists all the ITU specifications (http://wiki.kitz.co.uk/index.php/TPLink_TD-W9980#TD-W9980_Technical_Specifications) and theres no mention of G.998.4... nor is there on their site. :(
so it's looking like the fritz with the lantiq chip is the only one that does support G.inp and vectoring
-
I can't see any reason why it shouldn't be supported, even the older dsl driver version has ReTx stuff. Unfortunately, without hacking into your own router, you've got no way of determining if it's enabled or not.
-
I've had the symptom of G.INP significantly dropping my synch rate
Me too, I've always had full 80/20 sync as my line is very short, but the last few weeks my sync rate has dropped and the ping time increased, even though there are no errors reported and the obtainable rate is still the same.
My Openreach modem is an ECI and seems to connect at the same lower speed as the 9980. I'm just waiting to borrow a friends unlocked Huawei so I can see if G.INP is enabled on my line.
-
I've just made a post about the TD-W9980 in the G.INP thread. As soon as I have more info I will update.
http://forum.kitz.co.uk/index.php/topic,15283.msg284420.html#msg284420
-
Thanks ejs for the work done on these !
-
Hi,
Thought I'd post here too as this is a thread more specific to the W9980.
I've been in contact with TP-Link for some time now, and my 9980 is now working with g.inp following updating to a beta test firmware they've sent me.
Full details over on the plusnet forum (as I'm too lazy to re-type it all again here ;)). http://community.plus.net/forum/index.php/topic,138451.0.html
Thanks,
Justin
-
Thank you Justin :)
-
Does anyone know if you can change the dns settings in this router. I have just got BT HH5 and cannot alter in there so looking at new router. This looks quite tidy peice of kit
-
Yes, you can change the DNS settings.
-
Yes, you can change the DNS settings.
Thanks I forgot I asked this means this may be best bet then
-
New firmware for TD-W9980 TD-W9980_V1_150507 .
http://www.tplink.com/en/handlers/download.ashx?resourceid=13269
New Features/Enhancement:
1.The prefix length of the Static IP of IPV6 now can be changed from 0 to 128.
2.Updated the ISP information list.
3.Improved the performance of Wireless 5GHz in short distances.
Bug Fixed:
1.Fixed the bug that the speed dropped on the BT line of UK when G.INP was enabled.
2.Fixed the kcodes security bug.
3.Fixed the bug that TD-W9980 had compatibility issues with the line of ZEN in UK.
4.Fixed the bug that TD-W9980 had compatibility issues with the line of TALK TALK in UK.
5.Fixed the bug that static IPV6 connection did not take effect after a reboot.
-
Bug Fixed:
1.Fixed the bug that the speed dropped on the BT line of UK when G.INP was enabled.
Excellent. Thanks for posting the link :)
Now marked fully compatible in the main g.inp thread
-
It doesn't seem to be listed on the TP-Link website yet, and it has taken over half an hour to download 72% of it so far.
Does anyone know if TP-Link disabled the shell access since it's a non-beta firmware? It's not easy to tell just from examining the binaries in the firmware.
-
It doesn't seem to be listed on the TP-Link website yet, and it has taken over half an hour to download 72% of it so far.
Does anyone know if TP-Link disabled the shell access since it's a non-beta firmware? It's not easy to tell just from examining the binaries in the firmware.
Available here http://www.tplink.com/en/download/TD-W9980_V1.html#Firmware very slow to download. Yes, shell access has been disabled again.
-
Does anyone know if TP-Link disabled the shell access since it's a non-beta firmware?
I should imagine they will have. From my experience in the past, all the beta f/w has shell access, but they disable it as soon as released officially.
-
Since my provider ( GVT ) doesn't use G.INP yet and the beta firmware looks to be pretty stable, I will stay with it .
-
Thanks, that's what I expected about shell access. The firmware is also visible on the uk.tp-link.com website now also.
-
"3.Improved the performance of Wireless 5GHz in short distances."
Any one know what they did?
I am having terrible Wi-Fi problems since moving the unit to be in its permanent home beside the mastersocket. Basically cant use Wi-Fi in the roofspace where I need it most :no:
Wish we could bump the transmit power up, the same 2.4Ghz wifi chip in other units appears to transmit with a lot more power.
-
I can confirm they have disabled SH access in that latest firmware.
The useless TPLink telnet stuff is still there though.
As noted else where you can just start your own copy of telnet via serial connection.
-
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FOgKmiYT.jpg&hash=920d707ed3cb4d1e9391e17ade8b103cbab061b6)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FSFZbtQp.png&hash=c1505d521e4f756d263f8faae81051b47b2f8ad5)
There is some random ..stuff.. going on with regional wifi limits for the 5Ghz, first image is set in UK region - 2nd is Australia.
No conclusions yet since I don't have any antennas atm to test. Several countries allowed 199mw which seemed like a huge percent of improvement, then Canada blew that away at 700mw odd.. then Australia above..
But anyone with Antennas want to check for increased range while setting to Canada or Australia.
Edit: I should add that its probably a few multiple times over the UK legal limit :-X
edit: 2.4GHz improvement by setting to Japan
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FIQaFZhK.jpg&hash=452dccb00d9fa3a6478cf5dea14f1df9ddfcecfe)
-
Does this new non-beta firmware support MER, I am currently using the beta with MER support but am un-sure if the new one has it
-
Does this new non-beta firmware support MER, I am currently using the beta with MER support but am un-sure if the new one has it
If you achieve it by means of the MAC cloning facility, then yes, that is available in the new firmware.
-
"3.Improved the performance of Wireless 5GHz in short distances."
Whatever it is they have done I hope it is an improvement as its one of the things I found disappointing in my review of the TD-W9980 (http://www.kitz.co.uk/routers/tplink_TD-W9980_review.htm). Unless I was stood right next to the router then performance wasnt any better than 2.4Ghz and any advantage soon dropped off - even in the same room. My Zyxel VMG8324 which only has 2.4GHz has a much better performance and range.
-
If you achieve it by means of the MAC cloning facility, then yes, that is available in the new firmware.
In the 1.6 beta there's a click box for MER support once you've setup your VDSL connection. I am guessing by your response that the current latest release does not have MER support in the way I am using it right now.
-
The WAN interface looks like this when configured for BT VDSL, no option that I can see there. Is that where the option was previously? You could always try the new firmware and revert to the beta if it isn't any good.
-
@Mooingall, do I understand that if I change the 2.4ghz location from UK to Japan I should get a stronger wifi signal, but it would also be breaking the law?
-
@Mooingall, do I understand that if I change the 2.4ghz location from UK to Japan I should get a stronger wifi signal, but it would also be breaking the law?
Yes correct, 2.4Ghz transmit power will move from 50mw to 100mw. Its appears to not be as much of a massive boost as it sounds but it has really helped with a dead area in our home (from non working to working).
Also with setting Japan the 5Ghz transmit power moves from 50mw to potentially 200mw but I believe there are some other restrictions in place that may drop that power depending on channel selected. I have not been able to test the 5Ghz.
Let me know how you get on.
The UK limit seems to be 100mW EiRP. I believe while using the Japan setting you would be totalling 223mw once you include the stock antenna's gain? Someone smarter than me can confirm that.
-
As well as being illegal, increasing your output power like that can cause extra interference to neighbouring properties. I really think that you should not do it.
-
That's a good point about interfering with neighbours WiFi.
-
Yes indeed, in simple terms we would be yelling louder than the neighbour.
Pick a non overlapping channel to minimize any disruption (1, 6 or 11 only), also check no one else is using the overlapping channels while making your choice. My understanding is if everyone sticks to 1, 6 or 11 then the devices cooperate with each other rather than simply shouting louder and drowning each other out.
If your wireless is OK then there is no reason to play with power levels and such.
-
Increasing the power output at only one end of the wireless connection probably isn't very useful. There's no point one end having much greater range than the other, if the transmissions from the other end can't reach the router.
Also, if your router has a much greater power output and range, then you might not see the other networks on the channel you're using. But the other networks on your channel might receive the signals from your router. So your router might interfere with other networks and not be aware of the problems it would be causing.
-
Please could I ask how people are getting on with the W9980, especially in terms of reliability?
I have been thinking about getting one, but have been put off by posts in the TP-Link forums about issues when UPnP is switched on and Wi-Fi dropouts/failures.
-
Mine has been up for 34 days showing 79995 down and 19999 up.
Good SNR 11.6 down.
Reporting zero errors (too good to be true?)
Wireless coverage appears to b e reasonable, unable to quantify further as I have 3 other wireless APs around the house.
Firmware was updated to latest on their site.
All in all very pleased and to me it looks to be an improvement on the TG589v3 that it replaced.
Only downside is that detailed line stats are not easily available.
Cheers
Sent from my Nexus 5 using Tapatalk
-
Thank you for the feedback Projjer - really appreciated.
It's good to hear that the W9980 is proving reliable in the longer-term, and to get a different perspective to all the negativity I've read recently.
Yes, a shame about the stats but I think I'll take the plunge.
Thanks again...
-
I've included a screenshot from my router stats page, for your info, I'm on BT Infinity 2, my HomeHub couldn't manage 24 hours connected in one go. I'm very happy.
-
I've included a screenshot from my router stats page, for your info...
Thank you! Certainly impressive. :)
-
The system uptime is how long the device has been switched on, not how long the DSL connection has been maintained. The zero error counts reported is a long standing bug with the web interface.
-
Are the stats in-depth enough to show connection time though?
-
No, that is the big downside to the TD- W9980, no stats available. Connection time can be deduced from the system log though.
-
Hmm... a bit naf, but it's available somewhere then I guess it's not the end of the world.
Thanks.
-
The system uptime is how long the device has been switched on, not how long the DSL connection has been maintained. The zero error counts reported is a long standing bug with the web interface.
I'm disappointed now :( I will say though, in practice, it is way better the a BT HomeHub 5.
-
The 9980 won't be getting vectoring according to: Will N600 - W9980 will have a G.Vector standart support in the future? (http://forum.tp-link.com/showthread.php?83295-Will-N600-W9980-will-have-a-G.Vector-standart-support-in-the-future)
-
hi guys
sorry for the very noobish question compared to what looks like very technical discussions here, but ive just bought this router to replace my current bt modem/HH4 combination, i have bt infinity 1.
is there anywhere that has a step by step guide to setting this router up for use on infinity?
what firmware should i run? (im looking for the most stable as i currently suffer from disconnects which im hoping is the HH4/modem and will be much improved using this router).
also, ive read abit about this g.inp and wondered if it was available to everyone and is it something a relative novice can enable?
I do work in I.T so i am relatively technical, but i know little about networking.
thanks guys and sorry if this question has been asked a million times before.
Ted
-
G.INP is only available on Huawei cabs. There was some beta firmware a while ago that enabled G.INP on this device but I don't know if that was rolled up into the latest stock firmware. But that's not important if you're on an ECI cab.
See http://www.kitz.co.uk/adsl/cabinet-lookup.htm
-
hi guys
sorry for the very noobish question compared to what looks like very technical discussions here, but ive just bought this router to replace my current bt modem/HH4 combination, i have bt infinity 1.
is there anywhere that has a step by step guide to setting this router up for use on infinity?
what firmware should i run? (im looking for the most stable as i currently suffer from disconnects which im hoping is the HH4/modem and will be much improved using this router).
also, ive read abit about this g.inp and wondered if it was available to everyone and is it something a relative novice can enable?
I do work in I.T so i am relatively technical, but i know little about networking.
thanks guys and sorry if this question has been asked a million times before.
Ted
The router practically sets itself up, select BT VDSL from the drop down list in the 'Quick Setup'and enter bthomehub@btbroadband.com as user name, BT as password, job done. Latest firmware is 150507
-
thanks Dray & Lic , much appreciated.
is there anything in the latest firmware to improve stability? if its purely additional features I wont use then I wont bother,
cheers
-
You need the latest firmware for G.Inp. Its perfectly stable.
-
hi guys
sorry for the very noobish question compared to what looks like very technical discussions here, but ive just bought this router to replace my current bt modem/HH4 combination, i have bt infinity 1.
is there anywhere that has a step by step guide to setting this router up for use on infinity?
what firmware should i run? (im looking for the most stable as i currently suffer from disconnects which im hoping is the HH4/modem and will be much improved using this router).
also, ive read abit about this g.inp and wondered if it was available to everyone and is it something a relative novice can enable?
I do work in I.T so i am relatively technical, but i know little about networking.
thanks guys and sorry if this question has been asked a million times before.
Ted
You won't regret the move to the 9980. Give things a day or two to settle and you won't look back. I had a very trying couple of weeks with BTs Hub 5 with constant rebooting and dropouts etc. Changed to the 9980 and I haven't looked back. Good luck. Also, just to add, the guys here are a great help when required.
-
55/6 wooow
nice speed
-
Hello guys, I see that all the gurus of TD-W9980 are here.
I recently purchased one and want to use it's USB ports to expose two my WD disks to streamer running Kodi (XBMC). Unfortunately I discovered that this router uses block device names (sda1/sdb1) in shares' names. Device names are not persistent between Linux boots and I found that after a couple of boots disks are exposed under different names (sda1 instead of sdb1 and sdb1 instead of sda1). As result path names are changed and it totally screws up Kodi's database.
Is it any way to give persistent names to disks shares exposed by this router ? Something like explained in following article: https://wiki.archlinux.org/index.php/Persistent_block_device_naming (https://wiki.archlinux.org/index.php/Persistent_block_device_naming) ? Alternatively, is it possible to login into this router via telnet/ssh and to setup the technique explained in this article ?
-
Not sure if I'm missing something here. The devices are sda1 and sdb1 on the router not on your Linux box so should remain consistently named regardless of Linux boots. There is no configuration of the router possible by Telnet/SSH.
-
If, for example, I will disconnect disk that got sda1 and reboot the router the remaining disk will get sda1. There was a situation when I didn't disconnected any disks, but after reboot they've got sdb1 and sdc1 in their share names (and in their block device names). In Linux block device names are not promised to be persistent, especially not for hot-add devices like USB drives.
Please check the link I supplied in previous note, they explain how to make those share names to be persistent between reboots. For example: if I could make that router to assign the share name according to volume label then my problem will be resolved..
-
Why are you re-booting the router? Have a look in USB settings> Storage sharing see if that will help.
-
I'm not rebooting my router :) But you know, sometimes electricity may be down or such things.. Yes, I know it should be rare, still I would like to avoid reconfiguration of Kodi after that.
I can define shares if I will disable "anonymous sharing" check box and I don't have any problems with that. But again, when I define a share I'm asked to select a volume and to select a folder on it. "To select volume" means to select between sda1 and sdb1, as they are connected now. If, from some reason (e.g. reboot) volume will get a different block device names then this share will cease to work.
Never mind, I guess I will have to suffer it. Or, maybe, I will buy a normal NAS device, will disassemble my USB drives (those are WD external USB drives) and will put them into that NAS..
-
FAO Kitz, if I remember you have a contact in TPLink who supplied the beta fw that supported MER for Sky?
Do you have any idea if they're likely to add support MER in later f/w's? As I'm stuck on 150413 without G.INP support for now :(
Thanks in advance
-
I'm afraid my main contact was with the guy who rolled out the g.inp f/w for the TD-W9970 and Im not sure if he had anything to do with the MER releases.
Unfortunately he has since moved to elsewhere within TPlink, but Ive fired off an email tonight to another contact to see if that person has any info.
Will get back to you if I hear anything.
-
Thank you.
-
Got a reply back. Not that they are aware of, but I wrote back explaining that Openreach appear to have started rolling out g.inp to their ECI cabs now and eventually all Openreach FTTC cabs will require g.inp compatible modems. I also explained that anyone on Sky needed MER support to be able to use their TD-W9980. He has now taken it up with their Head Office. Will keep you informed.
-
Published Date 25/01/16
Bug Fixed:
1.Fixed the bug that can not get the IPv6 Gateway within ZEN of UK.
2.Fixed the bug that DSL error packet shows abnormal.
3.Fixed the bug that can not get the DNSv6 and LAN IPv6 prefix automatically.
Notes :
1.For TD-W9980(UN)_V1
2.Your device's configuration won't be lost after upgrating.
http://www.tp-link.com/en/download/TD-W9980.html#Firmware
http://www.tp-link.com/res/down/soft/TD-W9980_V1_160125.zip
I don't recall seeing this last week. Any thoughts on what the "(UN)" might be?
-
UN is what TP-Link use to indicate it's universal firmware for all countries, rather than for a specific country (UK) or region (EU). I found 160125 was on the global TP-Link website, but not the UK one.
It still contains DSL firmware xcpe_574306_571801.bin, so no vectoring support.
-
Thanks for the info Ejs.
I updated anyhow, interestingly I now see a metric buttload of "DSL Downstream Errors (Pkts)" on the main page, currently 170359 within a few seconds of getting a IP.
I don't think I have ever seen it not say zero even after months of uptime.
Edit, 3 upstream errors appeared a few mins later - again I have never seen it ever say anything but 0.
Was error counting, completely broken before?
-
Error count displaying in the web interface was broken. The bug was in the HTML/JavaScript code. StatPOSTer could get the error counts.
It looks like the 160125 firmware should now be displaying CRC error counts for the current showtime - the ability to get stats covering the current showtime was added to the TP-Link layer.
-
Yes deffo showing the errors now which is nice, one thing worth noting is losing DSL connection apparently resets the error count :shrug2:
I guess it makes sense but there is no trace of the old count anywhere, they could have dumped it to the logs before clearing it.
-
Got a reply back. Not that they are aware of, but I wrote back explaining that Openreach appear to have started rolling out g.inp to their ECI cabs now and eventually all Openreach FTTC cabs will require g.inp compatible modems. I also explained that anyone on Sky needed MER support to be able to use their TD-W9980. He has now taken it up with their Head Office. Will keep you informed.
The response from Head Office is they will not be updating MER on the TD-W9980 and are currently only supporting MER for Sky on the VR200/VR900/VR600/VR2600 :(
-
Oh man that sucks. Thanks anyway Kitz :)
-
Well! I've taken the plunge about a week ago & bought a 9980 for my work premises.
So far so good! Very impressed - noticable improvement in network speeds (old Technicolor 'thing' was only 10/100 - no GigE...)
Just one question which I dont seem to be able to find a definitive answer on:- the 4th LAN/WAN ethernet socket that is (manufacturer quote) "an interchangable LAN/WAN port" - how does one ensure that it is configured as a LAN port and not a WAN port??
Probably been staring me in the face for a while, but I've probably got 'brain-fade' by now!!
TVM in advace
z1ts
-
The functionality of the LAN/WAN Ethernet port is set according to the "Operation Mode" setting:
xDSL Modem Router Mode - 4th Ethernet LAN port
Wireless Router Mode - Ethernet WAN port
-
MT ejs
I thought it would something extremely simple!
z1ts
-
Recently moved over to SKY and needed the MER option but i was running the latest so a pain to downgrade.
So contacted TP-link and they sent me a beta TD-W9980v1_0.6.0_1.13_up_boot(160321)_2016-03-21_10.04.27.bin which i presume is just the latest with added MER.
Havn't had chance to test it yet tho.
-
The only one with MER is an older firmware so I'd be surprised if what they sent you is the correct one, and trouble is it lacks the later firmwares G.INP compatibility.
-
Having said that the latest firmware available on the tplink website for the w9980 is from 2015, so it would be interesting to see what they've sent you. Any chance you could share it, via pm etc?
-
Having said that the latest firmware available on the tplink website for the w9980 is from 2015, so it would be interesting to see what they've sent you. Any chance you could share it, via pm etc?
Nope, the latest is from 25 Jan 2016 http://uk.tp-link.com/download/TD-W9980.html#Firmware
-
Went through this with tplink last year. From what I was told the beta version was not the latest and supposedly they were not going to implement MER support in further versions. Seemed pointless using it due to no further support, of course they may have changed this view but this is what they sent me at the time.
Firmware Version:0.6.0 1.10 v0021.0 Build 150413 Rel.32590n
Hardware Version:TD-W9980 v1 00000000
-
Hi,
Sorry ive been away but for anyone thats interested this is what they sent me.
http://s000.tinyupload.com/?file_id=01101659031691863891
-
This firmware has VDSL_Sky(MER) in the pull down menu.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fs33.postimg.org%2F6bfvn5ujz%2Fw9980.jpg&hash=892317935f129a97c476f6c9def4b69d462cc76f) (http://postimage.org/)
-
Certainly looks promising. If it has G.INP enabled also it would be just the firmware I need! Anyone know how we can check for G.INP, does the w9980 have telnet etc?
-
TP-Link beta firmwares usually have the sh telnet command enabled to get to a shell. Then you can use the commands:
/firmware/dsl_cpe_pipe.sh lfcg 0
/firmware/dsl_cpe_pipe.sh lfcg 1
/firmware/dsl_cpe_pipe.sh lfsg 0
/firmware/dsl_cpe_pipe.sh lfsg 1
0 = upstream and 1 = downstream for those commands. lfcg = LineFeatureConfigGet which shows what's enabled on the TP-Link itself, lfsg = LineFeatureStatusGet which shows what's in use, subject to cabinet capability and the DLM enabling retransmission for your line.
TP-Link release firmwares don't give shell access, although there is a way around that (http://forum.kitz.co.uk/index.php/topic,15738.0.html).
-
Dunno about G.inp my cab is ECI so not bothered in looking.
Although in DSL settings there is Enable SRA check box.
-
... beta TD-W9980v1_0.6.0_1.13_up_boot(160321)_2016-03-21_10.04.27.bin ...
Hello everybody. I'm really sorry to bring this topic up after three years since the last post, but does anyone still have this firmware file, and if so would you be willing to send it to me? (Obviously the TinyUpload URL expired years ago.)
Thanks and sorry again.
-
Yes, I still have it.
-
Yes, I still have it.
Hi Licquorice
I am also in need of this firmware downgrade if you can send me a link.
Thx
Mick
-
I have nowhere to put it I'm afraid, do you have somewhere I can upload it to?
-
Try this https://file.io/8Y72qC
-
Try this https://file.io/8Y72qC
also here if that link stops working
https://www.dropbox.com/s/24lc8mv7gjkzozr/TD-W9980v1_0.6.0_1.10_up_boot%28150413%29_2015-04-13_09.06.50.zip
-
I don't think that is the version required.
-
Thank you so much licquorice! That's the one I was looking for (2016/03/21).
-
Uploaded again for MickAtHome https://file.io/9XXpg2
-
I have nowhere to put it I'm afraid, do you have somewhere I can upload it to?
PM sent
-
Responded
-
I have nowhere to put it I'm afraid, do you have somewhere I can upload it to?
Thanks for sorting me out a link. Firmware flashed and W9980 now connecting to Sky Fibre :-)
Mick
-
Friends, sorry to revive this topic, but could you please provide the firmware TD-W9980v1_0.6.0_1.13_up_boot (160321) _2016-03-21_10.04.27.bin? The links are off .... thanks for any help!
-
Guys does anyone have the firmware for the TD-W9980 that supports MER that they can send me please?
Thank you in advance.
-
Hi There,
does anyone still have the firmware TD-W9980v1_0.6.0_1.13_up_boot (160321) available that they can send me?