From owner-freebsd-net@FreeBSD.ORG Sat Mar 4 18:00:38 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 352D916A420 for ; Sat, 4 Mar 2006 18:00:38 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: from daemon.egr.msu.edu (daemon.egr.msu.edu [35.9.44.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA7D143D46 for ; Sat, 4 Mar 2006 18:00:37 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: by daemon.egr.msu.edu (Postfix, from userid 21281) id 93A9D1CC54; Sat, 4 Mar 2006 13:00:56 -0500 (EST) Date: Sat, 4 Mar 2006 13:00:56 -0500 From: Adam McDougall To: Pieter de Boer Message-ID: <20060304180056.GC63144@egr.msu.edu> References: <20060304142802.GA63144@egr.msu.edu> <4409A975.1080108@thedarkside.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4409A975.1080108@thedarkside.nl> User-Agent: Mutt/1.5.11 Cc: net@freebsd.org Subject: Re: PR kern/93849 IP checksum broken by pf no-df over bridge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2006 18:00:38 -0000 On Sat, Mar 04, 2006 at 03:51:33PM +0100, Pieter de Boer wrote: Adam McDougall wrote: >Could someone possibly take a look at this and let me know if it >looks 'broken' or if I might be doing something wrong? I am in >a crunch to choose a firewall solution within a few weeks and it >would help me to know if this issue can be solved. FreeBSD/pf >seemed an appropriate solution so far, especially since it has >CARP, pfsync, (and altq which im not using (yet?)). You could try compiling pf using CFLAGS=-O instead of -O2. This fixed a checksum problem I had. That probably was an entirely different issue, but perhaps it does help.. -- Pieter I tried that a few days ago when I saw mention of it for sparc64, but that did not help. The patch fixed it though.