From: Pavel Mores <pvl@uh.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] checksum update in TCP
Date: Mon, 20 Jan 2003 10:35:55 +0000 [thread overview]
Message-ID: <marc-lartc-104305899012461@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104305763511093@msgid-missing>
On Mon, Jan 20, 2003 at 10:23:16AM +0100, devik wrote:
> Hi,
>
> anyone knows when TCP checksum is updated ?
Normally, TCP checksum is not supposed to be changed (or even read)
at all during transfer (see rfc793 or TCP/IP Illustrated Vol.1).
If NAT is in use then it needs to be accounted for, of course, because
TCP chksum involves a pseudoheader which contains both source and
destination addresses - but this is not the case, as you say.
> On other side if it simply passes packet thru (because nothing
> except TTL is changed and TTL is not part of TCP checksum) then
> the checksum should really ensure that nothing is changed
> between sender and reciever and if data are invalid then error
> would be on sender's or reciever's side.
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?
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-20 10:35 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 [this message]
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
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-104305899012461@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