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:

Currently I am working to get new SELinux policy to RHEL8 in a similar fashion as it was done in Fedora. I would like to ask you to add bfd_multi in the selinux-policy corenetwork so that BFD daemon from FRR can bind to it:

network_port(bfd_multi, tcp,4784,s0, udp,4784,s0)

Michale,

It's quite late in RHEL 8.7 life cycle now, is it okay to deliver in 8.8?

Hi Zdenek,

I know it is late, creating the policy for FRR took longer than I thought it would. Sure we can do this in 8.8, I was just hoping to push the new selinux policy with frr to 8.7. I think the policy is ready but the only problem is the bfdd port which effectively makes bfdd unusable, because it won't start without the port. I don't suppose there is a way around this, is there?

Solved for now by using corenet_udp_bind_all_unreserved_ports, let's move this one to 8.8.

Commit to backport:
commit eccebdd167cc32e87c9b23b5b07e96e13f7a7568
Author: Zdenek Pytela <zpytela>
Date:   Thu May 12 11:23:12 2022 +0200

    Label port 4784/tcp and 4784/udp with bfd_multi

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 (selinux-policy 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-2023:2965