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:
If a port-range is defined and i check the status of the port range, if its enabled per zone :

[root@nkresic ~]# firewall-cmd --permanent --query-port=20-25/tcp
yes

If i check the single port inside the range :

[root@nkresic ~]# firewall-cmd --permanent --query-port=22/tcp
no

ssh service works without problems with a port-range definition, its only the status of the port, returned by the firewall-cmd, that is the problem. 




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

firewalld-0.4.4.4-6.el7.noarch



How reproducible:

both through GUI of firewall-config or through firewall-cmd



Steps to Reproduce:
1. remove some port that you know you need for connectivity, i removed 22
2. add a port range where your port is a part of that range
3. connectivity works but --query-port reports that it shouldnt



Actual results:

firewall-cmd returns a port with restriction



Expected results:

firewall-cmd should recognize a port inside a permitted port range

Additional info:

*** This bug has been marked as a duplicate of bug 1404076 ***