From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: exthdr: add support for tcp option removal
Date: Fri, 24 Dec 2021 17:07:30 +0100 [thread overview]
Message-ID: <YcXwQpTpRwe5XvZP@salvia> (raw)
In-Reply-To: <YcO5tQz5ImOxtZLx@salvia>
On Thu, Dec 23, 2021 at 12:50:17AM +0100, Pablo Neira Ayuso wrote:
> On Mon, Dec 20, 2021 at 03:32:47PM +0100, Florian Westphal wrote:
> > This allows to replace a tcp option with nop padding to selectively disable
> > a particular tcp option.
> >
> > Optstrip mode is chosen when userspace passes the exthdr expression with
> > neither a source nor a destination register attribute.
> >
> > This is identical to xtables TCPOPTSTRIP extension.
>
> Is it worth to retain the bitmap approach?
Probably a new nested attribute to store the list of types that you
would like to strip:
NFTA_EXTHDR_TYPES
NFTA_EXTHDR_TYPE
NFTA_EXTHDR_TYPE
From the kernel, you could build a bitmap (just like TCPOPTSTRIP)
based on this list.
From the dump path, you can iterate over the bitmap to check for
bitset to build this nest.
> > Signed-off-by: Florian Westphal <fw@strlen.de>
> > ---
> > proposed userspace syntax is:
> >
> > nft add rule f in delete tcp option sack-perm
>
> nft add rule f in tcp option reset sack-perm,...
next prev parent reply other threads:[~2021-12-24 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 14:32 [PATCH nf-next] netfilter: exthdr: add support for tcp option removal Florian Westphal
2021-12-22 23:50 ` Pablo Neira Ayuso
2021-12-24 16:07 ` Pablo Neira Ayuso [this message]
2021-12-27 14:11 ` Florian Westphal
2021-12-27 14:28 ` Pablo Neira Ayuso
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=YcXwQpTpRwe5XvZP@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@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 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.