Date: Sun, 25 Jan 2004 13:13:28 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Robert Watson <rwatson@freebsd.org> Cc: hackers@freebsd.org Subject: Re: XL driver checksum producing corrupted but checksum-correct packets Message-ID: <20040125131053.X873@odysseus.silby.com> In-Reply-To: <Pine.NEB.3.96L.1040124220715.62871T-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040124220715.62871T-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Jan 2004, Robert Watson wrote: > To pick up the corrupted packet on the machine where the corruption is > occurring, you might want to try hooking up the UDP checksum drop case to > BPF_MTAP() for a special BPF device or rule, or have it spit them into a > raw socket (probably easier). He said that the packet's checksum passes, but it is corrupt, so this won't work. I suppose that one thing we could do in the long run to help detect this sort of corruption would be to import OpenBSD's TCP MD5 support and ensure that packets which fail the md5 or fail the checksum are logged so that they can be investigated. Of course, that's adding data to the packet, and heisenberg wouldn't be too happy about that. :) Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040125131053.X873>