From owner-freebsd-hackers Mon Jan 17 8:50:14 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 06F3514A31 for ; Mon, 17 Jan 2000 08:50:05 -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 LAA15302; Mon, 17 Jan 2000 11:55:37 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Mon, 17 Jan 2000 11:55:37 -0500 (EST) From: Charles Youse To: "Louis A. Mamakos" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PR kern/15656 In-Reply-To: <200001171639.LAA18994@whizzo.transsys.com> 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 On Mon, 17 Jan 2000, Louis A. Mamakos wrote: > So, if you implemented as it is described, computing a sum of the > packet contents who's result is 0x0000 would then be complemented to > 0xFFFF for inclusion in the packet header. Agreed; however, the PR states that should the checksum be 0xFFFF, the complement of which is 0x0000, the checksum should still be sent as 0xFFFF. Can anyone verify this? I can verify that BSD sends 0-checksums; I can't on Solaris. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message