Bug 27659

Summary: iptables init script uses ipchains, bad options for iptables-restore
Product: [Retired] Red Hat Linux Reporter: Derrick Hamner <derrickh>
Component: iptablesAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-02-16 01:11:57 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 Derrick Hamner 2001-02-14 21:36:37 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)


The iptables init script uses ipchains to flush the existing chains in the 
start sequence. ipchains does not work with kernel 2.4. The init script 
also calls iptables-restore -f -p. iptables-restore does not accept those 
options.

Reproducible: Always
Steps to Reproduce:
1.touch /etc/sysconfig/iptables
2.service start iptables
3.
	

Actual Results:  
ipchains: Incompatible with this kernel
/sbin/iptables-restore: invalid option -- p
/sbin/iptables-restore: invalid option -- f

Expected Results:  iptables should be used to flush existing chains in the 
start sequence. iptables-restore should not be passed any options.
Comment 1 Glen Foster 2001-02-16 01:11:53 UTC 
We (Red Hat) should really try to resolve this before next release.
Comment 2 Karsten Hopp 2001-02-19 16:56:07 UTC 
Fixed in iptables-1.2.0-8
ipchains-restore will be called with paramater -c to save counters.