Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 84423 - Installer pays no attention to "no firewall" request
Installer pays no attention to "no firewall" request
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-02-16 13:07 EST by David J Craigon
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-18 11:21:27 EST
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 David J Craigon 2003-02-16 13:07:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
I've installed RH 8.0, and when setting the Firewall to no firewall on the
install, absolutly no attention is paid!

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

How reproducible:

Steps to Reproduce:
1.Install RH 8.0 and set...
2.the Firewall to "No Firewall" 
3.Upon installation /etc/init.d/iptables is still run in rc5.d, and the ports
are blocked. 

Expected Results:  All ports unblocked

Additional info:

Also changing the firewall settings using the GUI tool doesn't work either- stay
stuck on High, regardless. Only solution I've found is to /etc/init.d/iptables
stop (this is reported elsewhere as another bug).
Comment 1 Michael Fulbright 2003-02-17 10:00:09 EST
I have seen no problems with this feature working.

Was the iptables file it is loading created by the installer or was it created
Comment 2 David J Craigon 2003-02-18 11:21:27 EST
I'm not so sure about this now, looking again. Sorry to bother you... I'll try
to reopen this is there is a problem in future.

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