From owner-freebsd-hackers  Thu Nov 27 11:12:05 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA15878
          for hackers-outgoing; Thu, 27 Nov 1997 11:12:05 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from ns1.yes.no (ns1.yes.no [195.119.24.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15864
          for <hackers@FreeBSD.ORG>; Thu, 27 Nov 1997 11:12:01 -0800 (PST)
          (envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36])
	by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA05434;
	Thu, 27 Nov 1997 19:11:58 GMT
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.6/8.8.6) id UAA12968;
	Thu, 27 Nov 1997 20:11:50 +0100 (MET)
Date: Thu, 27 Nov 1997 20:11:50 +0100 (MET)
Message-Id: <199711271911.UAA12968@bitbox.follo.net>
From: Eivind Eklund <perhaps@yes.no>
To: Jaye Mathisen <mrcpu@cdsnet.net>
CC: hackers@FreeBSD.ORG
In-reply-to: Jaye Mathisen's message of Wed, 26 Nov 1997 18:43:55 -0800 (PST)
Subject: Re: How many rules maximum in ipfw?  Oh wait, comment...
References: <Pine.NEB.3.95.971126183425.5824U-100000@mail.cdsnet.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Oh wait, better check ipfw.  Yep, there it is, in list(ac,av). It
> statically sets it to 1024...  Perhaps this can be raised to a higher
> number in the source tree, or maybe user-definable as listed above, or
> maybe a command-line parameter?  I'll hack it, just somebody tell me what
> makes the most sense.

IMHO: Dynamic allocation.  ipfw shouldn't limit the number of rules;
if anything should be allowed to limit this, it should be the kernel.

Eivind.