From: "Josan Kadett" <corporate@superonline.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Cursed Checksums
Date: Sun, 22 Aug 2004 23:03:54 +0200 [thread overview]
Message-ID: <S268085AbUHVUD4/20040822200356Z+207@vger.kernel.org> (raw)
In-Reply-To: <1093174820.24319.60.camel@localhost.localdomain>
Perhaps there is a way to recompute IP header checksums before they get into
the interface? As I outlined, I have found a way to manipulate IP source
address before the packet is flushed to system, but a means of recalculating
the IP header checksum after that manipulation should be found. Because even
if I ignore IP header CRC in one system, all other boxes connected to this
machine has to be patched the same. That is impossible anyway.
Only if I could find a way to recalculate the checksum in IP headers by
doing a simple hack to the kernel, everything would be alright.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Alan Cox
Sent: Sunday, August 22, 2004 1:40 PM
To: Josan Kadett
Cc: Linux Kernel Mailing List
Subject: Re: Cursed Checksums
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-08-22 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 2:37 Josan Kadett
2004-08-22 11:40 ` Alan Cox
2004-08-22 19:39 ` Josan Kadett
2004-08-22 21:03 ` Josan Kadett [this message]
2004-08-22 20:36 ` Alan Cox
2004-08-22 22:58 ` Olivier Galibert
2004-08-23 0:05 ` Josan Kadett
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=S268085AbUHVUD4/20040822200356Z+207@vger.kernel.org \
--to=corporate@superonline.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®