Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 78923

Summary: Can't change firewall setting from high
Product: [Retired] Red Hat Linux Reporter: Alan McCaig <alanmccaig>
Component: redhat-config-securitylevelAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:50:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alan McCaig 2002-12-03 16:55:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
when installing Redhat 8.0 i chose to have medium security. After installation 
and started setting stuff up i noticed no one from outside localhost could 
connect or nmap me. i checked the firewall setting which was on high i changed 
it to normal and still no one could connect. i checked it again and for some 
reason which i dont knwo it was back on high ive tryed turning it completly 
off and it will still go back to high. ive tryed changing it through gui and 
also using teh setup command. Still can't get trafic from outside and get get 
setting of high think it is a bug in the software

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

How reproducible:

Steps to Reproduce: up firewall config
2.change setting from high security it then try to connect and cant go back in and it is on high secutiy 
again it is as if it dont save it

Actual Results:  it never saved teh setting

Expected Results:  shoudl have saved it

Additional info:

Comment 1 Harald Hoyer 2003-01-09 13:35:01 UTC
assigning to correct component

Comment 2 Brent Fox 2003-01-09 19:22:56 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:50:15 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.