netdev - Re: e1000 tcp checksum incorrect, x86 64b

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46FD2D3B.4050605@hp.com>
Date:	Fri, 28 Sep 2007 09:35:07 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Jon Smirl <jonsmirl@...il.com>, netdev@...r.kernel.org
Subject: Re: e1000 tcp checksum incorrect, x86 64b

Herbert Xu wrote:
> Jon Smirl <jonsmirl@...il.com> wrote:
> 
>>App is writing seven bytes to the socket. Socket write timeout expires
>>and the seven bytes are sent. The checksum is not getting inserted
>>into the packet. It is set to a constant 0x8389 instead of the right
>>value.  App is gmpc 0.15.4.95, Revision: 6794
>>
>>Attached Wireshark packet trace show the problem. e1000 is 192.168.1.4
>>64bit, Q6600. Dell Dimension 9200
> 
> 
> Wireshark is broken.  It needs to know TP_STATUS_CSUMNOTREADY
> means that the checksum is partial and will only be completed
> when the hardware sends the packet out.
> 
> Alternatively disable checksum offload with ethtool.

Or take the packet traces "outboard" of the NIC somewhere/somehow.

What problem(s) led to your taking the packet trace in the first place?

rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html