From: Florian Westphal <fw@strlen.de>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Davide Caratti <dcaratti@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
coreteam@netfilter.org
Subject: Re: [PATCH nf-next 0/2] netfilter: autoload NAT support for non-builtin L4 protocols
Date: Fri, 7 Oct 2016 16:20:52 +0200 [thread overview]
Message-ID: <20161007142052.GB7063@breakpoint.cc> (raw)
In-Reply-To: <CAOkSjBi8zZCyZ-7pqpiboK5HcnTohtx0vscA73wjHNzH-r5FHw@mail.gmail.com>
Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com> wrote:
> Unlike in iptables, in nftables we don't know the expected l4 protocol
> at rule setup time.
>
> In the iptables<->nftables compat layer, we have an expression
> attribute which is filled from userspace with the l4 protocol
> (NFTA_RULE_COMPAT_PROTO).
>
> Not sure if it's worth adding a new netlink attribute for nft_nat to
> tell the expression about the expected l4 NAT protocol.
Right, it might more sense to handle this in nft frontend
instead.
next prev parent reply other threads:[~2016-10-07 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 17:09 [PATCH nf-next 0/2] netfilter: autoload NAT support for non-builtin L4 protocols Davide Caratti
2016-10-06 17:09 ` [PATCH nf-next 1/2] netfilter: persistent aliases for l4 nat protocols Davide Caratti
2016-10-06 17:09 ` [PATCH nf-next 2/2] xt_nat: probe module for non-builtin L4 protocols Davide Caratti
2016-10-07 7:35 ` [PATCH nf-next 0/2] netfilter: autoload NAT support " Arturo Borrero Gonzalez
2016-10-07 9:59 ` Davide Caratti
2016-10-07 10:32 ` Arturo Borrero Gonzalez
2016-10-07 14:20 ` Florian Westphal [this message]
2016-10-17 17:58 ` Pablo Neira Ayuso
2016-10-18 9:12 ` Davide Caratti
2016-10-19 12:23 ` Pablo Neira Ayuso
2016-10-19 12:57 ` Florian Westphal
2016-10-19 15:56 ` 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=20161007142052.GB7063@breakpoint.cc \
--to=fw@strlen.de \
--cc=arturo.borrero.glez@gmail.com \
--cc=coreteam@netfilter.org \
--cc=dcaratti@redhat.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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 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.