|| ||Jan Engelhardt <jengelh-AT-inai.de> |
|| ||Pablo Neira Ayuso <pablo-AT-netfilter.org> |
|| ||Re: [RFC] back on nf_tables (plus compatibility layer) |
|| ||Thu, 1 Nov 2012 16:49:01 +0100 (CET)|
|| ||Netfilter Development Mailing list
Linux Networking Developer Mailing List
|| ||Article, Thread
On Wednesday 2012-10-31 16:42, Pablo Neira Ayuso wrote:
>> >> 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.
>> I'd rather tinker with xt2.
>You're are free spend your time on your pet project, but I warn you:
>it will *extremely hard* to justify its inclusion into mainline.
>As said, I don't think it makes sense to add two firewall
>engines/interfaces for the same thing.
You make it sound like you have already made up your mind and will
not consider xtnl because you are having nft as your pet project.
That would be really sad.
So, what xt2 has of this hour.
(- netlink interface obviously)
- netns support
- single table sufficiency
- is RCU'd
- atomic whole-table replace
- atomic chain-level multi-rule replace
(less to transfer over netlink between kernel<->user)
- chain-level dump (also relates to transfer size)
- packed ruleset for cache efficiency
- already has had some review from community members when it was last posted
- in-code and external documentation
Certainly there is still something to do - but so would there be for nft.
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)