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.

In nft-variants, options -4 and -6 sometimes have a different effect than in legacy ones. Fix this by backporting the following commits:

commit 1639b8ba5105542c73e0e1c35e70f245dab89d81
Author: Phil Sutter <phil>
Date:   Fri Feb 21 13:18:32 2020 +0100

    xtables: Align effect of -4/-6 options with legacy

    Legacy iptables doesn't accept -4 or -6 if they don't match the
    symlink's native family. The only exception to that is iptables-restore
    which simply ignores the lines introduced by non-matching options, which
    is useful to create combined dump files for feeding into both
    iptables-restore and ip6tables-restore.

    Signed-off-by: Phil Sutter <phil>

commit 0f40a8bc49d3f7b815336199931a82f919f37c4e
Author: Phil Sutter <phil>
Date:   Fri Feb 21 13:29:05 2020 +0100

    xtables: Drop -4 and -6 support from xtables-{save,restore}

    Legacy tools don't support those options, either.

    Signed-off-by: Phil Sutter <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 (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-2020:4518