From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
coreteam@netfilter.org
Subject: Re: [RFC]: ip_conntrack breaks UDP PMTU
Date: Sat, 15 Feb 2003 06:12:33 +0100 [thread overview]
Message-ID: <3E4DCC41.1040604@trash.net> (raw)
In-Reply-To: <20030214145521.GB17921@sunbeam.de.gnumonks.org>
Harald Welte wrote:
>On Fri, Feb 14, 2003 at 02:42:16PM +0100, Patrick McHardy wrote:
>
>
>
>>Usually all fragments except the last one will have equal size, so the
>>fragment sizes can be stored as (size, boundary) tuples. I would
>>suggest making the max.
>>
>>
>
>yes, usually. But if we implement this 'fragment-backlog', we should do
>it as good as possible.
>
>I see people already whining about 'firewall can be detected because
>overlapping fragments are not present after passing through' or stuff
>like this :((
>
This is probably unavoidable as long as we want to use ip_defrag. I think we
really don't want the "perfect solution".
>
>
>
>>number of different fragment sizes fixed or controllable via sysctl and
>>set it to some low default (like 4). This would reduce the amount of
>>memory per reassembled packet to 4 * (2b + 2b) = 16b.
>>
>>
>
>so what do we do if the number is exceeded? fallback to current
>behaviour?
>
I have to admit, i really don't know, I would favour dropping such
crap with a higher default of maybe 8-16, although i understand
conntrack should not drop any packets.
I guess some cruel decisions have to be made here, and we haven't even
started to think about mangling nat helpers ..
Bye,
Patrick
next prev parent reply other threads:[~2003-02-15 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 8:06 [RFC]: ip_conntrack breaks UDP PMTU Harald Welte
2003-02-14 13:42 ` Patrick McHardy
2003-02-14 14:55 ` Harald Welte
2003-02-15 5:12 ` Patrick McHardy [this message]
2003-02-15 19:34 ` [netfilter-core] " Jozsef Kadlecsik
2003-02-15 17:58 ` Thomas Poehnitzsch
2003-02-15 20:50 ` Patrick McHardy
2003-02-16 23:55 ` Thomas Poehnitzsch
2003-02-17 0:39 ` Patrick McHardy
2003-02-16 19:54 ` Harald Welte
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=3E4DCC41.1040604@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=laforge@gnumonks.org \
--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.