Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
`position` in an *nftables* add or insert rule is replaced by `handle` and `index`
With this update of the _nftables_ packages, the `position` parameter in an add or insert rule has been deprecated and replaced by the `handle` and `index` arguments. This syntax is more consistent with the replace and delete commands.
This excerpt from the nft man page:
RULES
[add | insert] rule [family] table chain [position position] statement...
replace rule [family] table chain handle handle statement...
delete rule [family] table chain handle handle
seems to imply that "insert ... position .." should use an offset into the ruleset, but it actually takes a handle just like delete/replace verbs.
At minimum the man page should be fixed to read something like
[add | insert] rule [family] table chain [position handle] statement...
^^^^^^
to make it clear this is handle, not an index (like iptables).
Upstream commit to backport:
commit effb881c9cef28aca47adeec5014e0457507539e
Author: Phil Sutter <phil>
Date: Wed May 9 16:03:40 2018 +0200
Deprecate add/insert rule 'position' argument
Instead, use 'handle' keyword for the same effect since that is more
consistent with respect to replace/delete commands. The old keyword is
still supported for backwards compatibility and also listed in man page
along with a hint that it shouldn't be used anymore.
Signed-off-by: Phil Sutter <phil>
Signed-off-by: Pablo Neira Ayuso <pablo>
Hi Mirek,
(In reply to Mirek Jahoda from comment #7)
> Based on our e-mail communication, I've just written a draft of a RN
> description in the Doc Text field. Could you please check it?
Looks good to me, thanks!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3154
This excerpt from the nft man page: RULES [add | insert] rule [family] table chain [position position] statement... replace rule [family] table chain handle handle statement... delete rule [family] table chain handle handle seems to imply that "insert ... position .." should use an offset into the ruleset, but it actually takes a handle just like delete/replace verbs. At minimum the man page should be fixed to read something like [add | insert] rule [family] table chain [position handle] statement... ^^^^^^ to make it clear this is handle, not an index (like iptables).