From owner-freebsd-ipfw@FreeBSD.ORG Mon Jan 11 08:34:08 2010 Return-Path: Delivered-To: ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BA26106566B for ; Mon, 11 Jan 2010 08:34:08 +0000 (UTC) (envelope-from julian@elischer.org) Received: from utility-0.aerioconnect.net (utility-0.aerioconnect.net [216.240.32.11]) by mx1.freebsd.org (Postfix) with ESMTP id CA2498FC1B for ; Mon, 11 Jan 2010 08:34:07 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by utility-0.aerioconnect.net (8.13.1/8.13.1) with ESMTP id o0B7tupK032190; Sun, 10 Jan 2010 23:55:56 -0800 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id ABA012D6010; Sun, 10 Jan 2010 23:55:55 -0800 (PST) Message-ID: <4B4AD98A.2080508@elischer.org> Date: Sun, 10 Jan 2010 23:55:54 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Maxim Ignatenko References: <20091209183821.GA40814@onelab2.iet.unipi.it> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ipfw@freebsd.org, Luigi Rizzo Subject: Re: RFC: new ipfw options X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 08:34:08 -0000 Maxim Ignatenko wrote: > 2009/12/9 Luigi Rizzo : >> 3. a hash version of 'table's >> >> Right now ipfw tables are implented as routing tables, which is >> great if you have to lookup a longest matching prefix, but a >> bit overkill if you care only for ports or jail ids, and >> totally uninteresting if you want to lookup flow ids, >> or generic sequence of bytes. My plan here is to reuse the >> ipfw hash tables to make them available for 'ipfw table ...' >> commands. To avoid code and syntax bloat, I'd use the number >> 0..TABLE_MAX-1 for the existing prefix tables, and >> TABLE_MAX..2TABLE_MAX-1 for the new hash tables. >> >> comments welcome >> > > I think better use another name ('htable' for example) instead of > overloading the old one. > And thanks for great ideas. > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" please keep teh current tables for IP addresses, longes prefix matching is really hard to do right on other schemes with the same behaviour. I know, I've tried :-) the answer id to have different types of tabels I guess, but don't try combine when things should remain different.