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:

Please add support for firewalld policies with ingress/egress zone set to HOST.

Podman's new network stack, Netavark, uses firewalld (where available) to (among other things) forward ports from the host to containers using firewalld policies and the `forward_ports` API. This is presently working for traffic coming from outside the host, but not for traffic from localhost which attempts to reach the forwarded ports. This functionality is required to prevent regressions from Podman's current network stack. A policy with both ingress-zone and egress-zone set to HOST will allow traffic from localhost to access these forwarded ports.

We intend on working around this via direct iptables rules until this feature is available.

Version-Release number of selected component (if applicable):

Any

How reproducible:

100%

Steps to Reproduce:
N/A

Actual results:
Traffic from localhost is not forwarded

Expected results:
Traffic from localhost is forwarded

Additional info:

Upstream commits:

54738f2db549 ("test(policy): verify top level policy dispatch")
48983a25f153 ("test(policy): support OUTPUT forward ports")
c5d5be227e3f ("feat(policy): support OUTPUT forward ports")

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 (firewalld 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-2022:8389