Bekijk de volledige versie : Timeout waiting for PADO packets
I have Asus ADSL modem in bridge mode and Asus WL500g configured for PPPoE. After reset (unplug and plug power cord) there is reported in the log file:
pppd[91]: Timeout waiting for PADO packets
pppd[91]: Unable to complete PPPoE Discovery
and this is repeated apx. 2-3 times and after apx. 3minutes it is correctly connected and all is working fine. If I make an reboot (via WWW or from command line) it is immediately connected. It means that this problem occures only after "hard reboot - power off/on"
Any ideas? Thanx for comments in advance...
I am experiencing the very same issue and also only after cold reboots. My modem is a D-Link DSL-362T.
The reason why the WL500g behaves after cold reboot in a different way is that all temporary files are lost after cold reboot. However it does not explain the reason why "Timeout waiting for PADO packets" occures. Any information is welcome.
WAN port dies? Do you've original wl500g (not deluxe)? Which firmware is currently flashed?
I have Deluxe version and the flashed firmware is the latest one:
* WL500gx-1.9.2.7-7c.zip
How can I easily check whether WAN port dies? I cannot ping the modem which is in BRIDGE mode (or do not know how)
note.: I did not experience the problems with WAN port dying. Once the router is connected there is no problem. The problem occures after cold reboot.
Hm... I see now. Does WAN port LED is green after cold reboot?
Anyway, this is not a firmware problem, this works fine for me...
WAN led _IS_ green after cold boot.
Oleg, I think that it is not a fw problem too. Anyway I would like to know if there is anybody else experiencing the same problems and probably successfuly solved it...
I am running 1.9.2.7-6b fw but on WL-500g, not Deluxe. For me this is not that critical because after a few minutes of timeouting, PPPoE finally connects and everything is fine from that moment on. However, there are people who reported that they simply couldn't make the router connect after cold reboot. The only way to connect is issuing 'reboot' over Telnet or restarting the thing via web interface.