From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Josan Kadett <corporate@superonline.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Cursed Checksums
Date: Sun, 22 Aug 2004 12:40:21 +0100 [thread overview]
Message-ID: <1093174820.24319.60.camel@localhost.localdomain> (raw)
In-Reply-To: <S268813AbUHUBhN/20040821013713Z+1335@vger.kernel.org>
On Sad, 2004-08-21 at 03:37, Josan Kadett wrote:
> When I manually calcaulate the checksum in the incoming TCP and UDP packets
> and re-inject them back to the socket, everything works fine. That is, the
> data integrity is not damaged or corrupted at all.
At least for the few you looked at. That proves nothing.
> I tried to investigate the code in tcp_input.c and udp.c to see if I can
> disable the checksum control for inbound packets entirely. No use it was
> since I need to do this urgently.
It depends on your hardware. With modern network cards we do the
checksum processing in hardware. For older setups passing a packet
through a Linux box won't directly help as the ttl recomputation is done
without recalculation from scratch.
We also have a pile of paths for checksumming including copy/checksum
rolled into one so it isn't easy to remove there.
I'd take up the issue with the vendor of the broken object. If its
something like an internal prototype you need to test then you'll
probably have to write a user space application using raw sockets to
communicate with it and do the fixups/passthrough in use space. Pretty
horrible either way.
Alan
Alan
next prev parent reply other threads:[~2004-08-22 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 2:37 Cursed Checksums Josan Kadett
2004-08-22 11:40 ` Alan Cox [this message]
2004-08-22 19:39 ` Josan Kadett
2004-08-22 21:03 ` Josan Kadett
2004-08-22 20:36 ` Alan Cox
2004-08-22 22:58 ` Olivier Galibert
2004-08-23 0:05 ` Josan Kadett
-- strict thread matches above, loose matches on Subject: below --
2004-08-22 18:55 Albert Cahalan
2004-08-22 22:38 ` Josan Kadett
[not found] <E1Bz02y-00052n-3Z@sc8-sf-mx2.sourceforge.net>
2004-08-22 20:14 ` Albert Cahalan
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=1093174820.24319.60.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=corporate@superonline.com \
--cc=linux-kernel@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