Re: Massive TCPv4 bad checksum
Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Sun, 18 Oct 1998 22:12:41 +0200 (CEST)
On Sun, 18 Oct 1998, H.J. Lu wrote:
> > Geert Uytterhoeven <geert@geert.cs.kuleuven.ac.be> 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?
> >
>
> Most of the bad packets are from ftp and rsh. As the result, my
> ftp and CVS over rsh on my CSLIP link are much slower than 2.0.
Mine come mostly from ssh, and some from auth:
TCPv4 bad checksum from 10.0.24.8:03ff to 10.0.24.15:0016, len=20/20/40
TCPv4 bad checksum from 10.0.24.8:03ff to 10.0.24.4:0016, len=20/20/40
TCPv4 bad checksum from 10.0.24.8:0071 to 10.0.24.4:04e2, len=20/20/40
10.0.24.4 = m68k
10.0.24.8 = PPC
10.0.24.15 = AXP
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
-
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/