On 28/10/2018 21:48, Patrick Shanahan wrote:
* Dave Plater <dplater.list@gmail.com> [10-28-18 14:04]:
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked?
why would it have anything to do with wicked?
According to the man page: "If NetworkManager is not in use and firewalld gets started after the network is already up" but it doesn't say what starts it. For the requesters this is firewalld after boot: # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org