iptables disabled in chkconfig but starting on its own
Posted: 2017/08/28 20:19:07
I run a Cloudera cluster and have iptables disabled on the out-of-band servers, but for some reason the iptables daemon starts without rules.
Here is a little more info. I am running CentOS 6.9 in Runlevel 3:
-I have turned iptables off in chkconfig -- chkconfig iptables off
-I have turned iptables off in the live session -- service iptables stop
-When I check the status of iptables -- service iptables status, I get iptables: Firewall is not running.
That is all great, but then later (Not sure if it is a day later or a week later, but it is definitely not an hour later) when I check the status of iptables, I get:
This indicates to me that the firewall is started, but without the rules. Is that correct? When I run service iptables stop, I get:
Then the status goes back to Firewall is not running. This may or may not be causing problems with the cluster, but either way, I want to know why the daemon seems to be starting on its own.
Thanks for any help you can provide.
Here is a little more info. I am running CentOS 6.9 in Runlevel 3:
-I have turned iptables off in chkconfig -- chkconfig iptables off
-I have turned iptables off in the live session -- service iptables stop
-When I check the status of iptables -- service iptables status, I get iptables: Firewall is not running.
That is all great, but then later (Not sure if it is a day later or a week later, but it is definitely not an hour later) when I check the status of iptables, I get:
Code: Select all
Table: filter
Chain INPUT (policy ACCEPT)
num target prot opt source destination
Chain FORWARD (policy ACCEPT)
num target prot opt source destination
Chain OUTPUT (policy ACCEPT)
num target prot opt source destination
Code: Select all
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
Thanks for any help you can provide.