OpenWrt Forum Archive

Topic: Timeout PADO packets

The content of this topic has been archived on 29 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello,

I finally put Kamikaze on my WAG354G (given there). It's Kamikaze built the 1st January.
I tried to set up my WAN network but the PPPoE discovering cannot be complete. Here is my config: (eth0.1 is the wan)

BusyBox v1.8.2 (2008-01-01 14:57:58 CET) built-in shell (ash)

root@OpenWrt:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:BF:EB:C1:F6
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:425 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:44599 (43.5 KiB)  TX bytes:79337 (77.4 KiB)
          Interrupt:41

eth0.1    Link encap:Ethernet  HWaddr 00:14:BF:EB:C1:F6
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:324 (324.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I don't know if eth0.1 is a good choice but when I changed it at the next boot the network dispear so I kept this name. I have not listed here a eth1 interface (which I don't know what it is) and a wlan0 too.
When I tried to set up wan it say:

root@OpenWrt:~# ifup wan
[...]
root@OpenWrt:~# logread
[...]
Jan  1 00:01:09 OpenWrt daemon.warn pppd[366]: Timeout waiting for PADO packets
Jan  1 00:01:09 OpenWrt daemon.err pppd[366]: Unable to complete PPPoE Discovery
Jan  1 00:01:49 OpenWrt daemon.info pppd[592]: Plugin rp-pppoe.so loaded.
Jan  1 00:01:49 OpenWrt daemon.info pppd[592]: Plugin rp-pppoe.so loaded.
Jan  1 00:01:49 OpenWrt daemon.notice pppd[593]: pppd 2.4.3 started by root, uid 0
Jan  1 00:02:04 OpenWrt daemon.warn pppd[593]: Timeout waiting for PADO packets
Jan  1 00:02:04 OpenWrt daemon.err pppd[593]: Unable to complete PPPoE Discovery

root@OpenWrt:~# ps
[...]
  659 root       2568 S   /usr/sbin/pppd plugin rp-pppoe.so mtu 1492 mru 1492 n

It seems that pppd is running after the timeout. Here is the other files that I configured:

root@OpenWrt:/etc/ppp# cat chap-secrets # same as pap-secrets
#USERNAME  PROVIDER  PASSWORD  IPADDRES
"secret@bluewin.ch" "*"     "secret"        "*"
# bluewin.ch is my ISP

root@OpenWrt:/etc/ppp# cat options # same error as above with the default settings
debug
noaccomp
nopcomp
nocrtscts
lock
maxfail 0
lcp-echo-failure 5
lcp-echo-interval 1
name "secret@bluewin.ch"
user "secret@bluewin.ch"
passive
noipdefault
defaultroute
plugin rp-pppoe.so
mtu 1492
mru 1452

With the linksys firmware (config here) it works so I don't understand why it wouldn't work with Kamikaze. I'm a beginner in OpenWRT so if I forget to give an information tell me. I hope someone can help me.

Thank you very much !
Best regards, Jamesbch.

This definitely does work in Kamikaze.  I have done it on another AR7-based device.

Please post the contents of your /etc/config/network file (without the PPPoE password, of course.)

See the PPPoE configuration section of the KamikazeConfiguration wiki page.

Sorry I omitted the most important file big_smile Here is it:

config interface loopback
    option ifname    lo
    option proto    static
    option ipaddr    127.0.0.1
    option netmask    255.0.0.0

config interface lan
    option ifname    eth0
    option proto    static
    option ipaddr    192.168.1.1
    option netmask    255.255.255.0

# WAN config
config interface    wan
    option ifname    "eth0.1"
    option proto    "pppoe"
    option device    "ppp"
    option username "secret@bluewin.ch"
    option password "secret"
    option keepalive    "5"
    option usepeerdns
    option defaultroute
    option persist
    option noipdefault
    option ktune
    option unit    0

I go look at the documentation and your link.

PS: Must I set the 'proto' of wan to dhcp ? Is that better instead of pppoe ?
I don't know what to change in my files so I need someone give me a hand, please.

I did lots of tests and I wasn't able to connect to Internet at all hmm so I need some help please.
Here is what I found:

1/ ifconfig shows me an interface called eth1 (disabled at boot) and I don't what it is.

