From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [RFC] back on nf_tables (plus compatibility layer)
Date: Fri, 26 Oct 2012 13:04:19 +0200 [thread overview]
Message-ID: <20121026110419.GA16629@1984> (raw)
In-Reply-To: <alpine.LNX.2.01.1210252352420.13437@nerf07.vanv.qr>
On Fri, Oct 26, 2012 at 12:02:56AM +0200, Jan Engelhardt wrote:
> On Thursday 2012-10-25 19:06, Pablo Neira Ayuso wrote:
>
> >Hi,
> >
> >I've been working for a while to recover nf_tables kernel patches and
> >to implement a compatibility layer so it can be used with existing
> >x_tables target/match extensions. [...]
> >2) Provide a fast path to merge this into mainstream. We'll have both
> > iptables and nftables interfaces during some time in the Linux kernel,
> > then remove iptables infrastructure at some point. iptables scripts
> > would not break as we'll have the iptables emulation over nftables.
> >[...]
> >One final thing: nftables does not support atomic table commit. The
> >point here is if we really need this for the emulation utility or we
> >can live without that. Implementing atomic table replacement in
> >nftables is not trivial. I have hard time to find this commit table
> >feature useful.
>
> Meanwhile, I am on xtables2 that actually reproduces the set of
> _really important_ features that currently are in the setsockopt
> iptables, like atomic table replace and atomic dump.
>
> I have updated to the newest tree, and the first set is
> available in the git repository at:
> git://git.inai.de/linux xt2-20121025
If you think this feature is important, checkout nf_tables and think
how to integrate this prototype code that provides atomic table
replacement to it.
next prev parent reply other threads:[~2012-10-26 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:06 [RFC] back on nf_tables (plus compatibility layer) Pablo Neira Ayuso
2012-10-25 22:02 ` Jan Engelhardt
2012-10-26 11:04 ` Pablo Neira Ayuso [this message]
2012-10-31 13:50 ` Jan Engelhardt
2012-10-31 15:42 ` Pablo Neira Ayuso
2012-11-01 15:49 ` Jan Engelhardt
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=20121026110419.GA16629@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netdev@vger.kernel.org \
--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.