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.
nftables-0.8-10.el7.x86_64
nftables will present type 'host' instead of unicast, also 'other' is not documented. all 4 types including 'unicast' alias should be mentioned in pkt_type definition.
man nft(8):
├──────────────┼────────────────────────────────────────┤
│pkt_type │ Packet type: Unicast (addressed to lo‐ │
│ │ cal host), Broadcast (to all), Multi‐ │
│ │ cast (to group). │
└──────────────┴────────────────────────────────────────┘
+++ This bug was initially created as a clone of Bug #1374754 +++
currently the nftables tool supports the following symbols for pkt_type matches:
broadcast
multicast
unicast
with the latter being quite misleading, actually meaning 'unicast packet for this host' or PACKET_HOST, in term of kernel's define.
Other relevant symbols are advisable, e.g. at least for the pkt_type PACKET_OTHERHOST.
--- Additional comment from Phil Sutter on 2017-10-19 10:54:24 CEST ---
This was fixed by Florian:
commit 8a7f6de536408336770e352cde939f8cb09a644d
Author: Florian Westphal <fw>
Date: Thu Oct 27 14:31:34 2016 +0200
meta: fix pkttype name and add 'other' symbol
'unicast' doesn't check for unicast packets; it checks for PACKET_HOST,
i.e. a packet coming in for this host.
A unicast address to some other machine (e.g. because nic is
in promisc mode) will have PACKET_OTHER.
So at best this is misleading, so this patch changes it
to 'host'. The unicast entry is retained for compat purpose.
Signed-off-by: Florian Westphal <fw>
Acked-by: Pablo Neira Ayuso <pablo>
The patch is part of v0.7 release. Since RHEL7.5 will come with v0.8, this ticket is merely TestOnly anymore.
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-2019:2215
nftables-0.8-10.el7.x86_64 nftables will present type 'host' instead of unicast, also 'other' is not documented. all 4 types including 'unicast' alias should be mentioned in pkt_type definition. man nft(8): ├──────────────┼────────────────────────────────────────┤ │pkt_type │ Packet type: Unicast (addressed to lo‐ │ │ │ cal host), Broadcast (to all), Multi‐ │ │ │ cast (to group). │ └──────────────┴────────────────────────────────────────┘ +++ This bug was initially created as a clone of Bug #1374754 +++ currently the nftables tool supports the following symbols for pkt_type matches: broadcast multicast unicast with the latter being quite misleading, actually meaning 'unicast packet for this host' or PACKET_HOST, in term of kernel's define. Other relevant symbols are advisable, e.g. at least for the pkt_type PACKET_OTHERHOST. --- Additional comment from Phil Sutter on 2017-10-19 10:54:24 CEST --- This was fixed by Florian: commit 8a7f6de536408336770e352cde939f8cb09a644d Author: Florian Westphal <fw> Date: Thu Oct 27 14:31:34 2016 +0200 meta: fix pkttype name and add 'other' symbol 'unicast' doesn't check for unicast packets; it checks for PACKET_HOST, i.e. a packet coming in for this host. A unicast address to some other machine (e.g. because nic is in promisc mode) will have PACKET_OTHER. So at best this is misleading, so this patch changes it to 'host'. The unicast entry is retained for compat purpose. Signed-off-by: Florian Westphal <fw> Acked-by: Pablo Neira Ayuso <pablo> The patch is part of v0.7 release. Since RHEL7.5 will come with v0.8, this ticket is merely TestOnly anymore.