No Network Interfaces Bound to Firewalld Zone

Posted March 22, 2017 11.3k views

Using a fresh build of CentOS 7.3, I am attempting to follow the tutorial at

However there are no active zones when I use “sudo firewall-cmd –get-active-zones” as per the tutorial. I believe this is due to no network interface being bound to a zone. Using comand “sudo firewall-cmd –zone=public –list-all
public”. I can see that there are no interfaces bound to the public zone (which I presume is what I need). I have used:

  • $ sudo firewall-cmd –permanent –add-service=ssh
  • $ sudo firewall-cmd –permanent –add-service=http
  • $ sudo firewall-cmd –permanent –add-service=https
  • $ sudo firewall-cmd –permanent –add-port=80/tcp
  • $ sudo firewall-cmd –permanent –add-port=443/tcp
  • $ sudo firewall-cmd –reload

But I don’t think any of this is helping without an active zone. My goal is to have ports 80 and 443 show as opened after an external port scan, but they continue to show as closed. Please advise.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers

To assign an interface to a zone, run:

  • sudo firewall-cmd --zone=public --change-interface=eth0

Here is another useful command:

  • sudo firewall-cmd --get-zone-of-interface=eth0

It allows you to find which zone to which a particular interface is bound.

  • Your answer save my time.When i execute firewall-cmd --get-active-zones, i get no return.My default zone is also public,so i add eth0 as public interface, then i get right active zone

I just build a Centos 7.5 system and my interfaces weren’t assigned to any zone. I added source ip ranges to trusted and created a few other zones with source ip ranges. All the zones plus the rules in the public zone are working.

I don’t know if it’s a bug or a feature, but not having to force an interface to a zone seems to be beneficial.