From owner-freebsd-net Fri Mar 19 17:21:11 1999 Delivered-To: freebsd-net@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 696FE150AA for ; Fri, 19 Mar 1999 17:21:06 -0800 (PST) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id 193D567 for ; Fri, 19 Mar 1999 19:20:46 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 01210B9 for ; Fri, 19 Mar 1999 19:20:45 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-net@freebsd.org Subject: Integrating the NetBSD PFIL hooks.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 19:20:45 -0600 From: Chris Csanady Message-Id: <19990320012046.01210B9@friley-185-205.res.iastate.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What would it take for us to intergrate NetBSD's PFIL hooks? It is hard to do much work in the current network stack with so much of the mess that currently exists. At the very least, ip_input.c and ip_output.c would be much cleaner with this mechanism. I'm just wondering what needs to be done, and if it is possible. Ipfilter would already support this, but how about ipfw, dummynet, divert and such? Would the authors of the respective code be willing to help out with the necessary changes? Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message