Description of problem: In man 5 firewalld.zone, typos in rule section: - "general rule structure" has superfluous "/" at end of opening rule tag; - "rule structure for source black or white listing" has same error; - error causes rule tag to be prematurely closed; - following the documented structure in a zone file causes firewalld to fail to load the zone file; Version-Release number of selected component (if applicable): - firewalld.noarch-0.3.9.3-1.fc19 How reproducible: - always Steps to Reproduce: - man 5 firewalld.zone - use documented rule structure in zone file (eg, to blacklist a particular IP) Actual results: - following the given structure yields zone file rules like: <rule family="ipv4"/> <source address="11.11.22.22"/> <drop/> </rule> - which fails to load, with journals like firewalld[30037]: 2014-04-26 11:05:39 ERROR: INVALID_RULE: no element, no action: rule family="ipv4" firewalld[30037]: 2014-04-26 11:05:39 ERROR: Invalid rule: Action outside of rule firewalld[30037]: 2014-04-26 11:05:39 ERROR: Failed to load zone file '/etc/firewalld/zones/public.xml': Expected results: - zone file loads and source address is blacklisted Additional info: - works correctly once superfluous "/" is deleted from initial rule tag - typo in man documentation
Fixed upstream, thanks. https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=012608e9d099e13e2672cfafd58c188cada0b90f
firewalld-0.3.10-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/firewalld-0.3.10-1.fc20
Package firewalld-0.3.10-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firewalld-0.3.10-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6834/firewalld-0.3.10-1.fc20 then log in and leave karma (feedback).
firewalld-0.3.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.