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:
It would be useful if firewalld knew what port was associated with the rsyncd service.  In this way I could run firewall-cmd --add-service=rsyncd

Version-Release number of selected component (if applicable):firewalld-0.3.9-7.el7.noarch


How reproducible:100%


Steps to Reproduce:
1.firewall-cmd --get-services |grep rsy
2.
3.

Actual results:
no rsyncd service defined

Expected results:
rsyncd service defined

Additional info:

Added upstream
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=99dccf9ad72e067a68a541de62b5bc3ef52655a7

Hello,

This is also true for many other frequently used services, that I've enumerated in bug #1155972 .

The necessary ports are already identified and well-documented in the .macro files included in the shorewall RPM package (present in EPEL); it only takes converting them in firewalld's service .xml files and including them in the official firewalld RPM.

IMHO, common denominations for these services (in firewalld and shorewall) should greatly reduce confusion and ease migration.

I am willing to help to this conversion, by translating service xmls myself, if someone quickly includes these in the official package.

Best regards,
Răzvan

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://rhn.redhat.com/errata/RHBA-2015-2422.html