From owner-freebsd-questions  Wed Jun 14 02:22:31 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id CAA26055
          for questions-outgoing; Wed, 14 Jun 1995 02:22:31 -0700
Received: from zap.zap.qc.ca (zap.zap.qc.ca [198.168.127.8])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA26039
          for <questions@freebsd.org>; Wed, 14 Jun 1995 02:22:24 -0700
Received: (from fortin@localhost) by zap.zap.qc.ca (8.6.9/8.6.6) id FAA01240; Wed, 14 Jun 1995 05:22:03 -0400
From: Denis Fortin <fortin@zap.zap.qc.ca>
Message-Id: <199506140922.FAA01240@zap.zap.qc.ca>
Subject: Re: pppd failure on Freebsd 2.0 (cdrom)
To: wolperte@knox.pcec.philips.com (ED WOLPERT)
Date: Wed, 14 Jun 1995 05:22:02 -0400 (EDT)
Cc: questions@freebsd.org
In-Reply-To: <9506131147.AA21884@eis16.philips.com> from "ED WOLPERT" at Jun 13, 95 07:47:30 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 1217      
Sender: questions-owner@freebsd.org
Precedence: bulk

> I've been running [...] the 2.0 cdrom version.
> The connection [...] have been very reliable.
> However, have a few minutes of using pppd for connection to a cisco router,
> the system panics... at the pppd process.

2.0 PPP had a major problem that can be fixed with a one-line fix in 
the kernel.  

Here's the patch (apply in /sys/net):

---------------------------------snip------------------------------
*** if_ppp.c.orig	Tue Nov 22 07:38:43 1994
--- if_ppp.c	Tue Nov 22 07:39:17 1994
***************
*** 432,437 ****
--- 432,438 ----
  	    m_freem(m0);
  	    return (ENOBUFS);
  	}
+ 	m->m_len = 0;
  	if (uio->uio_resid >= MCLBYTES / 2)
  	    MCLGET(m, M_DONTWAIT);
  	len = M_TRAILINGSPACE(m);
---------------------------------snip------------------------------

Back when we ran 2.0 on a very busy PPP server, we had a few other, more
intricate, problems with it that would make me recommend 2.0.5 instead of
2.0, but if you've been running 2.0 happily with SLIP, then this little 
fix will let you get back the stability you used to have!
-- 
Denis Fortin                                                    fortin@acm.org
DMR Group Inc, (514) 877-3301                        These opinions are my own