From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] checksum update in TCP
Date: Thu, 23 Jan 2003 07:31:35 +0000 [thread overview]
Message-ID: <marc-lartc-104330914009407@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104305763511093@msgid-missing>
> > 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
> ... ;)
:) I can't ! Other user is in Italia, uses Win2k and have no clue
about networking. He is helping me a lot but I can't want too much
from him.
Just now I have whole tcpdump of transfer at my side (170MB), MD5
checksums of 8kb parts ot transfer and when comparing MD5s with
file's content they are ok.
So that my side stored into file exactly what arrived from network.
Seems like if w2k sometimes reads bad data from hdd .. When I resolve
it I'll let you know.
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-23 7:31 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
2003-01-23 7:31 ` devik [this message]
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-104330914009407@msgid-missing \
--to=devik@cdi.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