Clifford Kite wrote:
> Note several things that I found:
> 1. The "persist" option is buggy, at least in pppd 2.3.3. Hence
> the explicit "nopersist" on the command-line and the
> requirement to restart pppd if it exits.
Aha! At last! This appears to be the first time someone else has
mentioned suffering from the "other bug" in pppd that I mentioned
before. I have a fix which although I've only used with 2.3.5, should be
relatively easy to put into 2.3.3. But first, let me describe the
problem that I've fixed.
Symptoms:
1st dialup in demand mode works fine. If connection is terminated by a
request from peer (i.e. ISP times connection out), then next connection
attempt will fail after end of chatscript, when LCP negotiation etc.
should begin. Depending on debug level, you may get a message from pppd
"LCP: up event in state 1" (or was it 3? I can't remember offhand, as I
don't get it any more ;). After holdoff period has elapsed, next dialup
attempt will succeed.
If this describes the problem you were having with demand (& implied
persist) mode, then I'll post the fix (for ppp 2.3.5, but like I said, I
expect 2.3.3 to be pretty similar).
Alternative workaround is to reduce your idle timeout to be less than
your ISPs idle timeout, so as to ensure that it's always you that
initiates the termination. Or, if your ISP allows it, increase their
idle timeout and set yours to whatever you want.
--
Nick Phillips ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
