Well done! I did not have the latest version. But, after a "yum update firewalld", it's the same.
I was with default public zone : # firewall-cmd --get-active-zones public: p2p1
I check the INPUT ZONES : # iptables -v -n -L INPUT_ZONES Chain INPUT_ZONES (1 references) pkts bytes target prot opt in out source destination 0 0 IN_ZONE_public all -- p2p1 * 0.0.0.0/0 0.0.0.0/0
I change for work defaut zone : # firewall-cmd --set-default-zone=work # firewall-cmd --get-active-zones work: p2p1
The default zone is changed, but not the iptables rules : # iptables -v -n -L INPUT_ZONES Chain INPUT_ZONES (1 references) pkts bytes target prot opt in out source destination 0 0 IN_ZONE_public all -- p2p1 * 0.0.0.0/0 0.0.0.0/0
But, after a reboot it's OK : [root@localhost ~]# firewall-cmd --get-active-zones work: p2p1
The check is OK : [root@localhost ~]# iptables -v -n -L INPUT_ZONES Chain INPUT_ZONES (1 references) pkts bytes target prot opt in out source destination 0 0 IN_ZONE_work all -- p2p1 * 0.0.0.0/0 0.0.0.0/0
Philippe.
Le 23/05/2012 16:48, Jiri Popelka a écrit :
On 05/23/2012 12:26 AM, Philippe Marcovici wrote:
If the zoning is done via the command "firewall-cmd --set-default-zone=xxx" (no zone declaredin /etc/sysconfig/network-scripts/ifcfg-<iface>) a restart is required. Is this the desired behavior?
In my case no restart is needed. Do you have the latest firewalld, i.e. firewalld-0.2.5 ? _______________________________________________ firewalld-users mailing list firewalld-users@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/firewalld-users