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.
Bug 1801603 - Fix iptables-translate for interface names containing asterisk
Summary: Fix iptables-translate for interface names containing asterisk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: 8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.2
Assignee: Phil Sutter
QA Contact: Radka Brychtova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-11 10:27 UTC by Phil Sutter
Modified: 2023-04-11 15:34 UTC (History)
5 users (show)

Fixed In Version: iptables-1.8.4-8.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1763652
Environment:
Last Closed: 2020-04-28 17:00:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-37173 0 None None None 2023-04-11 15:34:47 UTC
Red Hat Product Errata RHEA-2020:1889 0 None None None 2020-04-28 17:00:39 UTC

Comment 1 Phil Sutter 2020-02-11 10:41:49 UTC
Upstream commit to backport:

commit e179e87a1179e272a9bdabb0220b17d61d099ee3
Author: Phil Sutter <phil>
Date:   Thu Feb 6 15:08:41 2020 +0100

    xtables-translate: Fix for interface name corner-cases
    
    There are two special situations xlate_ifname() didn't cover for:
    
    * Interface name containing '*': This went unchanged, creating a command
      nft wouldn't accept. Instead translate into '\*' which doesn't change
      semantics.
    
    * Interface name being '+': Can't translate into nft wildcard character
      as nft doesn't accept asterisk-only interface names. Instead decide
      what to do based on 'invert' value: Skip match creation if false,
      match against an invalid interface name if true.
    
    Also add a test to make sure future changes to this behaviour are
    noticed.
    
    Signed-off-by: Phil Sutter <phil>

Comment 3 Phil Sutter 2020-02-13 13:07:09 UTC
CI tests exposed a problem with above patch: By accident, all '+' characters
are replaced when translating interface names instead of just the last one. Fix
sent upstream:

https://lore.kernel.org/netfilter-devel/20200213130436.26755-1-phil@nwl.cc/

Comment 8 errata-xmlrpc 2020-04-28 17:00:30 UTC
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:1889


Note You need to log in before you can comment on or make changes to this bug.