From owner-freebsd-current Sun May 9 14:18:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 5F9E9151E5 for ; Sun, 9 May 1999 14:18:34 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id WAA13390; Sun, 9 May 1999 22:15:20 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA10725; Sun, 9 May 1999 22:14:58 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905092114.WAA10725@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: ppp is totally broken In-reply-to: Your message of "Sat, 08 May 1999 22:34:10 CDT." <19990508223410.A1526@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 May 1999 22:14:57 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I'm using the 3.1R PPP right now, until the problem is > resolved. I'm sending a problem report, as well. It should be resolved now. A NULL mbuf value is valid - it just means that there's nothing in it. I changed fsm_Input() with the last commits, and didn't notice the MBUF_CTOP(bp) calls that you pointed out :-( MBUF_CTOP is now more robust, as are all the fsm functions and mbuf_Prepend() (which would have died when doing protocol rejects). > -- > Chris Costello > RAM DISK is not an installation procedure! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message