> I have noticed the following error showing up in the log file lately. I
> have seen it with 2.1.[17,18] for sure and possibly before them as well.
> It has only happend sporadicaclly and is not something that I think I can
> repeat predictably. There is usually 100's of copies of the error in the
> messages log file, too.
>
> Dec 29 16:11:53 bridger kernel: TCPv4 bad checksum from 51fe0298:d221 to
> 3228a3cd:0426, len=730/730/750
>
> Any thoughts?
>
> Thanks,
> Mike
I had a similar concern that it might have been something wierd with my
connection. Someone, Alan Cox, I believe, responded and said it was
basically a normal debugging message that's in use for the 2.1.x kernels,
and it basically means that something got corrupted on its way to your
machine.
I got sick of it too, so I wrote a small and extremely simple patch. All
it does is change two lines to comment out that part of the tcpv4 code.
Obviously, I've been using it here with no problems and there's no reason
why it wouldn't be safe, but the standard disclaimer applies.
--- linux/net/tcp_ipv4.c Wed Dec 18 22:51:02 1996
+++ linux/net/tcp_ipv4.c Thu Dec 19 19:26:47 1996
@@ -1007,9 +1007,9 @@
case CHECKSUM_HW:
if (tcp_v4_check(th,len,saddr,daddr,skb->csum)) {
struct iphdr * iph = skb->nh.iph;
- printk("TCPv4 bad checksum from %08x:%04x to %08x:%04x, len=%d/%d/%d\n",
+ /* printk("TCPv4 bad checksum from %08x:%04x to %08x:%04x, len=%d/%d/%d\n",
saddr, ntohs(th->source), daddr,
- ntohs(th->dest), len, skb->len, ntohs(iph->tot_len));
+ ntohs(th->dest), len, skb->len, ntohs(iph->tot_len)); */
goto discard_it;
}
default:
-- Good government. Good government. Sit. Stay.