From owner-freebsd-security Sun Sep 27 07:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04160 for freebsd-security-outgoing; Sun, 27 Sep 1998 07:19:50 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04152 for ; Sun, 27 Sep 1998 07:19:45 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id QAA11808; Sun, 27 Sep 1998 16:13:01 +0200 (CEST) To: andrew@squiz.co.nz cc: Heikki Suonsivu , freebsd-security@FreeBSD.ORG Subject: Re: ipfw In-reply-to: Your message of "Mon, 28 Sep 1998 01:59:47 +1200." Date: Sun, 27 Sep 1998 16:13:00 +0200 Message-ID: <11806.906905580@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Andrew McNaughton writes: >On Sun, 27 Sep 1998, Heikki Suonsivu wrote: > >> Date: Sun, 27 Sep 1998 15:16:42 +0300 (EEST) >> From: Heikki Suonsivu >> To: freebsd-security@FreeBSD.ORG >> Subject: ipfw >> >> >> How much work would be to rewrite ipfw to have interface-specific lists >> instead of current global lists ? A long time ago I suggested splitting the one list we have today into several lists, specifically: * per interface input list * per interface output list * packet forwarding list * ip_input() list * ip_output() list Doing it would be simple, but people complained that configuring it would be too complex. This would save a lot of time in complex filters. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message