From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [RFC nf-next] netfilter: ct: add helper assignment support
Date: Wed, 15 Feb 2017 23:19:03 +0100 [thread overview]
Message-ID: <20170215221903.GB32431@breakpoint.cc> (raw)
In-Reply-To: <20170215170558.GA22564@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Note from myself, i dislike L3PROTO, it would be nicer to be able
> > to handle this via the table family but I did not yet find a way
> > to detect this from the obj->init() function.
>
> We can pass nft_ctx to obj->init().
OK, I can make that change then, no problem.
> > Its needed for nf_conntrack_helper_try_module_get().
> >
> > This also begs the question of how one would handle
> > NFPROTO_INET, in that case we'd want both v4 and v6, but that
> > would require stashing two struct nf_conntrack_helper in
> > priv area.
>
> Still, someone may want to only enable helper for IPv4 in the inet
> chain, right? It's a bit of corner case but this attribute provides
> slight more flexibility.
But assignment can be limited via nft ... meta nfproto ipv4, no?
> Probably, we should handle NFPROTO_INET as a real family at some
> point, so user doesn't have to specify twice the same configuration to
> attach helpers from inet chains.
Yes, that what I wanted to avoid ...
> On a different front, but related, I've been considering to handle the
> NFPROTO_INET family from the netfilter/core, so we can get rid of the
> existing specific code in nf_tables to handle this pseudofamily.
> Actually, just handle it as a real family. I have a patchset here in a
> branch I made to do this, I would need to revisit it.
Sounds good to me, although I am not sure how you're going to pull this
off ;)
> > Any ideas/suggestions?
> >
> > + NFTA_CT_HELPER_L4PROTO,
>
> Fine by now. We can place here more attributes, such as expectation
> timeouts and specific per-helper setting (eg. ftp loose). Just a
> matter of adding more attributes later on, no problem.
Right, I wanted to be sure that this is the right direction before
doing this.
> > + if (nla_strlcpy(name, tb[NFTA_CT_HELPER_NAME], sizeof(name)) >= sizeof(name))
> > + return -EINVAL;
>
> nla_policy already ensures we don't go over helper name size.
Right, I'll remove the conditional, thanks Pablo.
next prev parent reply other threads:[~2017-02-15 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 16:25 [RFC nf-next] netfilter: ct: add helper assignment support Florian Westphal
2017-02-15 17:05 ` Pablo Neira Ayuso
2017-02-15 22:19 ` Florian Westphal [this message]
2017-02-16 13:24 ` Pablo Neira Ayuso
2017-02-16 14:22 ` Florian Westphal
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=20170215221903.GB32431@breakpoint.cc \
--to=fw@strlen.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).