> Hi,
>
> Since 2.1.127 or thereabouts, I've noticed lots of "TCPv4 bad checksum"
> errors in my kernel logs. This is over a PPP connection.
>
> I know that there are supposed to be bugs with some ISPs VJ header
> compression, so I disabled it at the Linux end with "novj".
> Unfortunately, there are still checksums errors with VJ header
> compression disabled. :-(
I've also got this with 2.1.129 - infact during 16hrs of uptime i had
generated quite a bit of this in the dmesg file.
I dont know why.. I didnt have that with the 2.0.xx kernels at all.
unfortuantly i get most of them from my ISP's promaray and secondry web
proxies and the mail server.. (mail server isnt a problem really seeing
most mail is handled directly as per MX rules)
Anyone have a clue what this means
an example clip:
TCPv4 bad checksum from 141.224.128.14:0017 to 203.31.83.230:0413,
len=248/248/268
TCPv4 bad checksum from 141.224.128.14:0017 to 203.31.83.230:0413,
len=20/20/40
TCPv4 bad checksum from 203.60.16.2:0016 to 203.31.83.230:03ff,
len=44/44/64
TCPv4 bad checksum from 203.60.16.2:0758 to 203.31.83.230:0019,
len=544/544/564
TCPv4 bad checksum from 203.60.16.2:0758 to 203.31.83.230:0019,
len=297/297/317
TCPv4 bad checksum from 150.203.164.44:7345 to 203.31.83.230:0019,
len=257/257/277
Regards, Jim.
_____________________________________________________________________________
__ name: james woodward (jim)
/ . _ _ email: jim@jim.southcom.com.au, jim@woodward.southcom.com.au
(_/ / / \/ ) www: http://jim.southcom.com.au, http://www.mailbag.ml.org
+---------------------------------------------------------------------------+
| The e-mail address of this message is copyright. If you use them for |
| inappropriate spamming, you agree to pay $5,000 to James Woodward for |
| every act of misuse and unauthorized reproduction without permission. |
+---------------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/