From owner-freebsd-net Thu Feb 21 11:25:54 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id DA9B937B404 for ; Thu, 21 Feb 2002 11:25:51 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 89859AE278; Thu, 21 Feb 2002 11:25:51 -0800 (PST) Date: Thu, 21 Feb 2002 11:25:51 -0800 From: Alfred Perlstein To: Lars Eggert Cc: net@freebsd.org Subject: Re: incorrect checksums with xl? Message-ID: <20020221192551.GG12136@elvis.mu.org> References: <3C7547E0.8050805@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C7547E0.8050805@isi.edu> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Lars Eggert [020221 11:18] wrote: > Hi, > > I'm looking at a packet trace taken of an xl card under 4.5, and I see > bad IP and TCP/UDP checksums. The release notes state that checksumming > maybe offloaded to the NIC now, but I'd still expect them to be correct > in a packet trace! > > More specifically, the IP checksum is always zero, while the TCP and UDP > checksums are non-zero but bad. However, netstat shows no packets > arriving with bad checksums, so I assume that they get mangled somewhere > in the kernel after inbound processing. (And the machine works fine on a > network; I found this by accident.) > > Any clues? I'm not 100% on this, but bpf may be queueing the packet without doing a deep copy of it? Another thing may be that the card performs the checksum but uses the checksum area as a scratch area? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message