Bug 101841 - Extra 'iptables' string in /etc/sysconfig/iptables output
Summary: Extra 'iptables' string in /etc/sysconfig/iptables output
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-config-securitylevel
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-07 15:04 UTC by Steve Bonneville
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-08-07 18:29:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Example /etc/sysconfig/iptables file. (668 bytes, text/plain)
2003-08-07 15:06 UTC, Steve Bonneville
no flags Details

Description Steve Bonneville 2003-08-07 15:04:54 UTC
Description of problem:

The new ruleset is written to /etc/sysconfig/iptables with several rules
prepended with the string 'iptables', which breaks the configuration (see
second example line):

   -A FORWARD -j RH-Firewall-1-INPUT
   iptables -A RH-Firewall-1-INPUT -i lo -j ACCEPT

The error on 'service iptables restart':

[root@as /]# service iptables restart
Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: filter                    [  OK  ]
Unloading iptables modules:                                [  OK  ]
Applying iptables firewall rules: Bad argument `iptables'
Error occured at line: 10
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
                                                           [FAILED]
[root@as /]#

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

How reproducible:  
Every time.  Run redhat-config-securitylevel and click 'Ok' to get the default
configuration.

Comment 1 Steve Bonneville 2003-08-07 15:06:08 UTC
Created attachment 93485 [details]
Example /etc/sysconfig/iptables file.

Comment 2 Bill Nottingham 2003-08-07 18:29:58 UTC
Fixed in 1.2.1-1.


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