Differences between revisions 12 and 13
Revision 12 as of 2015-05-15 09:04:12
Size: 4408
Comment: nftables in jessie-backports
Revision 13 as of 2015-09-24 07:03:15
Size: 4151
Comment: refresh page a bit
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
nftables is under heavy development. nftables is under heavy development. Current version is v0.5.
Line 26: Line 26:
The short answer is: nftables is not a stable software, and it has nothing to do in a stable operating system.

Jessie was about to be released with nftables v0.3. Which is a very early release. Some important changes happened in v0.4, and in Linux kernel 3.18.

However, you can find nftables v0.4 in jessie-backports :-)
You can find nftables in jessie-backports :-)
Line 34: Line 30:
nftables requires a linux '''kernel >= 3.13''', but running a newer '''kernel >= 3.18''' is recommended. nftables requires a linux '''kernel >= 3.13''', but running a newer '''kernel >= 4.2''' is recommended.

nftables is a framework by the Netfilter Project that provides packet filtering, network address translation (NAT) and other packet mangling.

Two of the most common uses of nftables is to provide firewall support and NAT.

nftables is meant to replace the iptables framework.

Current status

nftables is under heavy development. Current version is v0.5.

For a production firewall, you should keep using iptables.

However, you would like to start testing nftables:

  • the new syntax and engine
  • get in touch with new workflows
  • report bug and request features

Currently, lots of bugs-fixes and features are added in each new release.

Why nftables is not in Debian Jessie?

You can find nftables in jessie-backports :-)


nftables requires a linux kernel >= 3.13, but running a newer kernel >= 4.2 is recommended.

Also, nftables requires libnftnl, a public library which provides a low level interface to the kernel subsystem.

Aptitude will take care of all dependencies.


What is nftables?

Is the new framework by the Netfilter Project, allowing you to perform packet filtering (firewalling), NAT, mangling and packet classification.

Why a new framework?

The previous framework (iptables) has several problems hard to address, regarding scalability, performance, code maintenance, etc..

What are the major differences?

In iptables there are several tables (filter, nat) and chains (FORWARD, INPUT...) by default. In nftables, there are no default tables/chains.

Also, in iptables you only have one target per rule (-j ACCEPT, -j LOG ...). In nftables, you can perform several actions in one single rule.

nftables includes built-in data sets capabilities. In iptables this is not possible, and there is a separated tool: ?ipset.

In the iptables framework there are tools per family: iptables, ip6tables, arptables, ebtables. Now, nftables allows you to manage all families in one single CLI tool.

This new framework features a new linux kernel subsystem, know as nf_tables. The new engine mechanism is inspired by BPF-like systems, with a set of basic expressions, which can be combined to build complex filtering rules.

Should I stop working with iptables to build a firewall?

No. Currently, nftables is in an early development state. Nowadays, iptables is more stable.

Then, Why should I use nftables?

You can start testing what is meant to become the future of firewalls on Linux. Report bugs, request features and get in touch with the latest in this technology.

I knew the iptables syntax. Is there a new syntax is nftables?

Yes, but the nftables one is better :-)

new syntax

Create a basic IPv4 table:

# nft add table filter

Create a chain for input traffic IPv4:

# nft add chain filter input { type filter hook input priority 0; }

A rule to check that all is fine (IPv4):

# nft add rule filter input counter accept

Show all the previous:

# nft list table filter

Flush rules in chain filter/input:

# nft flush chain filter input

Delete the chain filter/input:

# nft delete chain filter input

Delete the table filter:

# nft delete table filter

The family parameter is optional. The default is 'ip':

# nft add table ip6 filter
# nft add chain ip6 filter input
# nft add rule ip6 filter input counter accept

Debian ships an example configuration:

# nft -f /usr/share/doc/nftables/examples/basic.nft

Count traffic on destination port tcp/22:

# nft add rule filter input tcp dport 22 counter

Count and accept traffic in 80/tcp and 443/tcp in new an establised state:

# nft add rule filter input tcp dport {80, 443} ct state new,established counter accept

Export the ruleset in XML format (importing not yet supported):

nft export xml

external resources

Check out the official nftables wiki: http://wiki.nftables.org/