Bug 449938

Summary: Firewall not disabled in system-config-firewall
Product: [Fedora] Fedora Reporter: Joshua Rosen <bjrosen>
Component: firestarterAssignee: Damien Durand <splinux25>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 9CC: leamhall, livinded, subhash.vinchurkar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 16:30:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Rosen 2008-06-04 11:55:13 UTC
Description of problem: The DISABLE button in the firewall GUI doesn't disable
the firewall. I was able to disable the the firewall by disabling iptable with
Webmin.


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


How reproducible:100%


Steps to Reproduce:
1.Invoke system-config-firewall
2.
3.
  
Actual results: The GUI claims that the firewall is disabled but it's not.


Expected results:


Additional info:

Comment 1 Joe Rozner 2008-06-16 03:04:23 UTC
I came across this problem last night and can confirm it, though there is no
real output given and not much other information to contribute.

Comment 2 Joe Rozner 2008-07-04 01:06:33 UTC
seems to be fixed after the last update.

Comment 3 Subhash 2008-08-18 06:32:27 UTC
This problem is also observed by me. 

1.
Can you please let me know what is the exact fix for this, we need to know this for proper functioning of our product to be supported on fedora linux. 

2.
I also see that firewall-behavior is many times unexpected. Even if you allow some of the specific ports as exceptions, it sometimes works and sometimes fails. The exact ratio of fail-success is not predictable.

If any patch/rpm is available to fix this problem, please let let me know.

Comment 4 Leam 2008-10-14 14:00:53 UTC
I found a similar circumstance but it was self-induced. A manual edit of /etc/sysconfig/system-config-firewall to make it "--disabled" didn't change anything because /etc/sysconfig/iptables file still existed with rules that blocked my service. 

Running system-config-firewall, ensuring the "Enabled" box is NOT checked, and clicking "Ok" so that it runs it's stuff and removes the /etc/sysconfig/iptables file worked for me.

Comment 5 Bug Zapper 2009-06-10 01:23:53 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2009-07-14 16:30:18 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.