Bug 1563629
Summary: | RFE: Not able to add any description for particular port via "firewall-cmd" command | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Nakul Dev <ndev> |
Component: | firewalld | Assignee: | Eric Garver <egarver> |
Status: | CLOSED MIGRATED | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.1 | CC: | ajawarka, jmaxwell, mmhatre, nonalodiaasirei, sukulkar, todoleza |
Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
Target Release: | 8.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-21 10:14:51 UTC | Type: | Story |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1682341 | ||
Bug Blocks: |
Description
Nakul Dev
2018-04-04 11:09:35 UTC
The firewalld way for this is to create a custom service and add it the zone. The service name can provide context and the short can provide further information. e.g. # firewall-cmd --permanent --new-service=foobar # firewall-cmd --permanent --service=foobar --set-short="this is my description of foobar" # firewall-cmd --permanent --service=foobar --add-port=3384/tcp # firewall-cmd --permanent --add-service foobar # firewall-cmd --permanent --list-all public ... services: dhcpv6-client ssh foobar # firewall-cmd --permanent --service=foobar --get-short this is my description of foobar Hi, Just wanted to check, if there is any progress on this RFE. (In reply to Amol Jawarkar from comment #10) > Hi, > > Just wanted to check, if there is any progress on this RFE. No progress nor estimate of when it'll be done. *** Bug 1739421 has been marked as a duplicate of this bug. *** Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. I'm writing this comment because it wasn't until I restarted the systemctl with systemctl restart firewalld with sudo: https://geometrydashlite.co I had attempted every suggestion above. the VM was restarted. In VNIC, I even made the rules. However, it wasn't fixed until the service was restarted. The Oracle Cloud Network environment VM: Compute Instance (using Oracle Linux 8 as a developer) https://access.redhat.com/articles/7032570 |