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.
RHEL9 lacks the following two fixes:
commit 2ba74d421cd622757df7a93720afc3b5b4b3b4e0
Author: Florian Westphal <fw>
Date: Tue Aug 2 14:52:30 2022 +0200
nft: fix ebtables among match when mac+ip addresses are used
When matching mac and ip addresses, the ip address needs to be placed
into then 2nd 32bit register, the switch to dynamic register allocation
instead re-uses reg1, this partially clobbers the mac address, so
set lookup comes up empty even though it should find a match.
Fixes: 7e38890c6b4fb ("nft: prepare for dynamic register allocation")
Reported-by: Yi Chen <yiche>
Signed-off-by: Florian Westphal <fw>
commit 32efb4ffc33ae874b3f26f3380e2184ad6ceb26f
Author: Florian Westphal <fw>
Date: Thu Sep 22 13:33:50 2022 +0200
nft: un-break among match with concatenation
The kernel commit 88cccd908d51 ("netfilter: nf_tables: NFTA_SET_ELEM_KEY_END requires concat and interval flags")
breaks ebtables-nft 'among' emulation, it sets NFTA_SET_ELEM_KEY_END but
doesn't set the CONCAT flag.
Update uapi header and also set CONCAT.
Signed-off-by: Florian Westphal <fw>
Jiri, please approve for RHEL9.1.z
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 (iptables bug fix and enhancement update), 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-2023:0949
Description of problem: ebtables --among-src with over 3 entities or including negation fail. Version-Release number of selected component (if applicable): iptables-nft-1.8.8-4.el9 How reproducible: always Steps to Reproduce: following commands fail (extensions/libebt_among.t) ebtables -A INPUT --among-src de:ad:0:be:ee:ff=10.0.0.1,c0:ff:ee:0:ba:be=192.168.1.1 ebtables -A INPUT --among-src ! c0:ff:ee:0:ba:be=192.168.1.1,de:ad:0:be:ee:ff=10.0.0.1 ebtables -A INPUT --among-src de:ad:0:be:ee:ff=10.0.0.1 --among-dst c0:ff:ee:0:ba:be=192.168.1.1 ebtables -A INPUT --among-src de:ad:0:be:ee:ff=10.0.0.1 --among-dst ! c0:ff:ee:0:ba:be=192.168.1.1 ebtables -A INPUT --among-src ! de:ad:0:be:ee:ff --among-dst c0:ff:ee:0:ba:be=192.168.1.1 ebtables -A INPUT --among-src de:ad:0:be:ee:ff=10.0.0.1 --among-dst ! c0:ff:ee:0:ba:be=192.168.1.1 ebtables -A INPUT --among-src c0:ff:ee:0:ba:be=192.168.1.1,de:ad:0:be:ee:ff Actual results: every invocation above prints: ebtables v1.8.8 (nf_tables): SET_ADD failed (No such file or directory): set __set%d Expected results: no output ruleset from iptables-nft-1.8.7-28.el9.x86_64 table bridge filter { chain INPUT { type filter hook input priority filter; policy accept; ether saddr . ip saddr { c0:ff:ee:00:ba:be . 192.168.1.1, de:ad:00:be:ee:ff . 10.0.0.1 } counter packets 0 bytes 0 ether saddr . ip saddr != { c0:ff:ee:00:ba:be . 192.168.1.1, de:ad:00:be:ee:ff . 10.0.0.1 } counter packets 0 bytes 0 ether saddr . ip saddr { de:ad:00:be:ee:ff . 10.0.0.1 } ether daddr . ip daddr { c0:ff:ee:00:ba:be . 192.168.1.1 } counter packets 0 bytes 0 ether saddr . ip saddr { de:ad:00:be:ee:ff . 10.0.0.1 } ether daddr . ip daddr != { c0:ff:ee:00:ba:be . 192.168.1.1 } counter packets 0 bytes 0 ether saddr != { de:ad:00:be:ee:ff } ether daddr . ip daddr { c0:ff:ee:00:ba:be . 192.168.1.1 } counter packets 0 bytes 0 ether saddr . ip saddr { de:ad:00:be:ee:ff . 10.0.0.1 } ether daddr . ip daddr != { c0:ff:ee:00:ba:be . 192.168.1.1 } counter packets 0 bytes 0 ether saddr . ip saddr { c0:ff:ee:00:ba:be . 192.168.1.1, de:ad:00:be:ee:ff . 0.0.0.0/0 } counter packets 0 bytes 0 } } Additional info: