From: Pavel Mores <pvl@uh.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] checksum update in TCP
Date: Tue, 21 Jan 2003 11:58:45 +0000 [thread overview]
Message-ID: <marc-lartc-104315039017432@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104305763511093@msgid-missing>
On Mon, Jan 20, 2003 at 03:09:57PM +0100, devik wrote:
> > Or imho even more probably, the problem could be the line. I've had a
> > couple of these during last 3 years. Namely, is there a serial line
> > (possibly wireless) involved?
>
> Yes it is. There is wireless net inbetween. But interestingly
> I have seen no other packet corruption except when communicating
> via FTP with concrete W2k user.
> He can FTP with others as I can too but can't between themselves.
>
> Also how could wireless link change data inside of a TCP packet ?
> Then checksum should become wrong and the packet rejected ... ?
Yes, they should. What I had in mind was a data-dependent bug on a 2
Mbps wireless link that caused packets having alternate zero and one
patterns in it (0x5555 or 0xaaaa) to be dropped by the link and never
seen by the receiver. Now, I'm not sure what the exact symptoms are of
what you are solving. If your problem is that the TCP transmission
completes successfully (i.e. everything's OK as far as TCP is concerned)
but the data that came out of the pipe is different that the data that
had been sent, that should be a different problem.
> I changed proftpd to compute and log MD5 of each chunk of data
> going out of read() syscall so I will be able to compare them
> to file on HDD (catching errors in FS, IDE (DMA) or HDD).
> Also in the same time I'll save tcpdump's raw packets to be able
> to compare stored data with packet contents (with 100MB ftp file
> it will be a lot of fun :-( )
Can you produce a "binary diff" of sent and received file to see how
exactly they differ? Are the two files completely different? Or do
they differ just in a couple of places? Is something missing? Is
something changed? If so, how? That's how I managed to isolate some
difficult data-dependent bugs, it might be useful here, too.
pvl
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-21 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 9:23 [LARTC] checksum update in TCP devik
2003-01-20 10:35 ` Pavel Mores
2003-01-20 11:09 ` Patrick McHardy
2003-01-20 11:19 ` Patrick McHardy
2003-01-20 14:09 ` devik
2003-01-21 11:58 ` Pavel Mores [this message]
2003-01-21 13:59 ` devik
2003-01-22 23:24 ` Pavel Mores
2003-01-23 7:31 ` devik
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=marc-lartc-104315039017432@msgid-missing \
--to=pvl@uh.cz \
--cc=lartc@vger.kernel.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