From: robin_listas@es.invalid   
      
   On 08/08/2021 22.13, Sidney_Kotic wrote:   
   > On 8/8/21 10:05 AM, Carlos E. R. wrote:   
   >   
   >> I see a possible problem: SuSEfirewall2 also tries to start, and   
   >> conflicts with firewalld.   
   >>   
   >> So check both:   
   >>   
   >> systemctl status firewalld   
   >> systemctl status SuSEfirewall2   
   >   
   > Went back into yast and set the SuSEfirewall2 stuff to start manually.    
   > Left firewalld to start at boot.   
   >   
   > Rebooted and things look fine.   
      
   My recommendation, unless you have a previous configuration in   
   SuSEfirewall2, just uninstall it.   
      
   The two programs conflict. The conflict is not automatic, because there   
   are people like me with configuration of SuSEfirewall2 going back to   
   decades, who need both tools in order to do a migration. Thus YaST, for   
   the moment, allows you to set both to start, or to set one to start   
   manually. But this generates a conflict if they actually both try to run.   
      
   So, set SuSEfirewall2 to run "never", or just do:   
      
   systemctl --now disable SuSEfirewall2   
      
      
   And even better, uninstall it. And do the same on all your machines   
   running Leap 15.* or Tumbleweed.   
      
   --   
   Cheers,   
          Carlos E.R.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)