From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 22 Dec 1998 14:07:38 +1100
Message-Id: <199812220307.OAA04223@tango.anu.edu.au>
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
CC: linuxppc-dev@lists.linuxppc.org
In-reply-to: 
	<Pine.LNX.4.03.9812212249030.5317-100000@mercator.cs.kuleuven.ac.be>
	(message from Geert Uytterhoeven on Mon, 21 Dec 1998 22:49:55 +0100
	(CET))
Subject: Re: TCPv4 checksum errors
Reply-to: Paul.Mackerras@cs.anu.edu.au
References: <Pine.LNX.4.03.9812212249030.5317-100000@mercator.cs.kuleuven.ac.be>
Sender: owner-linuxppc-dev@lists.linuxppc.org
List-Id: <linuxppc-dev@lists.linuxppc.org>


Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:

> There must be a bug left in the TCPv4 checksum code. Linux/PPC still sends
> out packets with bad checksums. Any TCP checksum experts listening?

I have tried Dave Miller's checksum test program on the PPC inet
checksum code and it didn't find any errors.  Do you have an example
of a specific packet with a bad checksum generated by Linux/PPC?

Paul.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]