OpenWrt Forum Archive

Topic: pppd Not Starting Properly

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

I have Kamikaze v8.09.1 loaded on my WRT54G-TM and I use PPPoE as required by my ISP.

The trouble I am having is that the pppd deamon is not loading correctly at boot time.
I enabled the pppd log file and trapped the below from that file which provides more details about this problem.

Plugin rp-pppoe.so loaded.
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery
System time change detected.
Terminating on signal 15

Once the router is booted I can get the link up by typing "ifup wan" at the command line but that is rather inconvenient.

So now I am hoping to learn more about what of the source of a PADO timeout might be.  Is this a boot order issue?

Hopefully someone here will know something about PPPoE and enlighten me.

Thanks,

What service? or script switches on the PPPD on your case ?
and what is its priority ?
you can put it to the very last one to start.
just as a quick fix.

look at /etc/init.d/

Hope this helps.
Regards
mohnkhan

The way I understand it /etc/rc.d/S40network has this line in the "boot()" routine:

include /lib/network

This directory includes the pppoe.sh script which starts pppd.  I am not wanting to mess with the boot order of network in init.d just yet because i am afraid that will introduce more problems.  If no further info comes to light then maybe I will go that way.

Anyway thanks for the input.

Some more specifics I have noticed.

The pppd deamon is running at boot time but the pppo interface does not come up.  Maybe a timing problem with the Modem but I am not sure.

I saw a related to this https://dev.openwrt.org/ticket/2781 but when I tried the "fix" mentioned there it did not resolve this issue.

(Last edited by pbix on 23 Jan 2010, 15:59)

the lines
>>Plugin rp-pppoe.so loaded.
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery
<<
i see when the modem has not established a contact to the ISP on ethernet level, required for the  ppp protocol to authenticate the user and get assigned an ip address and know about dns service.
As the router has no knowlege about the status of the modem the cause can be from very low level, no connection to the telephone, via no adsl signal to synchronise to, via the modem not having been set up as a bridge, to the ISP not having activated the account.

doddel wrote:

i see when the modem has not established a contact to the ISP on ethernet level, required for the  ppp protocol to authenticate the user and get assigned an ip address and know about dns service.

Possibly so.  So what's the procedure to get PPPD to try again?  The link does come up, it just seems that some sequence is not correctly being retried or initiated.

have you checked via ps whether the ppp stuff is still active ? It normally just keeps trying after a certain wait time.
What I was trying to say is that these no discovery lines indicate that the line is not up.
Log into the modem and look what is going on there. Can you ping the modem itself.? What do the management pages say about the adsl connection ?
Is the modem configured as bridge ?

This is a boot time issue.  There is no way to log into the modem at the time that pppd is starting (during boot).

All I can say is that after the boot I can login into the modem and the link is up.

Then if I do an "ifup wan" from the command line ppp0 comes up so that is again confirmation that the modem is up and working OK.

As I stated previously pppd is running and can always be seen with the ps command.
You are apparently not correct when you say that it keeps trying after this error.

My modem is in bridge mode.

The discussion might have continued from here.