config atm-bridge
option encaps 'llc'
option payload 'bridged'
option vci '32'
option vpi '1'
are vpi and vci values true ?
for example, My country's ISS values vpi:8,vci:35
Yes, I tripplechecked them.
I found in file pppd/plugins/rp-pppoe/pppoe-discovery.c there is method "discovery" which tries 3 x 5s to get PADO reply. From there I see no light 
I think I will have to use my old modem/router till my line switches to VDSL in 6 weeks and then try W8970B again.
That is quite curious. I've never had a line where PPPoE wasn't virtually instantaneous or generally failed.
Although I never experienced it myself, I have read about cases where even ADSL lines need the correct VLAN ID. See the OP's problem above.
Also, does your ISP care about your modem's MAC address? I'm guessing not since you can switch between modems without any problem, but some do.
I don't understand networking PPPoE and such. But I can confirm that my old modem lights up DSL line and only after considerable amount of time Internet light comes up. It may very well take half a minute.
I talked to another guy at ISP as it is evening now and this time I was given information too about instantaneous connect. (as I believe takimata is saying) Besides he did not seem to know what "PADO timeout" I was talking about
I don't know how to set up VLAN ID for ADSL. I could not find it in the luci neither in the uci.
"too instantaneous"? That's the first time I heard about that, and the fact that you got two different answers from two different people makes me think that you've reached a lower support level where guessing is still a valid reaction.
At any rate, you can test if you're connecting too fast. Disable the WAN interface, unplug and replug the DSL line, wait a sensible amount of coffees and then reactivate the WAN interface.
network.dsl.xfer_mode='atm'
network.dsl.line_mode='adsl'
network.dsl.annex='b'
network.wan=interface
network.wan.proto='pppoe'
network.wan.ipv6='auto'
network.wan._orig_ifname='ptm0'
network.wan._orig_bridge='false'
I tend to believe problem lies in these lines:
network.wan.ifname='ptm0'
network.wan_dev.name='ptm0'
I compared my config with stock config and I see change in network.dsl.xfer_mode from ptm to atm. So what ptm0 means actually? And what is nas0? I tried that setting too.
I believe this is more nuanced, both VDLS and ADSL ITU standards use lettered annexes, but unfortunately they use the same letters for different meanings. For VDSL2 all bandplans are defined in Annex B if I recall correctly, while for ADSL Annex B is a specific bandplan that is compatible with ISDN. PTM and ATM are two different beasts entirely, think about them as different coding schemes on the wire (not entirely true). PTM actually was introduced as an Annex to ADSL2 (see ITU G.992.3 Annex N), but as far as I can tell is not used on ADSL links at all; while on VDSL2 links both ATM and PTM seem permitted only PTM seems to be used. In short for an adsl link you will in all likelyhood need network.dsl.xfer_mode='atm'.
Okay, this is actually starting to point to an issue. Obviously, only a small fraction of OpenWrt/LEDE supported routers do have an internal modem and so it will only affect a small part of the user base. But configuring an internal modem, what to choose and how to choose it, is woefully badly documented.
Especially if you're on ADSL (which, interestingly, a lot of people are regressing to nowadays), your exclusive source for documentation is random bits and pieces mentioned in some routers' Wiki pages. And as the issue at hand shows, they may even be wrong or outdated. Most notably, internal DSL configuration is completely absent from the network configuration pages and doesn't have any supplemental documentation.
See, and that directly contradicts what is written on OpenWrt's Wiki page for this router that says you should set PTM. Yes, of course, not LEDE pages. But like me right now, you have to be told that this is wrong by someone more knowledgeable, because even if you are somewhat familiar with the technologies and the abbreviations, see if you find an article that explains that PTM came with VDSL and ADSL in all likelyhood doesn't use it. And good luck finding anything that explains "ptm0", VLANs on PTM, and what "nas0" is (or isn't anymore, I'm still not quite sure about that one).
This is quite frustrating. Yes, I realize I shouldn't give advice on things I didn't do myself, but this is something that should be remedied.
(As for me, I will go further up and remove any guesswork/bad advice from my posts and keep my mouth shut about the ADSL business I never tried first hand.)
That seems to be true, but I note I have looked into the ITU standards but have not configured ADSL/VDSL in lede/openwrt at all, so take what I say with a grain of salt...
That sounds not great, I am planning of getting a router with a VDSL2 modem, and this looks like it will be a challenge to get working properly; I guess I will not retire my old modem-router before the replacement works well.
My reading of that section is simply an instruction how to set the different options without any information under which conditions one should select which, so not a direct contradiction, but also not too enlightening.
No, please keep advising people, even if you are not 100% sure, just label such more experimental recommendations accordingly. It will always be more helpful than total silence 
Best Regards
normaly but not tested via the file: /etc/ppp/options
try this:
...
lcp-echo-failure 5 # mean 5 trys = are failure
lcp-echo-interval 10 # mean interval in seconds to the next request
...i hope this file survice a uci reload
I made the change though to be honest I got to the internet right as I switched the router. (at the time without the change to /etc/ppp/options)
Sat Jun 17 19:54:46 2017 kern.warn kernel: [ 85.333693] enter showtime, cell rate: 0 - 2033, 1 - 2033, xdata addr: 0xa2fa0000
Sat Jun 17 19:54:46 2017 kern.info kernel: [ 85.339866] IPv6: ADDRCONF(NETDEV_CHANGE): nas0: link becomes ready
Sat Jun 17 19:54:46 2017 daemon.notice netifd: Network device 'nas0' link is up
Sat Jun 17 19:54:46 2017 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Jun 17 19:54:46 2017 daemon.notice netifd: Interface 'wan' is setting up now
Sat Jun 17 19:54:46 2017 kern.warn kernel: [ 85.364702] enter showtime, cell rate: 0 - 2033, 1 - 2033, xdata addr: 0xa2fa0000
Sat Jun 17 19:54:47 2017 daemon.info pppd[4171]: Plugin rp-pppoe.so loaded.
Sat Jun 17 19:54:47 2017 daemon.info pppd[4171]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sat Jun 17 19:54:47 2017 daemon.notice pppd[4171]: pppd 2.4.7 started by root, uid 0
Sat Jun 17 19:54:52 2017 daemon.info pppd[4171]: PPP session is 53922
Sat Jun 17 19:54:52 2017 daemon.warn pppd[4171]: Connected to 6c:20:56:14:0c:c5 via interface nas0
Sat Jun 17 19:54:52 2017 kern.info kernel: [ 91.082019] pppoe-wan: renamed from ppp0
Sat Jun 17 19:54:52 2017 daemon.info pppd[4171]: Using interface pppoe-wan
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: Connect: pppoe-wan <--> nas0
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: PAP authentication succeeded
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: peer from calling number 6C:20:56:14:0C:C5 authorized
Sat Jun 17 19:54:52 2017 daemon.notice netifd: Network device 'pppoe-wan' link is up
Sat Jun 17 19:54:52 2017 daemon.notice netifd: Interface 'wan6' has link connectivity
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: local IP address 85.135.162.239
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: remote IP address 84.16.59.41
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: primary DNS address 195.28.64.99
Sat Jun 17 19:54:52 2017 daemon.notice pppd[4171]: secondary DNS address 195.80.171.4
Ther must have been some other error im my config, though I am not sure. For the record I show the commands I have issued so far that got me to the internet vie ADSL,.
root@LEDE:~# uci set network.dsl.annex=b
root@LEDE:~# uci set network.dsl.line_mode=adsl
root@LEDE:~# uci set network.dsl.xfer_mode=atm
root@LEDE:~# uci delete network.dsl.tone
root@LEDE:~# uci set network.wan.ifname=nas0
root@LEDE:~# uci set network.wan.username=xxxuser@slovanet.adsl
root@LEDE:~# uci set network.wan.password=yyypass
root@LEDE:~# uci commit
Thanks to every one:-)
Time has come and this is my very first VDSL day.
Status: UP
Line State: showtime_tc_sync [0x801]
Line Mode: G.993.2 (VDSL2)
Annex: B
Profile: 17a
Data Rate: 52.496 Mb/s / 5.245 Mb/s
Max. Attainable Data Rate (ATTNDR): 98.747 Mb/s / 54.261 Mb/s
Latency: 8.0 ms / 2.0 ms
Line Attenuation (LATN): 14.8 dB / 16.3 dB
Signal Attenuation (SATN): 14.8 dB / 16.2 dB
Noise Margin (SNR): 18.6 dB / 23.2 dB
Aggregate Transmit Power(ACTATP): -9.5 dB / 14.4 dB
Forward Error Correction Seconds (FECS): 134756 / 181
Errored seconds (ES): 0 / 162941
Severely Errored Seconds (SES): 0 / 162939
Loss of Signal Seconds (LOSS): 0 / 162939
Unavailable Seconds (UAS): 32 / 32
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: 1m 2s
ATU-C System Vendor ID: Broadcom 177.169
Power Management Mode: L0 - Synchronized
Hello all
I have a TD-W8970 v1 model and I want to get started on all this, do you need the serial cable to be able to do it when you have an updated firmware?
the only way is updated via openwrt?
regards
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.