The NftTable object represents a nftables table. It consists of a set of chains which are being processed depending on the family property.
This object was introduced in InCore 2.1.
|› Inherited by:||NftAddressTranslation, NftFlow|
This property holds a list of chains for this table.
This property holds whether the table is enabled, i.e. it should be included in the firewall configuration.
This property holds the family of the Netfilter table. See the NftTable.Family enum for details.
This property holds the name of the firewall table, e.g.
This signal is emitted whenever the List.dataChanged() signal is emitted, i.e. the item at
index in the chains list itself emitted the dataChanged() signal.
This enumeration describes supported address families for which traffic/packets can be processed by tables. See the nftables documentation on families for further details
||Tables of this family will see IPv4 traffic/packets.|
||Tables of this family will see IPv6 traffic/packets.|
||Tables of this family will see both IPv4/IPv6 traffic/packets, designed to improve dual stack support. Both IPv4/IPv6 packets will traverse the same rules. Rules for IPv4 packets won’t affect IPv6 packets. Rules for both L3 protocol will affect both.|
||Tables of this family will see ARP-level (i.e, L2) traffic, before any L3 handling is done.|
||Tables of this family will see traffic/packets traversing bridges (i.e. switching). No assumptions are made about L3 protocols.|
||This family provides the ingress hook, that allows classifying packets that the driver has just passed up to the networking stack. This means the table sees all network traffic for the NIC getting in. No assumptions are made about L2 or L3 protocols, therefore ARP traffic can be filtered from here.|
See NftFirewall example on how to use NftTable.