Red Hat Bugzilla – Bug 811240
during boot firewalld is not ready when NetworkManager needs it
Last modified: 2012-04-24 00:25:53 EDT
When I run firewalld and NetworkManager (NM) with debug messages on I see that during boot firewalld begins to start (several seconds) after NM. That is bad - NM needs to inform firewalld when making network interfaces up otherwise they will be in no zone until firewalld starts.
I suggest these changes in firewalld.service:
- selfexplaining, needed to start firewalld before NM
- to tell systemd when firewalld is ready
- systems.service(5) says:
Behaviour of dbus is similar to simple, however it is expected that the daemon acquires a name on the D-Bus bus, as configured by BusName=. systemd will proceed starting follow-up units after the D-Bus bus name has been acquired. Service units with this option configured implicitly gain dependencies on the dbus.socket unit.
3) remove After=dbus.target
- I think the 'Type=dbus' does the same.
Note: I took me a plenty of time to get this solution because I had been trying either (1) or (2) but not both of them together :-(
firewalld-0.2.5-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing firewalld-0.2.5-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
firewalld-0.2.5-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.