Bug 804894 - Disabling firewall in yast does not survive reboot
Summary: Disabling firewall in yast does not survive reboot
Status: RESOLVED DUPLICATE of bug 807507
: 811188 (view as bug list)
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: Security (show other bugs)
Version: RC 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 07:44 UTC by Roger Oberholtzer
Modified: 2013-07-04 07:16 UTC (History)
8 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Oberholtzer 2013-02-21 07:44:19 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0

If I both disable and stop the firewall in Yast, it still starts again after the system reboots.

Bug 779455 addressed something related to this for 12.2, but there is something going on in 12.3 RC1

Reproducible: Always

Steps to Reproduce:
1. Stop and Disable the firewall in Yast
2. Reboot
3.
Actual Results:  
The firewall is started

Expected Results:  
The firewall, having been disabled, should not be started.

Stopping the firewall in Yast works. It just does not survive a reboot.

Before the reboot, but after I have disabled the firewall, looking in yast again shows the correct/expected settings. They just don't happen after the reboot.
Comment 1 Marcus Meissner 2013-02-21 08:01:35 UTC 
more a job for yast2-maintainers i think
Comment 2 Jiří Suchomel 2013-02-25 09:17:06 UTC 
YaST or systemd?
Comment 3 Frederic Crozat 2013-02-25 09:35:42 UTC 
yast or the way yast is enabling / disabling systemd services.

I think there was a bug somewhere in checking the location of the services (/lib/systemd/system => /usr/lib/systemd/system) but I might be wrong.
Comment 4 Marco Munderloh 2013-03-15 13:42:29 UTC 
Enabling the firewall in yast does work, disabling doesn't.

To disable the firewall I had to use:

systemctl disable SuSEfirewall2_init.service
Comment 5 Maitreya Maziarz 2013-03-15 16:08:06 UTC 
When using YaST (curses or normal), disabling firewall, finishing, and then going back into firewall setup, enable at startup is still displayed.
Comment 6 Ludwig Nussel 2013-03-18 08:20:23 UTC 
might be related to bug 807507
Comment 7 Marco Munderloh 2013-03-18 09:06:29 UTC 
I also noticed that SuSEfirewall2 ist not listed in chkconfig anymore, which is also not wanted, I assume.
Comment 8 Marco Munderloh 2013-03-18 09:29:36 UTC 
I installed the patched yast2 provided in bug 807507 and I am able to enable and disable the firewall now.

However, it would be nice to have SuSEfirewall2 back in chkconfig, as I don't like the systemctl interface.
Comment 9 Ludwig Nussel 2013-03-18 12:22:37 UTC 
ok so closing as duplicate of bug 807507

you can still run chkconfig SuSEfirewall2 on etc. SuSEfirewall2 even has a shortcut, SuSEfirewall2 off will unload all rules and disable the script. SuSEfirewall2 on will enable the scripts and apply rules.

*** This bug has been marked as a duplicate of bug 807507 ***
Comment 10 Johannes Meixner 2013-07-04 07:16:38 UTC 
*** Bug 811188 has been marked as a duplicate of this bug. ***