<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1"><tt>Hi CLUEbies,<br>
<br>
I've got a weird one. We run pppd on Linux with generally very good
success. We have a 15 second lcp-echo-interval and 3 lcp-echo-failure
to detect a dead peer. I ran into a situation where the peer was dead
for several hours but pppd was running normally and sending out its lcp
echo-requests and not getting any replies, but it did not die! The
hardware is all fine. Restarting pppd made everything come back to
normal. I do not understand how pppd went off into the weeds like that.<br>
<br>
We use this command line and these options:<br>
<br>
usr/sbin/pppd /dev/ttySX 921600 nodetach 10.0.0.2:10.XX.0.1 netmask
255.255.0.0 mtu 1500 lcp-echo-interval 15 lcp-echo-failure 3<br>
<br>
ms-dns 4.4.4.4<br>
ms-dns 8.8.8.8<br>
asyncmap 0x0<br>
local<br>
crtscts<br>
noipdefault<br>
mtu 384<br>
<br>
Feb 19 02:12:36 TPC pppd[3733]: pppd 2.4.4 started by root, uid 0<br>
<br>
I did some googling and I think I am the only person in the world that
this has ever happened to. I tried looking to see what bugs were fixed
in pppd 2.4.5 but I don't have good bug tracking mojo I guess. Does
this seem like it might be a bug in pppd?<br>
<br>
Thanks,<br>
Jim<br>
</tt></font>
<pre class="moz-signature" cols="72">--
Jim Ockers, P.Eng. (<a class="moz-txt-link-abbreviated" href="mailto:ockers@ockers.net">ockers@ockers.net</a>)
Contact info: <a class="moz-txt-link-freetext" href="http://www.ockers.ca/pason.html">http://www.ockers.ca/pason.html</a>
</pre>
</body>
</html>