[lug] pppd dropping after connection

[Elyse Grasso]

I'll check syslog. It's not a top priority now that kppp is connecting for 
me, but it would be nice to understand what was going on.

On Thursday 28 March 2002 12:38 am, you wrote:
> I had a situation similar to this a few days ago, and I'll bet this will
> help:  check out the /var/log/syslog file instead of /var/log/messages.
> In my case, the problem was not evident from looking at messages, but was
> totally obvious (well, sort of) from looking at syslog.  In my case, it
> was because of a kernel compile, and I had forgotten to add the "async
> serial" option in the kernel config.  When pppd went looking for that
> particular character device, modprobe tried to load it and failed, leading
> to a SIGTERM sent to pppd.
> 
> This was the line in syslog:
> modprobe: modprobe: Can't locate module tty-ldisc-3
> 
> I say it was sort of obvious because to realize that it was the ppp_async
> module that was needed, I had to look in /etc/modules.conf and see the
> line:
> alias tty-ldisc-3       ppp_async
> 
> I wouldn't like to claim that I knew to do that, but actually I figured it
> out from a Google search.  Long live Google!
> 
> 
>  On Wed, 27 Mar 2002, Elyse Grasso wrote:
> 
> > In the process of switching ISPs to frii.com. Trying to log in using 
wvdial.
> > Things connect far enough that I'm given an ip address, then it announces
> > that pppd has died (once with error code 13, once with error code 2) and 
that
> > it is redialing. The redials don't get as far before they fail
> >
> > In /var/log/messages, it seems to get to a line that says
> >  Connect: ppp0 <--> /dev/ttyS1
> > sometimes followed by
> >  Remote message: Request Denied
> >  PAP authentication failed
> > before it bails.
> >
> > The successful connection to my old ISP goes on from there with  lines 
about
> > compression modules, default routes, ip and dns addresses, etc.
> >
> > FRII says the connection is being authenticated or I wouldn't see the 
message
> > about the ip address in the command line window (which is confusing when
> > compared to the message log). Is it possible that it is actually the
> > compression negotiation that is failing sometimes?
> >
> > Any suggestions for ways to track this down?
> >
> > Thanks
> > Elyse
> >
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
>