Difference between revisions of "Adoption"

From nftables wiki
Jump to navigation Jump to search
(→‎virtualization / cloud / infrastructure: add link to docker and IPv6 with nftables)
(Edited page intro for clarity.)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page offers some light and data about current '''nftables adoption''' in the wider community.
The Netfilter project and community is focused on replacing the iptables framework with nftables, adding new features and refreshing some workflows along the way.
As you probably know, the focus of the Netfilter project and community is in replacing the iptables framework with nftables, adding brand new features and refreshing some workflows along the way.


Lots of upstream projects use iptables to handle NAT, filtering, mangling or other networking stuff.
Many upstream projects use iptables to handle filtering, NAT, mangling and other networking tasks. This page tracks '''nftables adoption''' in the wider community.
Here, the info we know about them, their relationship with nftables and the possibilities for them to migrate to nftables.


= Cases =
= Cases =
Line 13: Line 11:
== system / firewalling / management ==
== system / firewalling / management ==


* http://www.fail2ban.org/ -- the fail2ban tool already includes native support for nftables.
=== Supporting nftables ===
* http://www.firewalld.org/ -- firewalld by RedHat is currently developing a native integration with nftables.
 
The following projects are known to either directly support nftables or have authors actively working on nftables integration.
 
* https://www.fail2ban.org/ -- the fail2ban tool already includes native support for nftables.
* https://firewalld.org/ -- firewalld by RedHat is currently developing a native integration with nftables.
* https://suricata-ids.org/ -- suricata can work natively with nftables ([https://home.regit.org/2014/02/suricata-and-nftables/ link])
* https://suricata-ids.org/ -- suricata can work natively with nftables ([https://home.regit.org/2014/02/suricata-and-nftables/ link])
* https://keepalived.org/ -- keepalived works natively with nftables ([https://github.com/acassen/keepalived/issues/924])
=== Supporting iptables only ===
The following projects are known to only support iptables/iptables-nft, with no plans to support nftables in the future.
* http://ferm.foo-projects.org/ -- [https://github.com/MaxKellermann/ferm/issues/35#issuecomment-386091563 citation]
* https://shorewall.org/ -- [https://sourceforge.net/p/shorewall/mailman/message/35458915/ citation]


== virtualization / cloud / infrastructure ==
== virtualization / cloud / infrastructure ==

Latest revision as of 20:07, 17 February 2021

The Netfilter project and community is focused on replacing the iptables framework with nftables, adding new features and refreshing some workflows along the way.

Many upstream projects use iptables to handle filtering, NAT, mangling and other networking tasks. This page tracks nftables adoption in the wider community.

Cases

Known cases and examples we could heard of. TODO: extend with more current data.

All major Linux distributions contains the nftables framework ready to use. Check Nftables from distributions.

system / firewalling / management

Supporting nftables

The following projects are known to either directly support nftables or have authors actively working on nftables integration.

Supporting iptables only

The following projects are known to only support iptables/iptables-nft, with no plans to support nftables in the future.

virtualization / cloud / infrastructure

others

See also