From owner-freebsd-net Wed May 20 02:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28207 for freebsd-net-outgoing; Wed, 20 May 1998 02:37:29 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA28042 for ; Wed, 20 May 1998 02:36:18 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA11373; Wed, 20 May 1998 09:47:35 +0200 From: Luigi Rizzo Message-Id: <199805200747.JAA11373@labinfo.iet.unipi.it> Subject: Re: struct ifnet handling... To: julian@whistle.com (Julian Elischer) Date: Wed, 20 May 1998 09:47:35 +0200 (MET DST) Cc: eivind@yes.no, kjc@csl.sony.co.jp, net@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at May 20, 98 00:31:34 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > where there were logical splits, based on an automated transform of > > rules. These differences _are_ there, no matter what - there are > > those 6 classes of rules (at least). > > > > BTW: The concept of 'chains' are used on the Ciscos (there called > > 'rule lists' IIRC). > > what's so difficult about: > 100 [common rules always done] Nothing :) I think it is only a matter of naming (witnessed by the "rule list" name used by cisco) and perhaps of having some default demux/mux of 'chains' (but that could give a loss of flexibility for no real performance advantage). luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message