From owner-freebsd-hackers Wed Aug 14 10:19:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15264 for hackers-outgoing; Wed, 14 Aug 1996 10:19:48 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA15258; Wed, 14 Aug 1996 10:19:45 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA13898; Wed, 14 Aug 1996 10:19:13 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma013896; Wed Aug 14 10:19:13 1996 Message-ID: <32120A61.31DFF4F5@whistle.com> Date: Wed, 14 Aug 1996 10:18:25 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: sos@freebsd.org CC: "archie Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: ipfw vs ipfilter? References: <199608141303.PAA13221@ra.dkuug.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sos@freebsd.org wrote: > > In reply to Jordan K. Hubbard who wrote: > I'm all for it !! > It leaves the question what to do with julian's redirect code ?? > It shares much of the same "features" that ipfw does, and for all I care > it can go as well.. Most of the features with it is now in ipfilter... > Actually it's archie's code, but we really need it.. and I think I can make a good argument for giving the capacity to use user-land agents for complicated packet processing. Possibly we can add a "divert' to ipfilter and get darren to accept it back.. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > So much code to hack -- so little time.