Re: Homer has the ppp blues :-(
On Wed, 16 Apr 1997, Jens B. Jorgensen wrote:
> Mark Phillips wrote:
> > As I already explained, pppd has a nasty habit of thinking the link is
> > dead when it isn't really. With the old setup, the "persist" option
> > simply told pppd to renegotiate "handshaking" with the ppp process at the
> > other end. With the new setup, pppd first runs the chat script and of
> > course this doesn't work as the modem link is already up, hence it never
> > gets to renegotiate the handshaking.
>
> At any rate, when you say "pppd has the nasty habit of
> thinking the link is dead when it isn't" do you mean that pppd
> determines that the link is down and then exits? And the modem
> connection stays up? Why don't you turn on debugging for pppd and
> post the log trace here. We can probably fix this problem.
Yes, this is what I mean. I have turned on debugging. There seems
to be several relevant log files namely: "messages", "ppp.log", "debug".
The first two seem to give the most complete information, but let me
know if you need anything else.
Last night the problem occured again - I will include the log from ppp.log
below. As you will see, pppd thinks it has received a Hangup (SIGHUP)
even though there hasn't been one (or shouldn't have been on). When it
tries to connect with chat again, it fails because all it receives from
the other end is ppp stuff.
"ppp.log":
Apr 17 23:31:22 destiny pppd[13467]: local IP address 129.96.250.162
Apr 17 23:31:22 destiny pppd[13467]: remote IP address 129.96.250.16
Apr 17 23:31:41 destiny pppd[13467]: Hangup (SIGHUP)
Apr 17 23:31:41 destiny pppd[13467]: Modem hangup
Apr 17 23:31:41 destiny pppd[13467]: Connection terminated.
Apr 17 23:31:42 destiny chat[13780]: abort on (BUSY)
Apr 17 23:31:42 destiny chat[13780]: abort on (NO CARRIER)
Apr 17 23:31:42 destiny chat[13780]: abort on (VOICE)
Apr 17 23:31:42 destiny chat[13780]: abort on (NO DIALTONE)
Apr 17 23:31:42 destiny chat[13780]: send (ATDT82015010^M)
Apr 17 23:31:42 destiny chat[13780]: expect (name:)
Apr 17 23:32:27 destiny chat[13780]:
~!E^@^@(8^O@^@r^FC*P^Q@^A^A`z"^Z^K^D*{^](Sx9^O.P^Q"^X6^W^@^@X#~
Apr 17 23:32:27 destiny chat[13780]: alarm
Apr 17 23:32:27 destiny chat[13780]: send (^M)
Apr 17 23:32:27 destiny chat[13780]: expect (name:)
Apr 17 23:33:12 destiny chat[13780]:
~!E^@^@(^TI@^@r^FgpP^Q@^A^A`z"^Z^K^D*{^](Sx9^O.P^Q"^X6^W^@^@IV~
Apr 17 23:33:12 destiny chat[13780]: alarm
Apr 17 23:33:12 destiny chat[13780]: Failed
Apr 17 23:33:12 destiny pppd[13467]: Connect script failed
P.S. This problem doesn't seem to happen all the time. Sometimes the
connection stays up fine.
-----------------------------------------------------------------------------
Mark Phillips mark@maths.flinders.edu.au
"They told me I was gullible ... and I believed them!"
-----------------------------------------------------------------------------
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: