From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: nftables 1.0.6.y stable branch updates
Date: Thu, 23 Jan 2025 18:24:38 +0100 [thread overview]
Message-ID: <Z5J7Vh5OPORkmmXC@calendula> (raw)
Hi,
I have updated the 1.0.6.y -stable branch:
https://git.netfilter.org/nftables/log/?h=1.0.6.y
This branch contains 254 selected commits out of the 753 commits
available between v1.0.6 and git HEAD.
I have run _current_ tests/shell and tests/py in git HEAD on this
branch, with the following results:
- tests/shell:
W: [DUMP FAIL] 223/440 testcases/sets/meter_0
W: [DUMP FAIL] 162/440 testcases/sets/0022type_selective_flush_0
W: [FAILED] 107/440 testcases/sets/0038meter_list_0
These tests fail because 1.0.6.y does not include the code to convert
meters to dynamic sets, it should be possible to make it later, this
requires no kernel update.
- tests/py. The following tests fail:
- numgen inc compatibility with ipv4_addr datatype: this is a
userspace feature that is missing, this requires not kernel updates
and it should be possible to backport it.
- icmpv6 match extension: there is an extension to improve matching
capabilities of icmpv6 that is also not backports. This requires not
kernel update, it should be possible to support it.
- last statement: that tells you when last match on rule/element has
happened. This does not require a kernel update, it should be
possible to support it.
- inner matching: this feature requires kernel >= 6.3.
- bitwise multiregister: this feature requires kernel >= 6.13.
Comments welcome.
Thanks.
next reply other threads:[~2025-01-23 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 17:24 Pablo Neira Ayuso [this message]
2025-07-31 23:16 ` nftables 1.0.6.y stable branch updates (strike 2) Pablo Neira Ayuso
2025-08-17 21:54 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z5J7Vh5OPORkmmXC@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.