http://bugzilla.suse.com/show_bug.cgi?id=1166792 Bug ID: 1166792 Summary: systemd unit files: use "firewall" instead of "SuSEfirewall2" specifically. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: jnelson-suse@jamponi.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- A number of systemd units rely on "SuSEfirewall2.service" (or "SuSEfirewall2_init.service") I believe it would be preferable to have them rely on something more symbolic like "_a_ firewall service, such as SuSEfirewall2 or shorewall or firewalld". Such a thing seems like it would be possible. /usr/lib/systemd/system/docker.service:After=network.target lvm2-monitor.service SuSEfirewall2.service /usr/lib/systemd/system/wickedd-auto4.service:After=local-fs.target dbus.service SuSEfirewall2_init.service /usr/lib/systemd/system/wickedd-dhcp4.service:After=local-fs.target dbus.service SuSEfirewall2_init.service /usr/lib/systemd/system/wickedd-dhcp6.service:After=local-fs.target dbus.service SuSEfirewall2_init.service /usr/lib/systemd/system/wickedd-nanny.service:After=local-fs.target dbus.service SuSEfirewall2_init.service wickedd.service /usr/lib/systemd/system/wickedd.service:After=local-fs.target dbus.service isdn.service rdma.service SuSEfirewall2_init.service systemd-udev-settle.service -- You are receiving this mail because: You are on the CC list for the bug.