Bug ID 1008169
Summary Ufw isn't started on booting by systemd since it relies on a script (/etc/init.d/ufw) that doesn't exist
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Security
Assignee security-team@suse.de
Reporter junrrein@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Running "sudo ufw enable" enables and starts ufw for the current session.

In order for it be started automatically on system startup, it's necessary to
tell systemd to do so (systemctl status ufw).

However, upon booting, ufw is inactive.

"systemctl status ufw" outputs

~ $ systemctl status ufw
��� ufw.service - /etc/init.d/ufw Compatibility
   Loaded: loaded (/usr/lib/systemd/system/ufw.service; enabled; vendor preset:
disabled)
   Active: failed (Result: exit-code) since mi�� 2016-11-02 13:35:51 ART; 43min
ago
  Process: 1066 ExecStop=/etc/init.d/ufw stop (code=exited, status=203/EXEC)
  Process: 1062 ExecStart=/etc/init.d/ufw start (code=exited, status=203/EXEC)
 Main PID: 1062 (code=exited, status=203/EXEC)

The systemd unit file references /etc/init.d/ufw, which doesn't exist.

This same bug was reported against Openseuse Leap 42.1 [1].

[1] https://bugzilla.opensuse.org/show_bug.cgi?id=971327


You are receiving this mail because: