From owner-freebsd-stable@FreeBSD.ORG  Wed Dec 13 11:10:08 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 158F116A40F
	for <freebsd-stable@freebsd.org>; Wed, 13 Dec 2006 11:10:08 +0000 (UTC)
	(envelope-from max@love2party.net)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.177])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8536743CD5
	for <freebsd-stable@freebsd.org>; Wed, 13 Dec 2006 11:08:09 +0000 (GMT)
	(envelope-from max@love2party.net)
Received: from [88.64.181.134] (helo=amd64.laiers.local)
	by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis),
	id 0MKxQS-1GuRzD0Zgz-00033o; Wed, 13 Dec 2006 12:09:20 +0100
From: Max Laier <max@love2party.net>
Organization: FreeBSD
To: Pete French <petefrench@ticketswitch.com>
Date: Wed, 13 Dec 2006 12:09:06 +0100
User-Agent: KMail/1.9.4
References: <E1GuRv7-000DHq-OI@dilbert.ticketswitch.com>
In-Reply-To: <E1GuRv7-000DHq-OI@dilbert.ticketswitch.com>
X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGd<hB5S>u+2];
	R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart3202847.nQGea5S025";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200612131209.12687.max@love2party.net>
X-Provags-ID: kundenserver.de abuse@kundenserver.de
	login:61c499deaeeba3ba5be80f48ecc83056
Cc: spork@bway.net, freebsd-stable@freebsd.org
Subject: Re: pf killing NFS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2006 11:10:08 -0000

--nextPart3202847.nQGea5S025
Content-Type: text/plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 13 December 2006 12:05, Pete French wrote:
> > As Luke already pointed out, "no-df" on the scrub rule should help.=20
> > As=3D20 for the "bad cksum!" - this is a symptom of checksumming done
> > in=3D20 hardware.  ifconfig bge1 -rxcsum -txcsum should get rid of
> > them.
>
> I am a bit concerned by this - we use a lot of bge interfaces, and I
> have hardware checksumming enabled on all of them. Are they known to
> produce bad checksums ?

You are misunderstanding.  The problem is simply that the bpf device sees=20
bad checksums as it sees the packet before the hardware has calculated=20
it.  On the receiver the checksum will be correct.

=2D-=20
/"\  Best regards,                      | mlaier@freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier@EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News

--nextPart3202847.nQGea5S025
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQBFf99YXyyEoT62BG0RAjq7AJ4zCMmm2BWOOYeJGA+GWQQwKtjVEQCeM6VL
woTg+SBqDTtmWshFmEe5JJY=
=t+II
-----END PGP SIGNATURE-----

--nextPart3202847.nQGea5S025--