Red Hat Bugzilla – Bug 849572
Strange behaviour of iptables-save
Last modified: 2015-03-02 00:27:08 EST
Description of problem:
Strange behaviour of iptables-save. After service iptables stop command iptables-save print nothing to ouput. Then I run iptables -L and now iptables-save output three lines. I think that iptables -L is read only operation and this not may effect for iptables-save.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.service iptables stop
first iptables-save prints nothing
second iptables-save prints:
iptables-save# Generated by iptables-save v1.3.5 on Mon Aug 20 04:09:43 2012
:INPUT ACCEPT [22:1432]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [16:2896]
# Completed on Mon Aug 20 04:09:43 2012
same behaviour of both iptables-save commands
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
iptables-save dumps all IPv4 iptables rules. After service iptables stop, all netfilter firewall mudules are unloaded. Using "iptables -L" loads the base firewall modules if they are not loaded already, this results in the standard accept policy rules.
This is expected behaviour.