From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 19:41:36 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 D64D216A4CE for ; Fri, 20 Aug 2004 19:41:36 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86C0443D45 for ; Fri, 20 Aug 2004 19:41:36 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i7KJfXJt006575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Aug 2004 15:41:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i7KJfQI8004758; Fri, 20 Aug 2004 15:41:26 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16678.21478.381551.833252@grasshopper.cs.duke.edu> Date: Fri, 20 Aug 2004 15:41:26 -0400 (EDT) To: "David W. Hankins" In-Reply-To: <20040820190525.GA21626@isc.org> References: <20040820190525.GA21626@isc.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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:41:37 -0000 David W. Hankins writes: > > 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 caught > my eye. <...> > Client machine is amd64, running 64-bit mode 5-current fresh as of > yesterday. Network interface is e1000, so fxp. Server is also freebsd e1000 is actually em. 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. See this thread: http://lists.FreeBSD.org/pipermail/freebsd-net/2004-August/004703.html Drew