From owner-freebsd-security Tue Feb 18 13:46:39 2003 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9671C37B401 for ; Tue, 18 Feb 2003 13:46:36 -0800 (PST) Received: from chopin.familyconnect.com (chopin.familyconnect.com [65.69.103.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id A189343FAF for ; Tue, 18 Feb 2003 13:46:35 -0800 (PST) (envelope-from brad@s4f.com) Received: from blhdev (unverified [65.69.103.75]) by chopin.familyconnect.com (Vircom SMTPRS 1.4.232) with SMTP id for ; Tue, 18 Feb 2003 15:46:35 -0600 From: "Brad Holman" To: Subject: re: ipfw ecn issue(s) Date: Tue, 18 Feb 2003 15:46:36 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org According to the REL notes for v5.0R (http://www.freebsd.org/releases/5.0R/DP1/relnotes-i386.html), there is a fix incorporated for the issue: "ipfw(4) now filters correctly in the presence of ECN bits in TCP segments." Is there a patch for version 4.x that can fix the problem without having to upgrade? Brad Technical Support S4F, Inc. 918.524.1010 support@s4f.com ** We are proud to introduce the S4F FilterCube hardware filtering solution. Call our sales dept. today for details. ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message