From: Pablo Neira <pablo@eurodev.net>
To: Gervasio Bernal <gervasiobernal@speedy.com.ar>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: How to avoid fragmentation
Date: Thu, 27 Oct 2005 14:41:07 +0200 [thread overview]
Message-ID: <4360CAE3.6030600@eurodev.net> (raw)
In-Reply-To: <435D6030.8000509@speedy.com.ar>
Hi,
Gervasio Bernal wrote:
> I will show you an example:
>
> +---------------+
> | IP |
> | header |
> |---------------|
> | TCP |
> | header |
> |---------------|
> | My header |
> |---------------|
> | |
> | USER DATA |
> | |
> +---------------+
>
> I calculte the USER DATA checksum and put it in a field of My header.
> If the packet is larger than MTU, it will be fragmented and the checksum
> calculated in My header will be incorrect when I recieve it in the other
> endpoint of the communication.
>
> There is some form to avoid the fragmentation?
In this case, have a look at skb_checksum()
--
Pablo
prev parent reply other threads:[~2005-10-27 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 20:15 How to avoid fragmentation Gervasio Bernal
2005-10-24 23:37 ` Pablo Neira
[not found] ` <435D6030.8000509@speedy.com.ar>
2005-10-27 12:41 ` Pablo Neira [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=4360CAE3.6030600@eurodev.net \
--to=pablo@eurodev.net \
--cc=gervasiobernal@speedy.com.ar \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.