Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 105865

Summary:	Firewall rules set after choosing "no firewall"
Product:	[Fedora] Fedora	Reporter:	Jos Vos <jos>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED DUPLICATE	QA Contact:	Mike McLean <mikem>
Severity:	high	Docs Contact:
Priority:	high
Version:	rawhide	CC:	chris.ricker, dengen40, tammy.c.fox
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:	2006-02-21 18:58:49 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:
Bug Depends On:
Bug Blocks:	100643

Description Jos Vos 2003-09-28 18:22:06 UTC

When "no firewall" is chosen in Anaconda, after installation still a set of
default firewall rules seem to exist (I couldn't even ssh to the installed
system).

Comment 1 Michael Schwendt 2003-09-28 18:59:25 UTC

FWIW, I can confirm this.

Comment 2 Rick Ross 2003-09-29 00:35:12 UTC

It happened to me, too. It was easy enough to disable, and SSH was ok after that.

Rick

Comment 3 Pavel 2003-09-29 11:44:18 UTC

I can confirm it, too.

Comment 4 Jeremy Katz 2003-09-29 21:20:15 UTC

Fixed in CVS

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

Comment 5 Bill Nottingham 2003-09-30 03:59:07 UTC

*** Bug 105974 has been marked as a duplicate of this bug. ***

Comment 6 Dwight Engen 2003-10-15 04:15:43 UTC

I don't know what Status: RESOLVED means exactly, but the fix apparently didn't
make it into test3.

Comment 7 Red Hat Bugzilla 2006-02-21 18:58:49 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.