Bug 117753 - (iptables-save) "service iptables save" saves syntactically wrong rule in /etc/sysconfig/iptables
"service iptables save" saves syntactically wrong rule in /etc/sysconfig/ipta...
Status: CLOSED DUPLICATE of bug 111999
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: iptables (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Woerner
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2004-03-08 02:48 EST by Demosthenes T. Mateo Jr.
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:01:52 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 Demosthenes T. Mateo Jr. 2004-03-08 02:48:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
"service iptables save" creates this line in /etc/sysconfig/iptables:

-A RH-Firewall-1-INPUT -p icmp -m icmp any -j ACCEPT

Next time you do "service iptables start" you get this error:

Applying iptables firewall rules: Bad argument `any'

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

How reproducible:

Steps to Reproduce:
1. redhat-config-securitylevel-tui
2. select Enabled then create empty rule or select/add any port
3. save your options
4. service iptables start
5. service iptables save
6. service iptables restart

Actual Results:  Applying iptables firewall rules: Bad argument `any'
Error occured at line: 10
Try `iptables-restore -h' or 'iptables-restore --help' for more

Expected Results:  Should have restarted and activated the iptables rules.

Additional info:
Comment 1 Thomas Woerner 2004-03-09 11:43:27 EST

*** This bug has been marked as a duplicate of 111999 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:01:52 EST
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.