James, by any chance are you using your ppp-on script as the diald connect
script?  Your ppp-on script will start pppd, but when using diald it is
diald that will start pppd AFTER your diald connect script completes.  If
your connect script starts pppd the script won't finish, and then diald
will wait 60 seconds (by default, can be changed) for the connect script to
finish, and when it doesn't it will kill it and try again.

Your diald connect script should just dial the modem and login if
nessesary, nothing more.  Something like "connect '/usr/sbin/chat -f
/path/to/chatscriptfile'" in diald.conf, using chat or something similar.
When it finishes, diald will start pppd.

Hope this helps!

Mark.

At 01:54 PM 1/14/99 +0000, you wrote:
>My ppp-on script normally works perfectly, but as soon as I start diald the
>connection always fails to initiate.  Looking the logs, the passwords etc.
>are negotiated perfectly, but the ppp child process that is spawned times
>out after 55 secs... the modem hangs up and it basically doesn't work.  It
>then retries but fails consistently.
>
>
>This behaviour occurs using both my ppp-on script (normally fine), and
>automatic dialing.
>
>
>Any ideas?
>Would it help if I posted the logs?
>
>
>Thanks very much!
>- James
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-diald" in
>the body of a message to [EMAIL PROTECTED]
>


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to