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.
Description of problem:
nft monitor fails on ruleset with verdict map when there are nftrace-marked packets. It is not triggered when such packets are not comming
Version-Release number of selected component (if applicable):
nftables-0.9.0-14.el8.x86_64
How reproducible:
always
Steps to Reproduce:
send a packet that gets nftrace mark and passes through vmap
in this case 25/tcp from any machine
table inet example_table {
chain tcp_packets {
counter
}
chain udp_packets {
counter
}
chain incoming_traffic {
type filter hook input priority 0; policy accept;
tcp dport smtp nftrace set 1
ip protocol vmap { tcp : jump tcp_packets, udp : jump udp_packets }
}
}
Actual results:
trace id 1ee47dd1 inet example_table incoming_traffic packet: iif "eth0" ether saddr fa:16:3e:bf:5c:ae ether daddr fa:16:3e:df:95:bc ip saddr 10.0.138.11 ip daddr 10.0.136.212 ip dscp cs0 ip ecn not-ect ip ttl 64 ip id 38330 ip protocol tcp ip length 60 tcp sport 60138 tcp dport smtp tcp flags == syn tcp window 29200
trace id 1ee47dd1 inet example_table incoming_traffic rule tcp dport smtp nftrace set 1 (verdict continue)
trace id 1ee47dd1 inet example_table incoming_traffic rule ip protocol vmap { } (verdict BUG: verdict expression length 2048 is too large (2048 bits max)nft: datatype.c:265: verdict_jump_chain_print: Assertion `0' failed.
Aborted (core dumped)
Expected results:
Additional info:
Hi Tomas,
(In reply to Tomas Dolezal from comment #1)
> this is fixed in rebase nftables-0.9.2-2.el8.x86_64
Cool, thanks for clarifying! Are you able to verify this officially for RHEL-8.2.0?
Thanks, Phil
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/RHEA-2020:1774
Description of problem: nft monitor fails on ruleset with verdict map when there are nftrace-marked packets. It is not triggered when such packets are not comming Version-Release number of selected component (if applicable): nftables-0.9.0-14.el8.x86_64 How reproducible: always Steps to Reproduce: send a packet that gets nftrace mark and passes through vmap in this case 25/tcp from any machine table inet example_table { chain tcp_packets { counter } chain udp_packets { counter } chain incoming_traffic { type filter hook input priority 0; policy accept; tcp dport smtp nftrace set 1 ip protocol vmap { tcp : jump tcp_packets, udp : jump udp_packets } } } Actual results: trace id 1ee47dd1 inet example_table incoming_traffic packet: iif "eth0" ether saddr fa:16:3e:bf:5c:ae ether daddr fa:16:3e:df:95:bc ip saddr 10.0.138.11 ip daddr 10.0.136.212 ip dscp cs0 ip ecn not-ect ip ttl 64 ip id 38330 ip protocol tcp ip length 60 tcp sport 60138 tcp dport smtp tcp flags == syn tcp window 29200 trace id 1ee47dd1 inet example_table incoming_traffic rule tcp dport smtp nftrace set 1 (verdict continue) trace id 1ee47dd1 inet example_table incoming_traffic rule ip protocol vmap { } (verdict BUG: verdict expression length 2048 is too large (2048 bits max)nft: datatype.c:265: verdict_jump_chain_print: Assertion `0' failed. Aborted (core dumped) Expected results: Additional info: