Mark Murray wrote:
> > How long can this remain unfixed before the code is diked out,
> > and the checksum is recalculated fully, instead?
>
> Terry, you sound rather foolish when you argue like this. This
> is semantic tomfoolery and off topic. End of thread.
This is not a argument over mere implmenetation semantics.
The incremental checksum code is broken.
Bad tcpchecksum - before: 0x000038f3 after: 0x00001802
Bad tcpchecksum - before: 0x00002870 after: 0x0000e81e
Bad tcpchecksum - before: 0x00006319 after: 0x00000608
Bad tcpchecksum - before: 0x0000369a after: 0x00001212
Bad tcpchecksum - before: 0x0000d885 after: 0x00000004
The packets do not get through, no matter how many times
they are resent by the sender. The reason that the CVSup
is successful is an artifact of the CVSup retry mechanism.
People using other protocols, like FTP, or programs like
"fetch" are well and truly screwed by this bug.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
