Michael Collard <quadfour@iinet.net.au> wrote:
> I have a problem with a dialin setup I'm using. I do have the actual
> dialin session working and traffic is going backwards and forwards,
> however if the connection ends for any reason then pppd is left behind
> doing squat.

> I am using PPP 2.4.1 provided with Mandrake 9.2. I use this for my PPPoE
> connection without any problem whatsoever.

> The last bit of my log looks like:

> Jun 9 22:13:05 natalie pppd[26963]: using channel 84
> Jun 9 22:13:05 natalie pppd[26963]: Using interface ppp1
> Jun 9 22:13:05 natalie pppd[26963]: Connect: ppp1 <--> /dev/tts/0
> Jun 9 22:13:05 natalie pppd[26963]: sent [LCP ConfReq id=0x2 <mru 1432>
> <asyncmap 0x0> <auth pap> <magic 0x28ba878a> <pcomp> <accomp>]
> Jun 9 22:13:17 natalie last message repeated 4 times
> Jun 9 22:13:18 natalie pppd[26963]: Hangup (SIGHUP)
> Jun 9 22:13:18 natalie pppd[26963]: Modem hangup
> Jun 9 22:13:18 natalie pppd[26963]: Connection terminated.

This is not a disconnection during a working PPP session. It looks
like the other side abruptly hungup without starting it's PPP. But in
the case of an abrupt hangup at any stage I don't think there's any
way other to terminate pppd other than kill -9. Does "for any reason"
include one that does *not* involve an abrupt hangup? If so then show
us a log of the debug messages for such a session. And, please, NOT
hand-copied messages.

What bothers me is the /dev/tts/0 that appears in the output above. That
should read /dev/pts/0, or /dev/pts/<some integer> . I suppose Mandrake
could have mangled things and created /dev/tts but it's very doubtful that
it would be used by pppd. But if "looks like" means you hand-copied the
messages then that might explain it. In fact, comparing this with my
own logs strongly implies that it *is* a hand-copy. I'd expect a line
with "Using interface ppp1" before the "Connect" line and a 1-second
delay between the "Connect" and the first LCP request.

> I read through the PPP, Modem & dialin howtos and scoured usenet for
> someone else that has actually solved this problem. If it will help
> anyone, when pppd does mention it hangs up the /var/run/ppp1.pid file
> dissapears.

That's surprising; I'd expect the PID file to be around after an abrupt
hangup. Or does "it hangs up" mean that it is pppd that actually hangs
up, after closing the PPP session?

--
Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/