🚀 go-pugleaf

In article <66i8us$bto@metro.usyd.edu.au>, David Stanaway wrote:
>
>Herbert Xu wrote in message <3489F024.4523B493@gondor.apana.org.au>...
>>What you need to do first is to enable debugging by putting "debug" and
>>"kdebug 25" into your ppp options file and watching on the right syslog
>>channels.  This will let you determine whether the underlying link is
>>working (i.e., what you put in on one end does come out on the other
>>end) and if so, whether the remote server is responding or not.
>>--
>
>
>
>Here is the relevant section in the log (I think )...
>I also attatched my ppp script, and login script .
>
>Dec  9 01:59:15 tinderbox pppd[211]: Serial connection established.
>Dec  9 01:59:16 tinderbox pppd[211]: Using interface ppp0
>Dec  9 01:59:17 tinderbox pppd[211]: Connect: ppp0 <--> /dev/cua2
>Dec  9 01:59:51 tinderbox pppd[211]: LCP: timeout sending Config-Requests
>Dec  9 01:59:51 tinderbox pppd[211]: Connection terminated.
>Dec  9 01:59:51 tinderbox pppd[211]: Exit.

You didn't use "kdebug 25", right?  Anyway, LCP-* options are in
/etc/ppp/options.  This file is well commented (at least in Debian),
have a look.  (Hint: comment LCP-* options out).

Explanation: pppd sends lcp-echo-requests at specified intervals.  Peer ppp
returns lcp-echo-replies.  If pppd doesn't receive N replies it assumes the
link is dead and terminates.  If your link is not dead, then remote ppp is 
broken -- it doesn't reply to lcp-echo-requests.

-- 
Dimitri
-------
This is the official notification that I do not wish to receive
any unsolicited commercial e-mail, so don't try.  Or else.
(Solicited advertisements <huh?> and other such can be sent to 
  emaziuk at curtin dot edu dot au)