Micah
Feb 5 08:25:11 localhost kernel: Appletalk 0.17 for Linux NET3.035 Feb 5 08:50:25 localhost kernel: CSLIP: code copyright 1989 Regents of the University of California Feb 5 08:50:25 localhost kernel: PPP: version 2.2.0 (dynamic channel allocation) Feb 5 08:50:25 localhost kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc. Feb 5 08:50:25 localhost kernel: PPP line discipline registered. Feb 5 08:50:25 localhost kernel: registered device ppp0 Feb 5 08:52:25 localhost kernel: PPP: ppp line discipline successfully unregistered Feb 5 08:52:47 localhost kernel: PPP: version 2.2.0 (dynamic channel allocation) Feb 5 08:52:47 localhost kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc. Feb 5 08:52:47 localhost kernel: PPP line discipline registered. Feb 5 08:52:47 localhost kernel: registered device ppp0 Feb 5 08:54:47 localhost kernel: PPP: ppp line discipline successfully unregistered Feb 5 08:57:50 localhost kernel: CSLIP: code copyright 1989 Regents of the University of California Feb 5 08:57:50 localhost kernel: PPP: version 2.2.0 (dynamic channel allocation) Feb 5 08:57:50 localhost kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc. Feb 5 08:57:50 localhost kernel: PPP line discipline registered. Feb 5 08:57:50 localhost kernel: registered device ppp0 Feb 5 08:59:49 localhost kernel: PPP: ppp line discipline successfully unregistered ........ Feb 5 09:14:45 localhost kernel: CSLIP: code copyright 1989 Regents of the University of California Feb 5 09:14:45 localhost kernel: PPP: version 2.2.0 (dynamic channel allocation) Feb 5 09:14:45 localhost kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc. Feb 5 09:14:45 localhost kernel: PPP line discipline registered. Feb 5 09:14:46 localhost kernel: registered device ppp0 Feb 5 09:16:44 localhost kernel: PPP: ppp line discipline successfully unregistered
Ray Olszewski wrote:
The most likely cause of this behavior is that the system on the other end
drops you after some amount of idle time. But this is only a guess. To see
what's really going on, review the *complete* log of *one* pppd session (one
that experiences the idle timeout, of course) in /var/spool/messages . If
you don't have the experience to do this yourself, post a follow-up message
to the list with the log entries and, possibly, I or someone else will be
able to help you interpret them.At 05:21 AM 2/5/99 -0500, Micah Ferrell wrote:
>I have RH 5.2 with KDE on my Linux box. I am trying to use kppp to get an
internet
>connection up and running but, I am having problems. My connection goes "idle
>time-out". I am using PAP. What could be causing this? Do I need a log in
script
>when I use PAP? I have looked at the help files that came with KDE on using
kppp
>and, have implemented there solutions. Thanks in advance.------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
