On 29/10/2018 15:27, Carlos E. R. wrote:
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it. I just uninstalled, with -u, all firewall packages then reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report. Remember that on Linux, reinstallation typically doesn't change the configuration, so the results are the same as before.
SuSEfirewall2 is intentionally installed on 15.0 so that you can migrate the previous existing configuration; after doing that, you can uninstall it.
There is a script to do the migration.
If Patrick is correct, firewalld is started*after* network is actually started, not at boot. So check the status after the network goes up.
I do not currently have a 15.0 system with wicked networking to verify.
I can vaguely remember installing SuSEfirewall2 after updating to 15.0, there's a script installed with firewalld - "susefirewall2-to-firewalld" for the rules migration. Thanks Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org