From owner-freebsd-current  Tue Jun 27 09:11:23 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id JAA19792
          for current-outgoing; Tue, 27 Jun 1995 09:11:23 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA19781
          ; Tue, 27 Jun 1995 09:10:59 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id CAA11019; Wed, 28 Jun 1995 02:10:41 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199506271610.CAA11019@asstdc.scgt.oz.au>
Subject: Re: ipfw - addf reject = panic
To: paul@freebsd.org
Date: Wed, 28 Jun 1995 02:10:38 +1000 (EST)
Cc: current@freebsd.org
In-Reply-To: <199506271539.QAA01048@freebsd.netcraft.co.uk> from "Paul Richards" at Jun 27, 95 04:39:11 pm
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 495       
Sender: current-owner@freebsd.org
Precedence: bulk

Paul Richards writes:

> The ipfw code works for me fine but using user-space PPP. I suspect
> that it is the kernel PPP code that is falling over rather than
> anything else since it was flakey in 2.0 and has since been largely
> ignored since everyones switched.

Different code .. user-mode PPP has its own internal filter functions
executed at context-switch intervals along with the rest of the protocol. 
It also currently has no facility to return ICMP unreachable indications,

	michael