I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files.

All servers are up to date.

By "just noticed" I mean that I finally investigated why a newly rebooted VM failed to allow NFS connections. Prior to doing that. I'd been stopping the firewall to get access, then restarting the firewall after setting the eth1 interface to ACCEPT. This time I took a look at iptables and found that eth1 was set to REJECT, before I stopped the firewall. Because it was obvious that firewalld had been started by systemd by noticing the output of iptabled -nvL had the same set of rules you can see when firewalld is restarted, except that after restart interface eth1 is set to ACCEPT.

I assume there must be a different set of configuration files that are accessed upon reboot than those accessed upon firewalld restart.

Note that all CentoOS 7 machines (VM and hardware) in our data center have this same issue.

Anyone know where and what those files are?



Re: Firewalld

By Gordon Messmer at 10/12/2015 - 13:17

On 10/11/2015 03:00 PM, Emmett Culley wrote:
Rather than paraphrasing, could you show the specific rules, chains, or
policies you're talking about? A standard firewalld rule set has the
INPUT policy set to ACCEPT, with a terminal REJECT rule. An INPUT_ZONES
table will direct to an IN_public table, with log, deny, and accept rules.

Typically, the only rule that references an interface is the one in
INPUT_ZONES that "goto"s IN_public_allow. It is neither REJECT nor
ACCEPT, so it's really hard to guess what you're seeing that you don't
expect to see.

Re: Firewalld

By Emmett Culley at 10/12/2015 - 21:23

On 10/12/2015 10:17 AM, Gordon Messmer wrote:
Contents of iptables INPUT_ZONE upon reboot

Contents on iptables INPUT_ZONE after running 'systemctl restrat firewalld'

I expect to see the second output upon reboot.


Re: Firewalld

By Gordon Messmer at 10/13/2015 - 01:03

On 10/12/2015 06:23 PM, Emmett Culley wrote:
Thanks, that's a lot more clear. Weird, though. Does
/etc/sysconfig/network-scripts/ifcfg-eth1 specify a "ZONE="? Are you
using the "network" or the "NetworkManager" service?

Re: Firewalld

By Emmett Culley at 10/13/2015 - 09:15

On 10/12/2015 10:03 PM, Gordon Messmer wrote:
Here are the configuration files:





Re: Firewalld

By Gordon Messmer at 10/13/2015 - 15:51

On 10/13/2015 06:15 AM, Emmett Culley wrote:
In that case, specify a ZONE in ifcfg-eth1.

If you look at ifup-eth, you'll see that firewall-cmd is called during
interface configuration. If no zone is specified, the default is used.
I believe that firewalld starts first, configures the firewall
correctly, and then the "network" service starts later and sets both
interfaces into the default zone.

If you specify ZONE=trusted in ifcfg-eth1, then it'll be placed into
that zone.

Re: Firewalld

By Ian Mortimer at 10/11/2015 - 23:35

The saved rules are under /etc/firewalld/zones. The rules for the
default zone should be the ones loaded. The default zone is defined
in /etc/firewalld/firewalld.conf.

Re: Firewalld

By Paul Heinlein at 10/12/2015 - 11:45

It may be worth noting that most firewalld changes require two
invocations of firewall-cmd, one with "--permanent" and one without:

# this makes an immediate change that will not last past next
# reboot or service restart
firewall-cmd --zone="public" --set-target="ACCEPT"

# this makes no immediate change, but it will take effect at
# next reboot or service restart
firewall-cmd --zone="public" --set-target="ACCEPT" --permanent