action #45731
closed
Bug: firewalld is blocking everything until it's restarted
Added by flacco almost 6 years ago.
Updated about 3 years ago.
Description
After a reboot of an invis server the new firwalld daemon is blocking everything until it is restarted.
- Related to action #36079: Modify sine2 / invisAD-setup to be compatible with leap 15 added
- Status changed from New to In Progress
- % Done changed from 0 to 80
It seems that firewalld starts to early. The original service-unit file defines to start firewalld before "network-pre.target":
"[Unit]
Description=firewalld - dynamic firewall daemon
Before=network-pre.target
Wants=network-pre.target
After=dbus.service
After=polkit.service
..."
Starting firewalld later brings the risk that the system runs for a few moments without the firewall. Sytemd knows three different network targets. "network-pre.target", "network.target" and "network-online.target". The last one means that all network interfaces are up and online. Starting the firewall before this target should be secure enough.
Changing the firewalld service-unit file to:
"[Unit]
Description=firewalld - dynamic firewall daemon
After=network-pre.target
Before=network-online.target
After=dbus.service
After=polkit.service
..."
did the job. This should be secure enough.
... but I don't know if we should place a "Wants=network.online.target" in the service-unit file?
firewalld does not start to early. It works on my system. I am unable to reproduce this issue.
- Target version changed from 14.0 to Future
- Related to deleted (action #36079: Modify sine2 / invisAD-setup to be compatible with leap 15)
- Target version changed from Future to 14.1
- Due date changed from 2019-01-11 to 2019-02-28
- Target version changed from 14.1 to 14.2
- Due date changed from 2019-02-28 to 2019-08-31
- Status changed from In Progress to Workable
- Status changed from Workable to Closed
- % Done changed from 80 to 100
Also available in: Atom
PDF