From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: Merging iptables-nftables into iptables
Date: Thu, 5 Dec 2013 09:24:09 +0100 [thread overview]
Message-ID: <20131205082409.GB4557@localhost> (raw)
In-Reply-To: <CAOkSjBj5z7x+15Dmw-EWtqiBWfv4h+DBO0s7KNeZgkgrZP4g+w@mail.gmail.com>
On Wed, Dec 04, 2013 at 04:11:18PM +0100, Arturo Borrero Gonzalez wrote:
> On 4 December 2013 12:48, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Hi,
> >
> > The iptables-nftables tree [1] currently stores the iptables over
> > nftables compatibility support. This allows you to run iptables
> > commands using the nftables kernel infrastructure.
> >
> > JFYI, my plan is to merge the iptables-nftables into iptables at some
> > point of this week given that it contains stuff that is scheduled for
> > 3.13. After that merge, the iptables-nftables will be disabled.
> >
> > [1] http://git.netfilter.org/iptables-nftables/
>
> Could you give some hints about releases of userspace stuff?
> (libnftables, nft, new iptables...)
>
> Is 3.13 a deadline for releases?
The initial release of the userspace libraries and tools will happen
by when the Linux kernel 3.13 is released, that should happen by the
beginning of 2014.
The nftables compatibility layer (the so-called iptables-nftables)
will be included in regular iptables releases, since it will be part
of that package.
next prev parent reply other threads:[~2013-12-05 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 11:48 Merging iptables-nftables into iptables Pablo Neira Ayuso
2013-12-04 15:11 ` Arturo Borrero Gonzalez
2013-12-05 8:24 ` Pablo Neira Ayuso [this message]
2013-12-05 21:15 ` Bart De Schuymer
2013-12-05 21:54 ` Pablo Neira Ayuso
2013-12-12 9:15 ` Tomasz Bursztyka
2013-12-30 23:07 ` Pablo Neira Ayuso
2013-12-31 9:40 ` 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=20131205082409.GB4557@localhost \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--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 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).