Bug 76712 - a couple minor cleanup fixes for /etc/init.d/iptables
Summary: a couple minor cleanup fixes for /etc/init.d/iptables
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: iptables
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-25 09:39 UTC by Robert P. J. Day
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-07-01 09:51:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Robert P. J. Day 2002-10-25 09:39:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
  not errors, but three suggestions for cleanup of the iptables
script /etc/init.d/iptables:

1) line 54: chains=`cat /proc/net/ip_tables_names ...`

   this variable should really be "tables", not "chains",
   although this will still work since the variable is still
   used consistently throughout the script.  (this occurs
   more than once in the script.)

2) both lines 57 and 68, which ostensibly clear entries from
   the current tables, are immediately followed by a
   redundant "iptables -F".  again, not an error, but
   confusing if you're trying to figure out what those
   extra flushes are for.  apparently, nothing.  (this
   also occurs more than once in the script.)

3) references to all possible combinations of tables and
   chains do not mention the newer combinations of the
   mangle table with the INPUT, FORWARD and POSTROUTING
   chains, again in more than one place.

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


How reproducible:
Always

Steps to Reproduce:
1. see /etc/init.d/iptables
2.
3.
	

Additional info:

Comment 1 Michael Schwendt 2002-10-25 20:09:38 UTC
3) is duplicate of bug #75723.


Comment 2 Thomas Woerner 2003-07-01 09:51:37 UTC
fixed in iptables-1.2.7a-1.


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