Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Pavel Mores <pvl@uh.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] checksum update in TCP
Date: Wed, 22 Jan 2003 23:24:40 +0000	[thread overview]
Message-ID: <marc-lartc-104327794016434@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104305763511093@msgid-missing>

On Tue, Jan 21, 2003 at 02:59:07PM +0100, devik wrote:

> > 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.
> 
> I did (I wrote program for it). 16MB are totaly dirrerent
> (from offset 14MB aligned on page boundary) and some other
> part (10kB) is shifted by 1 byte. That part is not even 512B
> aligned. This is list of different parts between 148005111
> long files f1 and f2:
> from 14557184, cnt 4481067
> from 19038287, cnt 11393
>         at 19038288 (by 1) in f1
>         at 19038286 (by -1) in f2
> from 19049716, cnt  1162
>         at 19049717 (by 1) in f1
>         at 19049715 (by -1) in f2
> from 19050914, cnt 46210654
> from 68514564, cnt 4855808
>         at 68518659 (by 4095) in f2
> 
> "at" block is where the block was found in other file.

Uff. ;)  I give up, I don't remember seeing anything like this.  I would
do one tcpdump at the sender and another at the receiver and compare the
files.  If they differ, something's changed along the path, if they
don't, it should be possible to find out which version of the file the
dumps' data correspond to.  But that's what you've probably done already
... ;)

	pvl

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-01-22 23:24 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
2003-01-21 13:59 ` devik
2003-01-22 23:24 ` Pavel Mores [this message]
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-104327794016434@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