Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

jeanmichel.123

I just find a relation between the bad checksum and lenth:

I have seen:
bad checksum: 5a1c , when Len is 120
bad checksum: 5f58 , when Len is 1460
bad checksum: 5e1c , when Len is 1144
bad checksum: 5a28 , when Len is 132

This seams to mean that:

checksum= 0x59A4 + Len

but why on earth do I have this bug?

Reply | Threaded
Open this post in threaded view
|

Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

Steinar H. Gunderson
On Fri, Jul 07, 2006 at 08:53:49PM +0200, [hidden email] wrote:
> I just find a relation between the bad checksum and lenth:

You are putting way too much weight on the checksum. Ethereal's idea of the
outgoing checksum is _wrong_ when you have checksum offloading enabled (and
you probably do), so this is irrelevant unless it's also happening to the
_incoming_ packets.

/* Steinar */
--
Homepage: http://www.sesse.net/


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]