From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: fw@strlen.de, fmyhr@fhmtech.com, stefanh@hafenthal.de
Subject: [PATCH RFC nf-next 0/2] ct helper object name matching
Date: Tue, 9 Mar 2021 22:01:32 +0100 [thread overview]
Message-ID: <20210309210134.13620-1-pablo@netfilter.org> (raw)
Hi,
[ Compile tested-only and userspace update is missing ]
This patchset adds NFT_CT_HELPER_OBJNAME to match on the helper object name, ie.
From nftables, existing (inconsistent) syntax can be left in place for
backward compatibility. The new proposed syntax would more explicitly
refer to match the user wants to do, e.g.
ct helper name set "ftp-21"
ct helper name "ftp-21"
For NFT_CT_HELPER_TYPE (formerly NFT_CT_HELPER), syntax would be:
ct helper type "ftp"
It should be also possible to support for:
ct helper type set "ftp"
via implicit object, this infrastructure is missing in the kernel
though, the idea would be to create an implicit object that is attached
to the rule. Such object would be released when the rule is removed.
Let me know.
Pablo Neira Ayuso (2):
netfilter: nftables: rename NFT_CT_HELPER to NFT_CT_HELPER_TYPE
netfilter: nftables: add NFT_CT_HELPER_OBJNAME
include/net/netfilter/nf_conntrack_helper.h | 1 +
include/uapi/linux/netfilter/nf_tables.h | 7 +++--
net/netfilter/nf_conntrack_helper.c | 1 +
net/netfilter/nft_ct.c | 30 +++++++++++++++++----
4 files changed, 32 insertions(+), 7 deletions(-)
--
2.20.1
next reply other threads:[~2021-03-09 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 21:01 Pablo Neira Ayuso [this message]
2021-03-09 21:01 ` [PATCH nf-next 1/2] netfilter: nftables: rename NFT_CT_HELPER to NFT_CT_HELPER_TYPE Pablo Neira Ayuso
2021-03-09 21:01 ` [PATCH nf-next 2/2] netfilter: nftables: add NFT_CT_HELPER_OBJNAME Pablo Neira Ayuso
2021-03-09 21:18 ` [PATCH RFC nf-next 0/2] ct helper object name matching Florian Westphal
2021-03-09 21:24 ` 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=20210309210134.13620-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=fmyhr@fhmtech.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=stefanh@hafenthal.de \
/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).