From owner-freebsd-stable Tue May 7 4: 7:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from gs166.sp.cs.cmu.edu (GS166.SP.CS.CMU.EDU [128.2.205.169]) by hub.freebsd.org (Postfix) with SMTP id 0CCD137B400; Tue, 7 May 2002 04:07:28 -0700 (PDT) To: Eugene Grosbein Cc: stable@freebsd.org, luigi@freebsd.org Subject: Re: yesterday's 4.6-PRERELEASE: ipfw ... limit glitches References: <20020507134719.A3120@svzserv.kemerovo.su> From: Dan Pelleg Date: 07 May 2002 07:06:57 -0400 In-Reply-To: <20020507134719.A3120@svzserv.kemerovo.su> Message-ID: Lines: 27 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene Grosbein writes: > Hi! > > I've updated one of my servers to 4.6-PRERELEASE yesterday > and see that firewall still procudes lots of junk to console and > logs if you use 'limit' feature. That's very annoying if the server is > under moderate load. I've seen a couple of PR's about this > (f.e., kern/32600) but it's still there. > > Please consider fixing that or at least eliminate pollution of logs > before 4.6-RELEASE. It's nearly impossible to use this feature without > patching kernel now. > > Eugene Grosbein I'll second that. Last time I got any kind of reply from luigi regarding this it was about his attempt to get it into 4.5. However nothing has happened since (except for this coming up in -ipfw every once in a while). If you look at the PR you'll see that the obvious fix exposes a kernel panic bug (which I also sent a patch for). I don't know if my patch is ok or not (I know I'm using it), but either way, this PR should have been closed long ago. -- Dan Pelleg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message