`nftables` rebased to version 1.1.5:: + -- The `nftables` package has been updated to upstream version 1.1.5. Notable enhancements: * The memory consumption with sets and maps was reduced. * Sets can now depend on specific protocols. * The auto-merge feature skips elements with timeout and expiration. * You can use the `typeof` keyword with queues. * The `nft monitor` command can monitor `flowtable` events. * For consistency with other commands, the `nft list sets inet _<set_name>_` command works without the `table` keyword. * You can use a range expression to represent a range instead of two comparisons. * The Multipath TCP support with symbol table for subtypes was improved. * Support for mangling `bitfield` headers was added. * Set elements with multi-word descriptions are now displayed in a single line. * The layer 4 protocol dependency when listing raw expressions is not longer removed. * The JSON output format supports the `typeof` keyword. * The bytecode generation for Virtual Local Area Network (VLAN) Priority Code Point (PCP) mangling in `netdev`-family chains was fixed. * An issue causing bogus elements in large concatenated set ranges was fixed. * A new check result was added to the Forwarding Information Base (FIB) expression to verify routes. * The total number of elements is now displayed when listing sets. * You can delete maps can by using their unique handle. * The JSON parser was hardened. Notable bug fixes: * Error messages for set or map re-declarations with conflicting types were improved. * The `optimize` parameter was fixed and improved. * Extended error reporting with large set elements was fixed. * The incorrect removal of `meta nfproto` settings in listings. * The `get` and `reset` commands with internal sets and maps were fixed. * Listings display now the number of set elements. * Device names in `basechain` and `flowtable` declarations are correctly quoted. * An misleading `No buffer space available" error message was corrected. --