Date: Sun, 8 Feb 2009 13:18:57 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Danny Braniss <danny@cs.huji.ac.il> Cc: Peter Jeremy <peter@vk2pj.dyndns.org>, freebsd-stable@freebsd.org Subject: Re: impossible packet length ... Message-ID: <alpine.BSF.2.00.0902081318000.89719@fledge.watson.org> In-Reply-To: <E1LW9WA-0003Fu-O4@kabab.cs.huji.ac.il> References: <E1LW5Ht-0000VH-D8@kabab.cs.huji.ac.il> <20090208091656.GA31876@test71.vk2pj.dyndns.org> <E1LW60v-0000zC-B2@kabab.cs.huji.ac.il> <20090208104253.GB31876@test71.vk2pj.dyndns.org> <alpine.BSF.2.00.0902081252300.1129@fledge.watson.org> <E1LW9WA-0003Fu-O4@kabab.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Feb 2009, Danny Braniss wrote: > looking at the bce source, it's not clear (to me :-). If errors are detected > in bce_rx_intr(), the packet gets dropped, which I would expect to be the > treatment of an offloded chekcum error, but it seems that is not the case. I think we're thinking of different checksums -- devices/device drivers drop frames with bad ethernet checksums, but not IP and above layer checksums. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0902081318000.89719>