From: Florian Westphal <fw@strlen.de>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Hans Schillstrom <hans@schillstrom.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: [RFC] netfilter: xt_TEE: IPv4 Don't Fragmet options
Date: Sat, 16 Jun 2012 15:18:38 +0200 [thread overview]
Message-ID: <20120616131838.GB22939@breakpoint.cc> (raw)
In-Reply-To: <alpine.LNX.2.01.1206151500260.12865@frira.zrqbmnf.qr>
Jan Engelhardt <jengelh@inai.de> wrote:
> On Friday 2012-06-15 14:51, Hans Schillstrom wrote:
> >
> Here's another point I remember why we forced IP_DF: we want to keep
> the packet as-is. The receiver of the cloned packet (often a logger)
> has no way of autonomously knowing whether the packet was already
> fragmented originally as it came into the cloner, or whether
> fragmentation is a doing of the cloner.
Except that, if the path mtu was too low, it doesn't even
receive that packet. If the sender does PMTUD, that might be ok
since future packets will be reduced in size.
But if the sender doesn't do PMTUD (and 'DF not set' indicates that)
your 'clone receiver' will never get any data at all...
TEE really shouldn't force DF.
next prev parent reply other threads:[~2012-06-16 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 12:51 Re[3]: [RFC] netfilter: xt_TEE: IPv4 Don't Fragmet options Hans Schillstrom
2012-06-15 13:04 ` Jan Engelhardt
2012-06-16 13:18 ` Florian Westphal [this message]
2012-06-16 13:57 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2012-06-14 6:17 Hans Schillstrom
2012-06-14 17:52 ` Pablo Neira Ayuso
2012-06-14 18:59 ` Pablo Neira Ayuso
2012-06-14 20:07 ` Florian Westphal
2012-06-14 23:55 ` Jan Engelhardt
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=20120616131838.GB22939@breakpoint.cc \
--to=fw@strlen.de \
--cc=hans@schillstrom.com \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).