Firewalld service does not start on boot

The firewalld service is configured for the necessary ports I use, enabled, started but on each reboot I find that the service is not started. Is this behavior considered normal?
And I am exposed to the outside world threats. By-the-way, why SuSEFirewall2 was replaced with this firewalld s*** ?

What does the following show?

sudo systemctl status firewalld

And I am exposed to the outside world threats. By-the-way, why SuSEFirewall2 was replaced with this firewalld s*** ?

There are a number of existing threads discussing this topic…
https://forums.opensuse.org/showthread.php/529189-Problem-loading-firewall?highlight=firewalld
https://forums.opensuse.org/showthread.php/529290-can-anyone-provide-a-clear-overview-of-the-move-to-firewalld?p=2852651#post2852651
https://forums.opensuse.org/showthread.php/529169-yast2-firewall-launches-firewalld-GUI-since-most-recent-dup?highlight=firewalld

BTW, what is your inferred objection with using firewalld?

Maybe a firewall should be 100% reliable?

In YaST -> Services Manager firewalld is enabled and active, I can enter the config tool via YaST, but

sudo systemctl status firewalld
[sudo] password for root: 
● firewalld.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

On 4 machines I checked, 2 have this unbelievable status, 2 are up and running. 50% chance for having a firewall…

That’s not how a firewall works.

Ok, I found a solution for the problem - and it was SuSEfirewall2 service, after I disabled SuSEfirewall2.service the firewalld service works as expected.
Therefore it is an inconsistency in SuSEfirewall2 to firewalld replacement procedure.

What about SuSEfirewall2 - to me it was much more intuitive and trustworthy to use from a common user perspective than firewalld and its moronic interface - both gui & cmd, moreover that in addition cli is removed at ver 0.5

I get the idea that you are hijacking other one’s thread. But when you have four systems, do you mind in confirming that all four have the same version of openSUSE? After all we are ins a transition state moving from SuSEfirewall2 to firewalld, so e.g. Leap42.3 and older Tumbleweeds will still not have firewalld at all.

OK, my last reply in this thread: Yes, all 4 have been updated the last week and manually switched to firewalld, as described in the other thread linked above.

Unbelievable.

Yes, it is necessary to stop and disable SuSEfirewall2 before enabling/starting firewalld. It was a deliberate decision to leave the original firelwall in place (for obvious security/administrative reasons) until the administrator decides to invoke the changes.

What about SuSEfirewall2 - to me it was much more intuitive and trustworthy to use from a common user perspective than firewalld and its moronic interface - both gui & cmd, moreover that in addition cli is removed at ver 0.5

You would need to ask the developers that question to get a detailed answer, but resources are limited and that often influences these decisions.