Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 242190 - Firewall open ports are not kept or set.
Firewall open ports are not kept or set.
Status: CLOSED DUPLICATE of bug 227285
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Thomas Woerner
Depends On:
  Show dependency treegraph
Reported: 2007-06-01 22:59 EDT by A. Brown
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-08 11:14:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description A. Brown 2007-06-01 22:59:15 EDT
Description of problem:
when entering custom ports to open, the settings are not kept, and disappear
when the dialog is reopened, even if you click apply or okay.

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

How reproducible:
Will not keep firewall port opening settings at all.

Steps to Reproduce:
1. Open firewall/SELinux dialog from menu or command line
2. enter a port number
3. click apply or okay
4. reopen the dialog and the ports are no longer stored.
Actual results:
The ports I set to open are not kept when the dialog is closed, perhaps never
opening them.

Expected results:
Ports should still be there when I reopen the dialog and it should open them in
the firewall.

Additional info:

email me a iamscottevil@yahoo.com if you need to test cases.
Comment 1 Stuart Martin 2007-06-06 17:34:25 EDT
Seeing this issue on both i386 and x86_64.

Temporary fix is to run "setup" from a terminal and add the custom port, will
then show up in the main GUI.
Comment 2 Thomas Woerner 2007-06-08 11:14:21 EDT

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

Note You need to log in before you can comment on or make changes to this bug.