Hi. I installed LEDE on W8970 (17.01.1). There was no problem using Adsl2. But after Vdsl2 I can not connect internet.
My ISS Turk.net
config dsl 'dsl'
option annex 'b'
option xfer_mode 'ptm'
option line_mode 'vdsl'
config interface 'wan'
option ifname 'ptm0'
option proto 'pppoe'
option ipv6 'auto'
option username '***********@turk.net'
option password '*******'
Status: UP
Line State: showtime_tc_sync [0x801]
Line Mode: G.993.2 (VDSL2)
Annex: B
Profile: 17a
Data Rate: 76.796 Mb/s / 4.095 Mb/s
Max. Attainable Data Rate (ATTNDR): 104.982 Mb/s / 50.097 Mb/s
Latency: 0.0 ms / 0.0 ms
Line Attenuation (LATN): 8.4 dB / 6.5 dB
Signal Attenuation (SATN): 8.5 dB / 9.7 dB
Noise Margin (SNR): 16.3 dB / 34.2 dB
Aggregate Transmit Power(ACTATP): -11.7 dB / 10.1 dB
Forward Error Correction Seconds (FECS): 0 / 5
Errored seconds (ES): 0 / 5
Severely Errored Seconds (SES): 0 / 0
Loss of Signal Seconds (LOSS): 0 / 0
Unavailable Seconds (UAS): 31 / 31
Header Error Code Errors (HEC): 0 / 0
Non Pre-emtive CRC errors (CRC_P): 0 / 0
Pre-emtive CRC errors (CRCP_P): 0 / 0
Line Uptime: 11s
ATU-C System Vendor ID: Broadcom 164.81
Power Management Mode: L0 - Synchronized
The chipset speaks both, it's just the original TP-Link firmware that limits it to ADSL2+. I have both a W8970 and a W9980 (same chipset) on VDSL lines. If you look at the logfile above, the VDSL line is successfully connected (and quite nicely, I might add, 105 MBit is nothing to scoff at). So the problem must be on the authentication side, most probably the VLAN ID setting.
@vahithosan: I don't speak Turkish, but a cursory Google search seems to confirm that a the VDSL line needs to be on the correct VLAN ID, and you must set it in the ifname section. For example, VLAN ID 35 would be configured as:
config interface 'wan'
option ifname 'ptm0.35'
(...)
I couldn't tell you which VLAN ID is the correct one, you'll have to check yourself, either with other forums, customer support or manuals, or with your old router. Some forums seem to indeed indicate VLAN ID 35, but this page seems to say VLAN ID 15.
1 Like
Thanks for all reply. I will try and share here.
It works very well. Thanks.
here is my config file
root@LEDE:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix '****************'
config atm-bridge 'atm'
option encaps 'llc'
option payload 'bridged'
option vci '35'
option vpi '8'
config dsl 'dsl'
option annex 'b'
option tone 'av'
option xfer_mode 'ptm'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222'
config interface 'wan'
option ifname 'ptm0.35'
option proto 'pppoe'
option ipv6 'auto'
option username '***********'
option password '***********'
config device 'wan_dev'
option name 'ptm0'
option macaddr '**************'
config interface 'wan6'
option ifname 'pppoe-wan'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 2 4 5 6t'
1 Like
[quote="vahithosan, post:1, topic:4149, full:true"]
Hi. I installed LEDE on W8970 (17.01.1).[/quote]
Hi, I would like to try it too, but when following instructions at guide-quick-start/standardflashinginstructions
they say
The Device Techdata page will have two links: Firmware LEDE Install URL and Firmware LEDE Upgrade URL. The first is for a “factory installation”, the second for a “sysupgrade installation”.
I can only see Firmware LEDE Upgrade URL
at his link:
https://lede-project.org/toh/hwdata/tp-link/tp-link_td-w8970_10
Where did you find suitable firmware?
I cant find direct install firmware too but this guide very good. (for without opening case install)
https://forum.openwrt.org/viewtopic.php?pid=340785#p340785
Thank you. If I understand correctly you installed 15.05 release of openwrt-lantiq-xrx200-TDW8970-sysupgrade.image first using linked instructions and updated to LEDE afterwards using web interface of OPEN WRT?
Yes. first, I installed openwrt. After my router bricked when i installed lede.
This guides helped me: (i use ubuntu)
https://wiki.openwrt.org/toh/tp-link/td-w8970
"Installation using Serial"
OK, I already had serial access. Telnet did not work for me.So I installed OPEN WRT first and upgraded using sysupgrade image to LEDE. I see this firmware version now in web interface:
LEDE Reboot 17.01.1 r3316-7eb58cf109 / LuCI lede-17.01 branch (git-17.100.70571-29fabe2)
I hope I am all set correctly.
I think it's done
My router too (Powered by LuCI lede-17.01 branch (git-17.100.70571-29fabe2) / LEDE Reboot 17.01.1 r3316-7eb58cf109)
Today after reading about LEDE/Luci I decided to configure the router and use it insted of my old ADSL router. I can not get ADSL working, DSL status is DOWN.
Status: DOWN
Line State: not initialized [0x0]
Line Mode:
Annex:
Profile:
Data Rate: 0 b/s / 0 b/s
Max. Attainable Data Rate (ATTNDR): 0 b/s / 0 b/s
Did you need to install DSL support after installing LEDE?
I didnt install anything after LeDe install.
Maybe your problem is cable connection because I could see the DSL signal even if my settings were wrong.
Very strange I just reverted to TP-Link firmware and ADSL works. With LEDE there was no ADSL. And I planned to use this router for coming VDSL next month. Can someone please help with LEDE/xDSL?
This is a shot in the dark as I don't have first-hand experience with ADSL lines, only VDSL lines on this router. But AFAIK the annex setting is relevant for ADSL (not for VDSL). Did you select the correct annex in network's dsl config? I.e.,
config dsl 'dsl'
(...)
option annex 'b'
("a", "b", or "j" respectively)?
Hi i have a VDSL line too, but i know for the ADSL are the "config atm-bridge 'atm'" are relevant too.
You need the right VPI and VCI values and you must specefied the exact right DSL specification like: Annex B G992.1
VDSL should be work automatic.
The xfer_mode is on ADSL normally (i think soo) atm.
be shure that the Firmware a installed:
opkg list-installed | grep dsl-vrx200 should get:
dsl-vrx200-firmware-xdsl-a and dsl-vrx200-firmware-xdsl-b-patch
or
dsl-vrx200-firmware-xdsl-b and dsl-vrx200-firmware-xdsl-a-patch
How the loading (and patching) process work can be see in this script:
/etc/init.d/dsl_control
you can specified the firmware what should be used via:
option firmware 'path-to-your-firmware'
note that the restrubale firmware does not support vectoring if you need vectoring you can extract any other firmware from a vr9 device like FritzBox 7360 and use them.
see here: https://xdarklight.github.io/lantiq-xdsl-firmware-info/
Thanks. I tried some more options but no luck so far. Just to be sure .. I have W8970B, not plain W8970 as most of you probably, version V1. I hope that hw flavour is also supported with the same firmware.
BTW I have
dsl-vrx200-firmware-xdsl-b and dsl-vrx200-firmware-xdsl-a-patch
installed
I hve progress here. ADSL is now UP
DSL
DSL Status
DSL Status: UP
Line State: showtime_tc_sync [0x801]
Line Mode: G.992.5 (ADSL2+)
Annex: B
Profile:
Data Rate: 9.216 Mb/s / 862 Kb/s
Max. Attainable Data Rate (ATTNDR): 25.160 Mb/s / 1.523 Mb/s
Latency: 8.0 ms / 7.0 ms
Line Attenuation (LATN): 6.6 dB / 4.3 dB
Signal Attenuation (SATN): 5.2 dB / 4.1 dB
Noise Margin (SNR): 16.4 dB / 16.3 dB
Aggregate Transmit Power(ACTATP): 8.9 dB / 4.6 dB
Forward Error Correction Seconds (FECS): 0 / 53
Errored seconds (ES): 17 / 99507
Severely Errored Seconds (SES): 17 / 99362
Loss of Signal Seconds (LOSS): 2 / 99196
Unavailable Seconds (UAS): 79 / 79
Header Error Code Errors (HEC): 0 / 16829
Non Pre-emtive CRC errors (CRC_P): 0 / 0
Pre-emtive CRC errors (CRCP_P): 0 / 0
Line Uptime: 27m 30s
ATU-C System Vendor ID: Broadcom 177.169
Power Management Mode: L0 - Synchronized
but I still do not have access to internet. This is what I see in log
Mon Apr 17 17:27:06 2017 daemon.info pppd[9864]: Plugin rp-pppoe.so loaded.
Mon Apr 17 17:27:06 2017 daemon.info pppd[9864]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Mon Apr 17 17:27:06 2017 daemon.notice pppd[9864]: pppd 2.4.7 started by root, uid 0
Mon Apr 17 17:27:21 2017 daemon.warn pppd[9864]: Timeout waiting for PADO packets
Mon Apr 17 17:27:21 2017 daemon.err pppd[9864]: Unable to complete PPPoE Discovery
Mon Apr 17 17:27:21 2017 daemon.info pppd[9864]: Exit.
Mon Apr 17 17:27:21 2017 daemon.notice netifd: Interface 'wan' is now down
Mon Apr 17 17:27:21 2017 daemon.notice netifd: Interface 'wan' is disabled
Mon Apr 17 17:27:21 2017 daemon.notice netifd: Interface 'wan' is enabled
Mon Apr 17 17:27:21 2017 daemon.notice netifd: Interface 'wan' is setting up now
Mon Apr 17 17:27:21 2017 daemon.info pppd[10852]: Plugin rp-pppoe.so loaded.
Mon Apr 17 17:27:21 2017 daemon.info pppd[10852]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Mon Apr 17 17:27:21 2017 daemon.notice pppd[10852]: pppd 2.4.7 started by root, uid 0
Mon Apr 17 17:27:36 2017 daemon.warn pppd[10852]: Timeout waiting for PADO packets
Mon Apr 17 17:27:36 2017 daemon.err pppd[10852]: Unable to complete PPPoE Discovery
Mon Apr 17 17:27:36 2017 daemon.info pppd[10852]: Exit.
Mon Apr 17 17:27:37 2017 daemon.notice netifd: Interface 'wan' is now down
Mon Apr 17 17:27:37 2017 daemon.notice netifd: Interface 'wan' is disabled
Mon Apr 17 17:27:37 2017 daemon.notice netifd: Interface 'wan' is enabled
Mon Apr 17 17:27:37 2017 daemon.notice netifd: Interface 'wan' is setting up now
this is my config:
config dsl 'dsl'
option xfer_mode 'atm'
option line_mode 'adsl'
option annex 'b'
config interface 'wan'
option ifname 'nas0'
option proto 'pppoe'
option username 'XXX'
option password 'XXX'
config atm-bridge
option encaps 'llc'
option payload 'bridged'
option vci '32'
option vpi '1'
I talked to the guy at the provider. He says 15s (as seen from the log) is not enough, login usually takes longer for most customers for whatever reason. So it seems like I have to increase timeout on 40s or so. But where can I do this change? Forum search did not bring me much.