root@OpenWrt:/etc/config# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:14:BF:EB:C1:F6
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:992 errors:0 dropped:0 overruns:0 frame:0
          TX packets:927 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:97803 (95.5 KiB)  TX bytes:323027 (315.4 KiB)
          Interrupt:41

eth0.1    Link encap:Ethernet  HWaddr 00:14:BF:EB:C1:F6
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1368 (1.3 KiB)

eth1      Link encap:Ethernet  HWaddr 00:14:BF:EB:C1:F6
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:27

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:954 (954.0 B)  TX bytes:954 (954.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:14:BF:EB:E4:D6
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wmaster0  Link encap:UNSPEC  HWaddr 00-14-BF-EB-E4-D6-74-09-00-00-00-00-00-00-00-00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I tried many times to pppd every interfaces but each time it's a "Unable to complete PPPoE Discovery" with "Timeout waiting for PADO packets" :

root@OpenWrt:~# /usr/sbin/pppd plugin rp-pppoe.so eth0.1 (I tried eth1 and eth0 too)
Plugin rp-pppoe.so loaded.
Plugin rp-pppoe.so loaded.

root@OpenWrt:~# logread
[...]
Jan  1 00:02:37 OpenWrt daemon.info pppd[615]: Plugin rp-pppoe.so loaded.
Jan  1 00:02:37 OpenWrt daemon.info pppd[615]: Plugin rp-pppoe.so loaded.
Jan  1 00:02:37 OpenWrt daemon.notice pppd[616]: pppd 2.4.3 started by root, uid 0
Jan  1 00:02:52 OpenWrt daemon.warn pppd[616]: Timeout waiting for PADO packets
Jan  1 00:02:52 OpenWrt daemon.err pppd[616]: Unable to complete PPPoE Discovery
Jan  1 00:02:52 OpenWrt daemon.info pppd[616]: Exit.

2/ I tried to change all settings in network, I tried (on eth0.1) proto set to dhcp but it's worth. I tried to change the name to eth0.1 etc...
The debug mode in /ppp/options doesn't show me anything new. I rebooted a lots of time and it doesn't change anything to my probleme.

3/ I removed the Internet cable from the router. I rebooted, did a ifup and a pppd: Ifconfig -a showed exactly the same list as above. It seems that the router don't detect if the cable is in or not. Moreover, the Internet LED has never been lit on Kamikaze.

Please, Wodin or anybody else, can you give a hand. I shall be very grateful for it.

Thank you for your reply Wodin !

Unfortunatly br2684ctl has a grudge against me :

root@OpenWrt:/etc/config# /etc/init.d/br2684ctl start
br2684ctl[686]: socket creation failed: Address family not supported by protocol
br2684ctl[686]: Communicating over ATM 0.8.35, encapsulation: LLC

br2684ctl[686]: failed to create socket 124, reason: Address family not supported by protocol
br2684ctl[686]: setsockopt SO_SNDBUF: (-1) Unknown error -1

br2684ctl[686]: setsockopt SO_ATMQOS 9
br2684ctl[686]: Fatal: failed to connect on socket

my network config:

config atm-bridge
    option unit     0
    option encaps   llc
    option vpi      8
    option vci      35

config interface wan
    option ifname   nas0
    option proto    pppoe
    option username "..."
    option password "..."

What does this mean ? Won't I be able to connect to Internet ? I used a compiled bin version of Kamikaze, must I compile it myself ?

I just used the vpi and vci of my configuration for my ISP.
Do I need to modifiy anything else ? (chap-secrets ? options ?) Because I reset them to the defaults each time. I am really really not lucky.

(Last edited by jamesbch on 15 Feb 2008, 17:46)

jamesbch wrote:

I just used the vpi and vci of my configuration for my ISP.

The VPI and VCI must be as specified by your ISP, so that should be correct.

I don't know what is causing the br2684ctl problem.  I assume you tried rebooting? smile

Maybe compiling Kamikaze yourself will help, but since I don't know what the problem is, I can't say for sure.  When I tried it I compiled Kamikaze myself (because 7.09 doesn't support the boards I was using.)

It seems that another possible encapsulation is "vc", so perhaps you can try "option encaps vc" instead of llc.  (I have no idea if that's likely to help.)

This thread implies there might be something missing from the kernel (e.g. a module that isn't loaded.)  Rebooting might fix that.  Otherwise, installing the right kmod-xxx package might do the trick (although I think all necessary kernel modules should be installed already if you have br2684ctl installed).

Sorry for the vague reply smile

Your answer isn't vague, I know where to search know smile and I thank you very much.

I discovered something with br2684. If I do a "insmod br2684" and it don't find it. I don't understand why it is working for you but not me. I rebooted a lots of time of course.
I tried also vc instead of llc but it still doesn't do anything, same error, same probleme. One question, I don't see nas0 in `ifconfig -a` Is that a probleme too, isn't that ?

Here is my modules loaded:

root@OpenWrt:/etc/config# lsmod
Module                  Size  Used by    Not tainted
acx_mac80211           76032  0
nf_nat_tftp             1120  0
nf_conntrack_tftp       3760  1 nf_nat_tftp
nf_nat_irc              1856  0
nf_conntrack_irc        4848  1 nf_nat_irc
nf_nat_ftp              2464  0
nf_conntrack_ftp        6944  1 nf_nat_ftp
ppp_async              11616  0
ppp_generic            26944  1 ppp_async
slhc                    6080  1 ppp_generic
crc_ccitt               1472  1 ppp_async
mac80211              140224  1 acx_mac80211
cfg80211               18960  1 mac80211
arc4                    1408  2
aes                    28752  0
deflate                 2592  0
ecb                     2400  2
cbc                     3456  0
blkcipher               4976  2 ecb,cbc
crypto_hash             1632  0
cryptomgr               2432  0
crypto_algapi           9728  6 arc4,aes,deflate,ecb,cbc,cryptomgr

When something is missing in the kernel like modules, must I compile Kamikaze myself ? It's not so hard but my router need a specific kind of header, and I don't know what it is and where to write it into.
Can you see something missing in my lsmod ?

Thank you Wodin for your patience.

jamesbch wrote:

Can you see something missing in my lsmod ?

It seems you're missing a driver for the ATM chipset.

I don't have one of these routers with OpenWrt installed at the moment, but as far as I remember there should be a module called sangam-atm-annex-a.ko (or annex-b).  (South Africa uses Annex A.  If you don't know which one to use, install one and see if it works.  If it doesn't work, uninstall it and try the other one.)  The package is called kmod-sangam-atm-annex-a or kmod-sangam-atm-annex-b.

I suppose selecting the br2684ctl package doesn't automatically select an atm driver, because there are multiple drivers to choose from.

If you can't download them from the router (because you can't get your PPPoE session running smile) you should be able to download them manually from the place you got the image from:
kmod-sangam-atm-annex-a
kmod-sangam-atm-annex-b

Then copy them to /tmp on the router and run "ipkg install /tmp/kmod-sangam-atm-annex-a_2.6.23.1+07.02.01.00-ar7-1_mipsel.ipk" to install.

Ah perhaps an hope smile
I tried to install both but it depends on kmod-atm, I found one but it's for a previous version of the kernel (I have .23 and it's for .22). I used this http://downloads.openwrt.org/people/nic … /packages/ but I think the version on webalice will work, won't it ? How did you find packages at webalice ? I cannot access to the folder.

Installing kmod-atm (2.6.22.1-ar7-1) to root...
Nothing to be done
An error ocurred, return value: 1.
Collected errors:
ERROR: Cannot satisfy the following dependencies for kmod-atm:
         kernel (=2.6.22.1-ar7-1)
root@OpenWrt:/tmp# uname -a
Linux OpenWrt 2.6.23.1 #1 Tue Jan 1 15:32:51 CET 2008 mips unknown

Thank you for your help.

(Last edited by jamesbch on 17 Feb 2008, 10:32)

CONNECTION ETABLISHED ! OH YEAH !

Oh man big thanks! My hero Wodin, well done smile I made the bridge and it works on my computer too.
Last small probleme, the kernel module in kmod-sangam-atm-annex-b isn't loading at startup, so I must reinstall it to make it work. Anyway I'm glad this finally works !

BIG thank you again !

PS: It seems to be solved.

(Last edited by jamesbch on 19 Feb 2008, 20:45)

The discussion might have continued from here.