Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1660400

Summary: [RFE] need to add button for adding custom ports in firewall tab inside cockpit
Product: Red Hat Enterprise Linux 8 Reporter: Shivam Gupta <shivagup>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.0Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:03:19 UTC Type: Feature Request
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: 1721414, 1721548    
Bug Blocks:    

Description Shivam Gupta 2018-12-18 09:32:36 UTC
Description of problem: Need an button for adding a particular port and IP address in the firewall inside cockpit. Only services can be added using firewall for a default port but if require to add a particular port for particular IP then there is no any option.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Only services can be add in the firewall.


Expected results: need an option for adding IP and ports in the firewall by using the cockpit which makes more easy for an administrator to allow particular IP or network through firewall for a specific port.


Additional info: In the production environment, It is necessary to whitelist only authorised IPs for accessing the content on server through a particular port. If an administrator wants to allow only some sets of IPs for a particular port through firewall then it makes it easier if there is an option for that in cockpit.

Rather than running complex commands through terminal it is more easy to do firewall configuration using cockpit if this option will be introduced.

Comment 1 Martin Pitt 2019-04-02 06:51:40 UTC
I devote this bug to the "add custom ports" half of this report. This is being developed in <https://github.com/cockpit-project/cockpit/pull/11420>.

The "particular IP" half of this is part of the "add support for zones" story, and tracked in bug 1678473.

Comment 4 Martin Pitt 2019-08-01 09:40:59 UTC
firewalld got fixed, can you please re-test?

Comment 7 errata-xmlrpc 2019-11-05 22:03:19 UTC
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://access.redhat.com/errata/RHBA-2019:3518