Description of problem: When linking these modules statically in the kernel firewall-config fails to obtain any zones: "ip_tables", "ip6_tables", "nf_conntrack", "ebtables" These modules are actually present in my running kernel, but firewall-config fails to show/parse any firewall zones. Please relieve this constrain in firewall-config. Version is: Name : firewalld Architektur : noarch Version : 0.2.12 Ausgabe : 4.fc18
Okay, above is non-sense. the actual problem seems to be: Mär 24 21:35:29 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:29 DEBUG1: start() Mär 24 21:35:29 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:29 ERROR: ebtables not usable, disabling ethernet bridge firewall. Mär 24 21:35:29 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:29 ERROR: ebtables not usable, disabling ethernet bridge firewall. Mär 24 21:35:29 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:29 Traceback (most recent call last): Mär 24 21:35:29 localhost.localdomain firewalld[11645]: File "/usr/lib/python2.7/site-packages/firewall/server/decorators.py", line 40, in handle_exceptions Mär 24 21:35:29 localhost.localdomain firewalld[11645]: return func(*args, **kwargs) Mär 24 21:35:29 localhost.localdomain firewalld[11645]: File "/usr/lib/python2.7/site-packages/firewall/server/firewalld.py", line 75, in start Mär 24 21:35:29 localhost.localdomain firewalld[11645]: return self.fw.start() Mär 24 21:35:29 localhost.localdomain firewalld[11645]: File "/usr/lib/python2.7/site-packages/firewall/core/fw.py", line 102, in start Mär 24 21:35:29 localhost.localdomain firewalld[11645]: self._set_policy("ACCEPT") Mär 24 21:35:29 localhost.localdomain firewalld[11645]: File "/usr/lib/python2.7/site-packages/firewall/core/fw.py", line 370, in _set_policy Mär 24 21:35:29 localhost.localdomain firewalld[11645]: self._ip4tables.set_policy(policy, which) Mär 24 21:35:29 localhost.localdomain firewalld[11645]: File "/usr/lib/python2.7/site-packages/firewall/core/ipXtables.py", line 160, in set_policy Mär 24 21:35:29 localhost.localdomain firewalld[11645]: for chain in CHAINS[table]: Mär 24 21:35:29 localhost.localdomain firewalld[11645]: KeyError: 'security' Mär 24 21:35:30 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:30 DEBUG1: zone.addInterface('', 'wlan0') Mär 24 21:35:30 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:30 DEBUG1: INVALID_ZONE Mär 24 21:35:30 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:30 DEBUG1: config.listZones() Mär 24 21:35:30 localhost.localdomain firewalld[11645]: 2013-03-24 21:35:30 DEBUG1: getDefaultZone()
$ sudo cat ip_tables_names security raw nat mangle filter
Created attachment 715963 [details] patch I'll push this patch upstream once https://fedorahosted.org/rel-eng/ticket/5546 is fixed.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.