From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andreas Herz <andi@geekosphere.org>
Cc: Netfilter user mailing list <netfilter@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: Formal submission of Xtables2
Date: Mon, 17 Dec 2012 00:57:51 +0100 [thread overview]
Message-ID: <20121216235751.GA7528@1984> (raw)
In-Reply-To: <20121214094141.GO2606@workstation>
Hi Andreas,
On Fri, Dec 14, 2012 at 10:41:41AM +0100, Andreas Herz wrote:
> On 13/12/12 at 12:00, Pablo Neira Ayuso wrote:
> > On Thu, Dec 13, 2012 at 07:00:07AM +0100, Jan Engelhardt wrote:
> > [...]
> > > Please consider for merging.
> >
> > nftables and its compatibility layer already provide this and we will
> > not have to maintain two different netlink interfaces, which is too
> > much overhead.
>
> Apart of your discussion (i think it's quite interesting although
> you might not agree), is there a summary of the status of nftables?
> The last time i read about it, while i was at the university, i
> thought it was dead. I read that Patrick McHardy was the one
> pushing the project but never heard any news after 2010. Now i read
> that Pablo is taking care of it.
It's true that nftables suffered an hiatus in its development, but
we're back on it and there has been quite a lot of activity on it
recently. This is the kernel branch, you can check the changelog here:
http://1984.lsi.us.es/git/nf-next/log/?h=nf_tables8
And there's an iptables compatibility layer that is ready for IPv4,
you can find details here:
http://www.spinics.net/lists/netfilter-devel/msg23831.html
> So i would love to hear more details on the roadmap for nftables, might
> be interesting for me and my work here.
I understand you want to know more on the future of nftables, but
because the way I am, I prefer to skip "hot air" wording by now and
talk on code done anytime soon.
So I have to request some patience from you. We promise to deliver as
much information as possible once we are done with the core features.
Thanks.
prev parent reply other threads:[~2012-12-16 23:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 6:00 Formal submission of Xtables2 Jan Engelhardt
2012-12-13 11:00 ` Pablo Neira Ayuso
2012-12-13 11:36 ` Jan Engelhardt
2012-12-13 12:05 ` Pablo Neira Ayuso
2012-12-13 13:08 ` Jan Engelhardt
2012-12-13 14:28 ` Pablo Neira Ayuso
2012-12-13 14:53 ` Jan Engelhardt
2012-12-13 15:16 ` Pablo Neira Ayuso
2012-12-13 16:41 ` Jan Engelhardt
2012-12-13 17:25 ` Pablo Neira Ayuso
2012-12-13 18:19 ` Jan Engelhardt
2012-12-17 0:08 ` Pablo Neira Ayuso
2012-12-17 1:39 ` Jan Engelhardt
2012-12-17 9:53 ` Pablo Neira Ayuso
2012-12-17 10:12 ` Maciej Żenczykowski
2012-12-17 13:01 ` Jan Engelhardt
2012-12-17 14:30 ` Pablo Neira Ayuso
2012-12-17 20:51 ` Jan Engelhardt
2012-12-17 23:49 ` Jozsef Kadlecsik
2012-12-18 1:11 ` Jan Engelhardt
2012-12-18 1:51 ` Neal Murphy
2012-12-18 1:27 ` David Miller
2012-12-14 9:41 ` Andreas Herz
2012-12-14 18:49 ` Jan Engelhardt
2012-12-18 14:09 ` Andreas Herz
2012-12-16 23:57 ` Pablo Neira Ayuso [this message]
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=20121216235751.GA7528@1984 \
--to=pablo@netfilter.org \
--cc=andi@geekosphere.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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.