Bug 124861 - Using kickstart installation, firewall configuration fails
Summary: Using kickstart installation, firewall configuration fails
Keywords:
Status: CLOSED DUPLICATE of bug 123867
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-31 15:09 UTC by Pavel Urban
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:03:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Urban 2004-05-31 15:09:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)
Gecko/20040127

Description of problem:
When I try

firewall --enabled --port=ssh:tcp --port=dns:tcp --port=dns:udp

in ks-file during http://... kickstart installation, no firewall
configuration is in fact created. When I look at anaconda-ks.cfg on
installed system, I can see

firewall --enabled --port=ssh:tcp --port=dns:tcp --port=dns:udp
--port=ssh:tcp --port=dns:tcp --port=dns:udp

(all port arguments created twice).

My command line arguments:

linux text ksdevice=eth0 ks=http://10.0.0.1/ks/ks.cfg



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


How reproducible:
Always

Steps to Reproduce:
1. create network ks.cfg
2. add firewall --enabled --port=ssh:tcp --port=dns:tcp --port=dns:udp
to it
3. try network kickstart installation
    

Actual Results:  iptables -L -n shows no firewall rules applied, no
/etc/sysconfig/iptables file is created

Expected Results:  /etc/sysconfig/iptables file created with proper
configuration

Additional info:

Comment 1 Jeremy Katz 2004-06-01 20:30:37 UTC
Fixed in CVS for U3

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:53 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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