Description of problem: ----------------------- When attempting to change the default zone through either the graphical Firewall console (firewall-config) or the command line (firewall-cmd --set-default-zone=home), the following error gets thrown in both the gui and terminal: Error: COMMAND_FAILED: '/sbin/iptables -D INPUT_ZONES -t filter -i wlp4s0 -g IN_public' failed: iptables: No chain/target/match by that name. Version-Release number of selected component (if applicable): ------------------------------------------------------------- firewalld.noarch-0.3.9.3-1.fc20 How reproducible: ----------------- Always Steps to Reproduce: ------------------- Change default zone in firewall-config OR firewall-cmd --set-default-zone=home
I have no idea what can be the culprit so I need to see a lot more info: 1) add 'FIREWALLD_ARGS=--debug=2' into /etc/sysconfig/firewalld 2) # > /var/log/firewalld 3) # systemctl restart firewalld 4) attach output of the following command # firewall-cmd --list-all-zones | egrep -A8 'active|default' 5) attach output of the following command # iptables-save 6) # firewall-cmd --set-default-zone=home 7) attach any file you find in /etc/firewalld/zones/ 8) attach /var/log/firewalld thanks
Created attachment 895589 [details] Output for debugging as requested
I should note that I performed the --set-default-zone command now without any issues while I was collecting the command outputs. I experienced this issue multiple times yesterday though, which was after several reboots.
OK, if you happen to reproduce it again, try to collect the info once more. Thanks
Hello, I'm having a similar problem, although I trying to block two subnets which keep hammering fail2ban. I've attached the info you requestd above. Let me know if you need any additional information. Thanks!
Created attachment 901103 [details] output of iptables cmd
Created attachment 901104 [details] output of firewall cmd
Created attachment 901105 [details] firewalld.log
Created attachment 901106 [details] from /firewalld/zones
Created attachment 901113 [details] from /firewalld/zones
Additional information, I was trying to apply the rule to the "Trusted" zone... as a test I found I was able to apply the rule to the "Home" zone and it appears to be working. The problem that I am having now is that I have some applications which I had configured to use UPNP, and from what I gather that is not supported by firewalld. Use of the "Trusted" zone avoided the UPNP issue.
Sorry for the delay Gerald, your firewalld.log shows: '/sbin/iptables -t filter -A ACCEPT_log -s 61.174.51.0/24 -p tcp -m conntrack --ctstate NEW -j LOG --log-level warning' failed: iptables: No chain/target/match by that name. because it tries to add a rule into nonexistent ACCEPT_log chain. I tried to use your zones (especially the 'trusted' which seems to cause the problem) here and the rule is correctly added into IN_trusted_log: /sbin/iptables -t filter -A IN_trusted_log -s 61.174.51.0/24 -p tcp -m conntrack --ctstate NEW -j LOG --log-level warning What firewalld version do you use ? Can you try firewalld-0.3.10 ? (0.3.10 is currently moving from updates-testing into stable)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.