From: Martin Costabel <costabel@wanadoo.fr>
To: Paul.Mackerras@cs.anu.edu.au
Cc: Geert.Uytterhoeven@cs.kuleuven.ac.be, linuxppc-dev@lists.linuxppc.org
Subject: Re: TCPv4 checksum errors
Date: Tue, 22 Dec 1998 08:21:22 +0100 [thread overview]
Message-ID: <367F4872.3BE5EB12@wanadoo.fr> (raw)
In-Reply-To: 199812220307.OAA04223@tango.anu.edu.au
Paul Mackerras wrote:
>
> Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:
>
> > There must be a bug left in the TCPv4 checksum code. Linux/PPC still sends
> > out packets with bad checksums. Any TCP checksum experts listening?
>
> I have tried Dave Miller's checksum test program on the PPC inet
> checksum code and it didn't find any errors. Do you have an example
> of a specific packet with a bad checksum generated by Linux/PPC?
I can get bad TCPv4 checksum errors very easily by telnetting to
dev.linuxppc.org. From /var/log/messages:
Dec 22 08:05:07 rennes-43 identd[19807]: Connection from
dev.linuxppc.org
Dec 22 08:05:12 rennes-43 identd[19807]: from: 169.207.161.2 (
dev.linuxppc.org ) for: 2526, 21
Dec 22 08:05:12 rennes-43 identd[19807]: Successful lookup: 2526 , 21 :
root.root
Dec 22 08:05:52 rennes-43 kernel: TCPv4 bad checksum from
169.207.161.2:0017 to 193.252.125.43:09df, len=20/20/40
Dec 22 08:05:55 rennes-43 kernel: TCPv4 bad checksum from
169.207.161.2:0017 to 193.252.125.43:09df, len=20/20/40
Yesterday I got them also all the time while ftping from there. Today I
didn't see this.
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-22 7:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-21 21:49 TCPv4 checksum errors Geert Uytterhoeven
1998-12-22 3:07 ` Paul Mackerras
1998-12-22 7:21 ` Martin Costabel [this message]
1998-12-22 9:21 ` Geert Uytterhoeven
1998-12-22 9:35 ` David S. Miller
1998-12-22 10:01 ` Geert Uytterhoeven
1998-12-22 10:11 ` David S. Miller
1998-12-22 10:38 ` Geert Uytterhoeven
1998-12-22 10:13 ` Arno Griffioen
1998-12-23 9:14 ` Geert Uytterhoeven
1998-12-23 13:23 ` Gabriel Paubert
1998-12-23 21:58 ` Alan Cox
1998-12-24 7:36 ` David S. Miller
1998-12-28 9:20 ` Andreas Schwab
1998-12-28 13:04 ` Alan Cox
1998-12-28 13:12 ` Andreas Schwab
1998-12-24 3:57 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=367F4872.3BE5EB12@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).