From owner-freebsd-ipfw Sat Dec 8 4:57:39 2001 Delivered-To: freebsd-ipfw@freebsd.org Received: from palraz.rem.cmu.edu (PALRAZ.REM.CMU.EDU [128.237.161.212]) by hub.freebsd.org (Postfix) with ESMTP id EFB4137B405 for ; Sat, 8 Dec 2001 04:57:36 -0800 (PST) Received: from palraz.wburn (palraz [192.168.1.1]) by palraz.rem.cmu.edu (8.11.6/8.11.4) with ESMTP id fB8CvYl10641 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Sat, 8 Dec 2001 07:57:36 -0500 (EST) (envelope-from dpelleg@palraz.rem.cmu.edu) Received: (from dpelleg@localhost) by palraz.wburn (8.11.6/8.11.6) id fB8CvYq13301; Sat, 8 Dec 2001 07:57:34 -0500 (EST) (envelope-from dpelleg) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15378.3646.123303.804870@palraz.wburn> Date: Sat, 8 Dec 2001 07:57:34 -0500 To: freebsd-ipfw@freebsd.org Subject: incorrect handling of limit rules X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid From: Dan Pelleg Reply-To: Dan Pelleg Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have posted a PR detailing incorrect handling of parent rules in ipfw. It's long, so I won't post it here. Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=32600 Summary: incorrect handling of the expire and count field in parent rules caused ipfw to emit "OUCH! cannot remove rule" messages. While fixing this, I stumbled on a kernel panic bug, which was hidden by the more benign bug. PR includes patches for both bugs, as well as a similar fix to userland ipfw and plugging of a minor problem to do with the rule list passed to userland ipfw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message