From owner-freebsd-bugs Mon Mar 24 11: 0:34 2003 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0F1437B401 for ; Mon, 24 Mar 2003 11:00:31 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45E6B43FAF for ; Mon, 24 Mar 2003 11:00:31 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h2OJ0VNS068530 for ; Mon, 24 Mar 2003 11:00:31 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h2OJ0UXl068519; Mon, 24 Mar 2003 11:00:30 -0800 (PST) Date: Mon, 24 Mar 2003 11:00:30 -0800 (PST) Message-Id: <200303241900.h2OJ0UXl068519@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Coleman Kane Subject: Re: kern/50216: kernel panic on 5.0-current when use ipfw2 with dynamic rules Reply-To: Coleman Kane X-Spam-Status: No, hits=0.0 required=5.0 tests=none version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/50216; it has been noted by GNATS. From: Coleman Kane To: freebsd-gnats-submit@FreeBSD.org, lazyking@hotmail.com Cc: Subject: Re: kern/50216: kernel panic on 5.0-current when use ipfw2 with dynamic rules Date: Mon, 24 Mar 2003 13:58:46 -0500 More info: Using the following rule: allow tcp from any to me port 25 limit src-addr 10 The system will panic as stated, though having multiple clients hammer the smtp port will cause this panic in about 5 minutes or so. Only connecting repeatedly from one client doesn't seem to have this effect. On Mon, Mar 24, 2003 at 12:52:04PM -0500, Coleman Kane wrote: > I have experienced this problem as well, on three 5.0-R boxes (one an > alpha). It seems to manifest itself when using limit rules in the > firewall. I can successfully use keep-state/setup rules on all of > these machines. I have not had time to look into the source due to > work/school constraints. I figured I would put in my experience to > help out luigi or whomever else decides to hash this out. > > -- > coleman kane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message