The content of this topic has been archived between 12 Apr 2018 and 23 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
config atm-bridge
option unit 0
option encaps llc
option vpi 1
option vci 32
option payload bridged # some ISPs need this set to 'routed'
config interface wan
option ifname nas0
option proto pppoe
option username "f00"
option password "xxx"That works for me with german provider arcor
I have the same settings the format is a bit different.
The Problem actually is
OpenWrt daemon.warn pppd[906]: Timeout waiting for PADO packets
Also the ppp interface is not appearing in ifconfig.
Do i need to explicitly mention the ppp0 interface in the /etc/network/interfaces file?
is br2684ctl installed and running?
yes it is though it doesnot run automatically i start it with the init script.
When i set the payload to routed the logread says unrecognized option 'nic-nas0
Jan 1 01:08:50 OpenWrt local2.notice br2684ctl[2727]: Interface "nas0" created sucessfully
Jan 1 01:08:50 OpenWrt local2.notice br2684ctl[2727]: Communicating over ATM 0.0.103, encapsulation: LLC
Jan 1 01:08:50 OpenWrt local2.info br2684ctl[2727]: Interface configured
Jan 1 01:08:50 OpenWrt local2.info br2684ctl[2731]: RFC 1483/2684 bridge daemon started
Jan 1 01:08:51 OpenWrt daemon.info pppd[2762]: Plugin rp-pppoe.so loaded.
Jan 1 01:08:51 OpenWrt daemon.err pppd[2762]: Interface nas0 not Ethernet
Jan 1 01:08:51 OpenWrt user.info : /usr/sbin/pppd: unrecognized option 'nic-nas0'
Jan 1 01:08:51 OpenWrt daemon.err pppd[2762]: unrecognized option 'nic-nas0'
Jan 1 01:08:51 OpenWrt user.info : pppd version 2.4.3
Jan 1 01:08:51 OpenWrt user.info : Usage: /usr/sbin/pppd [ options ], where options are:
Jan 1 01:08:51 OpenWrt user.info : <device> Communicate over the named device
Jan 1 01:08:51 OpenWrt user.info : <speed> Set the baud rate to <speed>
Jan 1 01:08:51 OpenWrt user.info : <loc>:<rem> Set the local and/or remote interface IP
Jan 1 01:08:51 OpenWrt user.info : addresses. Either one may be omitted.
Jan 1 01:08:51 OpenWrt user.info : asyncmap <n> Set the desired async map to hex <n>
Jan 1 01:08:51 OpenWrt user.info : auth Require authentication from peer
Jan 1 01:08:51 OpenWrt user.info : connect <p> Invoke shell command <p> to set up the serial line
Jan 1 01:08:51 OpenWrt user.info : crtscts Use hardware RTS/CTS flow control
Jan 1 01:08:51 OpenWrt user.info : defaultroute Add default route through interface
Jan 1 01:08:51 OpenWrt user.info : file <f> Take options from file <f>
Jan 1 01:08:51 OpenWrt user.info : modem Use modem control lines
Jan 1 01:08:51 OpenWrt user.info : mru <n> Set MRU value to <n> for negotiation
Jan 1 01:08:51 OpenWrt user.info : See pppd(8) for more options.
Jan 1 01:09:08 OpenWrt daemon.info pppd[2933]: Plugin rp-pppoe.so loaded.
Jan 1 01:09:08 OpenWrt daemon.err pppd[2933]: Interface nas0 not Ethernet
Jan 1 01:09:08 OpenWrt daemon.err pppd[2933]: unrecognized option 'nic-nas0'yes it is though it doesnot run automatically i start it with the init script.
Run the following to make the init script run at boot:
/etc/init.d/br2684ctl enableThis creates a symlink in /etc/rc.d/
Not sure what the PADO errors are.....are you sure your ISP is using PPPoE? You might want to try changing "option proto" from pppoe to dhcp and see if you get a lease on nas0. If you do, then they're using bridged DSL.
Also, not that it relates to your current problem but G.DMT.BIS=ADSL2 from what I googled, so once you're up and running you might want to change your modulation variable to AD2MOD.
I have enabled br2684ctl.
I changed option proto to routed but still no connection. I think openwrt and my router dont like each other :-)
I changed option proto to routed but still no connection.
No, please re-read my post. We're looking for a potential DHCP lease on the nas0 interface.
If you're sure your connection is PPPoE, you might want to troubleshoot with this Google search:
"Timeout waiting for PADO packets" site:forums.whirlpool.net.au
The whirlpool forum is an excellent source of information.
You're close!
The discussion might have continued from here.