From: Patrick McHardy <kaber@trash.net>
To: philipc@snapgear.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 1/4] TCPMSS: dont drop packets
Date: Wed, 24 May 2006 18:16:58 +0200 [thread overview]
Message-ID: <447486FA.8010206@trash.net> (raw)
In-Reply-To: <20060524040950.838105000@snapgear.com>
philipc@snapgear.com wrote:
> MSS clamping should be best effort, since we are doing the clamping
> to avoid dropped packets. If we can't clamp, then forward it anyway
> and hope PMTU discovery works.
>
> The test case that caused problems was syn packet containing data.
That seems to be an invalid testcase.
> Related questions:
> This patch changes the behaviour when setting the MSS too, is this
> acceptable?
>
> Should skb_make_writable() and skb_checksum_help() cause dropped packets
> if they fail?
>
> Which mangle targets should drop packets if they fail?
> MARK should, since the mark may be used in filter rules.
> What about DSCP, ECN, TOS, TTL?
I don't think its a good idea to change this long standing behaviour.
The next incarnation of iptables will support user-supplied verdicts
for non-terminal targets, but until then it seems reasonable to say
"user said do x, can't do it, so drop".
It should be noted that most of these conditions can't be true anyway,
I have a half-finished patch to remove most of them.
next prev parent reply other threads:[~2006-05-24 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 4:04 [PATCH 0/4] netfilter patches for consideration philipc
2006-05-24 4:04 ` [PATCH 1/4] TCPMSS: dont drop packets philipc
2006-05-24 16:16 ` Patrick McHardy [this message]
2006-05-24 23:42 ` Philip Craig
2006-05-26 14:40 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 2/4] TCPMSS: clamp to input interface MTU too philipc
2006-05-24 16:18 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 3/4] log dropped ICMP redirects philipc
2006-05-24 16:26 ` Patrick McHardy
2006-05-25 2:34 ` Philip Craig
2006-05-26 14:49 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 4/4] drop ftp bounce attacks philipc
2006-05-24 16:31 ` Patrick McHardy
2006-05-25 2:55 ` Philip Craig
2006-05-26 14:51 ` Patrick McHardy
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=447486FA.8010206@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=philipc@snapgear.com \
/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.