From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 19:54:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA38516A4CE for ; Fri, 20 Aug 2004 19:54:23 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4FD643D48 for ; Fri, 20 Aug 2004 19:54:22 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7KJsC4U058763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Aug 2004 22:54:13 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7KJsEXN067675; Fri, 20 Aug 2004 22:54:14 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Aug 2004 22:54:13 +0300 From: Ruslan Ermilov To: Andrew Gallatin Message-ID: <20040820195413.GD57723@ip.net.ua> References: <20040820190525.GA21626@isc.org> <16678.21478.381551.833252@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EP0wieDxd4TSJjHq" Content-Disposition: inline In-Reply-To: <16678.21478.381551.833252@grasshopper.cs.duke.edu> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: "David W. Hankins" cc: current@freebsd.org Subject: Re: on amd64 tcp4 cksums are bad (FYI) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 19:54:24 -0000 --EP0wieDxd4TSJjHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 20, 2004 at 03:41:26PM -0400, Andrew Gallatin wrote: >=20 > David W. Hankins writes: > >=20 > > This is as observed via tcpdump on [client], which is what is producing > > the bad checksums. Obviously it doesn't cause a problem since no one > > listens to TCP checksums, but it's interesting. I only noticed it > > because I was tcpdump'ing for completely unrelated reasons, and it cau= ght > > my eye. >=20 > <...> >=20 > > Client machine is amd64, running 64-bit mode 5-current fresh as of > > yesterday. Network interface is e1000, so fxp. Server is also freebsd >=20 > e1000 is actually em. =20 >=20 > You're almost certainly using a driver which offloads transmit > checksums. (both fxp and em do) Since BPF sniffs the packet before it > leaves the host, the checksum has not yet been calculated, so it looks > bad. >=20 > See this thread: > http://lists.FreeBSD.org/pipermail/freebsd-net/2004-August/004703.html >=20 This should be added to FAQ. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --EP0wieDxd4TSJjHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBJlblqRfpzJluFF4RAvMtAJsG0yiLyidrdeWSGcjR31iXRQP0dACgiG0f 8647hawaIfjuQno72alwFYM= =BOFB -----END PGP SIGNATURE----- --EP0wieDxd4TSJjHq--