Re: Bogus 'TCPv4 Bad checksum' messages with 2.1.89? (was Re: poor performance when swapping)

Sean M. Kelly (smkelly@zombie.org)
Tue, 10 Mar 1998 21:50:32 -0600 (CST)


On Tue, 10 Mar 1998, Benjamin Redelings I wrote:

[snip]
: I haven't had that much problem with networking myself. I've got a
:33.6k modem which is usually running at 26.4 :) The only problem that I
:can obviously see is that I get a lot of 'TCPv4 bad checksum' messages
:from everybody, which I don't remember on 2.0.33. That might relate to
:your problem... or it might relate to the possibility that I have line
:noise now :) Still I'm pretty sure that I get it only from certain
:hosts.
[snip]

I too have those:
Mar 10 17:17:25 main kernel: TCPv4 bad checksum from 152.2.254.81:0014 to
206.83.79.151:0824, len=1480/1480/1500
Mar 10 17:17:26 main kernel: TCPv4 bad checksum from 152.2.254.81:0014 to
206.83.79.151:0824, len=1480/1480/1500
Mar 10 18:26:15 main kernel: TCPv4 bad checksum from 207.213.224.251:0050
to 206.83.79.151:0867, len=1196/1196/1216
Mar 10 20:16:52 main kernel: TCPv4 bad checksum from 207.213.224.251:0050
to 206.83.79.151:0bb1, len=1480/1480/1500
.........

Other than that, 2.1.89 works well for me too. I have a AMD K6-233mHz w/
64MB of ram and 40MB of swap. The only difference I've noticed is that my
free real memory is less than it used to be and my swap is being used
more, which does seem to be slightly slower.

--
Sean Kelly
smkelly@zombie.org

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu