[lkml]   [1998]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Massive TCPv4 bad checksum
In article <Pine.LNX.4.02.9810181325430.509-100000@cassiopeia.home>,
Geert Uytterhoeven <> writes:
> On Sat, 17 Oct 1998, H.J. Lu wrote:
>> I have massive TCPv4 bad checksum on my CSLIP link from
>> my CSLIP server to my machine ever since I upgraded to
>> linux 2.1.1xx. Any suggestions?

> My m68k box generates plenty of these messages when receiving packets from my
> PPC box. This would indicate a bug in the checksum code for either (or both)
> m68k and PPC.

> But I also see the message on my AXP box, when receiving packets from the PPC.
> The Intel box on our network reports no bad checksums at all. None of the
> Linux boxes report any bad checksums from the Winslows machines.

> Who's (who are?) the bad guy(s)?

Is there a systematic on what types of packets arrive with bad checksums?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:45    [W:0.078 / U:1.196 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site