12.3 cannot stop firewall to start at boot

suse 12.3 kde fresh install with separated /home, if I go to >yast2>firewall and I check the button to disable firewall automatic starting it seams to work, but when I reboot the firewall is still there and if I go to >yast2>firewall the check is on the enable firewall automatic starting.
how can I disable the firewall???
thnx :slight_smile: ciao :slight_smile: pier

Try these in a terminal


systemctl status SuSEfirewall2.service
systemctl enable SuSEfirewall2.service
systemctl start SuSEfirewall2.service
systemctl stop SuSEfirewall2.service
systemctl disable SuSEfirewall2.service

maaaany thanks, they worked perfectly:), could it be a bug in yast??

thnx :slight_smile: ciao :slight_smile: pier

Nope, this is because we’re used to the old runlevels, while systemd is taking over. You may be interested in systemd-ui, which you can start with

kdesu systemadm

Try enabling, starting, stopping from there. It also gives a nice overview on what services rely on.

This is interesting, I can not get my firewall to start either.
I follower the instructions above and got no error messages so I assumed the firewall was started. I now check yast and it says the firewall is running but then I check systemd-ui and get this.
http://paste.opensuse.org/view/download/37947521

It looks like the firewall is not running. I wonder what it is really doing? Which one of these service managers should I trust?

On 2013-03-17 22:26, Knurpht wrote:
>
> pier_andreit;2536914 Wrote:
>> maaaany thanks, they worked perfectly:), could it be a bug in yast??
>>
>> thnx :slight_smile: ciao :slight_smile: pier
>
> Nope, this is because we’re used to the old runlevels, while systemd is
> taking over. You may be interested in systemd-ui, which you can start
> with

Well, THAT is a bug in YaST, which is not able to handle start/stop of
services any longer, because of the systemd migration.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Yes, I’m surprised that YaST wasn’t updated to handle this for openSUSE 12.3, although I guess it’s still trying to provide compatibility with sysvinit while it is still supported.

On 2013-03-18 01:06, deano ferrari wrote:
> Yes, I’m surprised that YaST wasn’t updated to handle this for openSUSE
> 12.3, although I guess it’s still trying to provide compatibility with
> sysvinit while it is still supported.

YaST doesn’t seem to be a priority anymore. Perhaps when the new SLES
get released. :-}


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Is there a bug filed for this?

On 2013-03-29 14:36, tosiara wrote:
>
> Is there a bug filed for this?

That YaST lacks maintenance and is bitrotting? That’s a known issue. I
read a developer complaining of this recently…

This particular issue of stopping the firewall? Dunno, I haven’t looked,
but it is not the first time that I see posts on this.

It would certainly be a good idea to report it again, let them close it
as duplicated if they like.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Filed a new bug: https://bugzilla.novell.com/show_bug.cgi?id=812606