Since upgrading to pre-2.1.90-3 I've seen some bad checksums that I
haven't seen before. Haven't seem them in anything through pre-2.1.90-2
and, although they're infrequent, I've probably sent more than enough
traffic through all the other kernels to make them creep out.
The kernel that received this is a linux-2.1.89 kernel. 132.241.60.99
and 132.241.60.36 are the same laptop (pre-2.1.90-3) in two different
locations, 132.241.60.35 is yet another computer (pre-2.1.90-3).
--- john
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mar 16 07:41:48 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.99:0400 to 132.241.82.10:0016, len=20/20/40
Mar 16 07:50:09 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.99:0016 to 132.241.82.10:0d3e, len=20/20/40
Mar 15 00:15:59 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.35:03ff to 132.241.82.10:0016, len=20/20/40
Mar 15 10:59:13 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.36:0400 to 132.241.82.10:0016, len=20/20/40
Mar 15 15:02:01 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.36:0401 to 132.241.82.10:0016, len=20/20/40
Mar 15 20:08:50 hircine kernel: <7>TCPv4 bad checksum from 132.241.60.36:0400 to 132.241.82.10:0016, len=20/20/40
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu