Why is firewalld not using NetworkManager interface zones?
After a reboot, FirewallD overwrites that ifcfg file, removing the ZONE (setting it to ZONE= ). NetworkManager then thinks that that interface has no zone, and now FirewallD assumes that the interface goes to the default ( public) zone. Not keeping the configuration set before the reboot.
How to remove interface from zone with centos8?
– Firewalld / Centos8 My issue is when I’m trying to remove interface from public (default) zone I get error: The interface is under control of NetworkManager and already bound to the default zone. The interface is under control of NetworkManager, setting zone to default. success
Can you remove an interface from a zone?
The interface is under control of NetworkManager, setting zone to default. success Public zone configuration: When I am stopping the NetworkManager it allows me to remove it. However when I start NetworkManager back again and restart firewalld the interface eth0 is back in public zone.
How to remove an interface from a firewall?
To remove an interface from a zone, I issued the following commands: firewall-cmd –zone=trusted –remove-interface=lo –permanent. firewall-cmd –reload. firewall-cmd –zone=trusted –list-all. However, the interface was still associated with the zone.
Why does firewalld think docker0 has no zone?
After the reboot, suddenly FirewallD thinks again that the docker0 has no zone. Check the zone of the docker0 interface as seen by FirewallD: And NetworkManager also thinks that it has no zone. But even more, it thinks that there are two connections (not just one as before) and that they both have no zone assigned.
How to change interface zone in firewalld using nmcli?
Sign in to your account Changing an interface (e.g. docker0) zone (e.g. trusted) that is controlled by NetworkManager using nmcli updates the zone in FirewallD and creates a ifcfg file. Before the change, FirewallD thinks that it has no zone.