From owner-freebsd-hackers Sun Jun 8 21:17:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA02924 for hackers-outgoing; Sun, 8 Jun 1997 21:17:20 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA02908 for ; Sun, 8 Jun 1997 21:17:13 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id FAA08889; Mon, 9 Jun 1997 05:16:41 +0100 (BST) Message-Id: <199706090416.FAA08889@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Lenzi, Sergio" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pppd & natd problem turnaround.. In-reply-to: Your message of "Mon, 09 Jun 1997 00:49:34 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Jun 1997 05:16:40 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hello all. > > I have seen some messages dealing with pppd & natd panicing FreeBSD 2.2 > systems. > > The problem arises when a negative m->m_len value is reveived in function > pppfcs in module sys/net/ppp_tty.c > > A turnaround is to replace m_len to ZERO whenever is less then zero. > > I know it is not the best, but it works for now. > > Here is the patch. [.....] I've updated it to -current and 2.2. Thanks. As you say, it prevents a panic ! > > Sergio Lenzi. > > Unix consult. > -- Brian , Don't _EVER_ lose your sense of humour....