From owner-freebsd-hackers Mon Jan 17 7:31:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 42DBE14C1E for ; Mon, 17 Jan 2000 07:31:44 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id KAA15164 for ; Mon, 17 Jan 2000 10:37:21 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Mon, 17 Jan 2000 10:37:21 -0500 (EST) From: Charles Youse To: freebsd-hackers@freebsd.org Subject: PR kern/15656 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In this PR, regarding IP header checksums, it's stated that a checksum of 0 is specified by the standard to be transmitted as all-1s (0xFFFF). (A checksum of all 0s is taken to mean that the transmitting host did not calculate a checksum.) Can anyone find a reference to this in the official docs, or perhaps find an explanation why we do indeed send 0'ed checksums? I've replicated this behavior on both 3.4-STABLE and 4.0-CURRENT, i386 and alpha. Thanks, Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message