Bug 106713

Summary:	yast2-ntp-client does not correctly detect manually started firewall
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Forgotten User vd_J2WSqeK <forgotten_vd_J2WSqeK>
Component:	YaST2	Assignee:	Lukas Ocilka <locilka>
Status:	VERIFIED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Minor
Priority:	P5 - None	CC:	jsrain
Version:	Beta 2
Target Milestone:	---
Hardware:	i586
OS:	SUSE Other
Whiteboard:
Found By:	System Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	yast logs

Description Forgotten User vd_J2WSqeK 2005-08-23 13:33:35 UTC

Code10 beta2

On the Complex NTP Client Configuration Screen - Firewall Settings
If the Firewall was set to start on boot then "Open Port in Firewall" is
selectable.  But if the firewall was started manually "Firewall Configuration:
Start-Up / Service Start / Manually" then this option (Open Port in Firewall) is
greyed and not selectable.  Using SuSEfirewall2 status indicates the firewall is
in fact functional but the option is not selectable.

It appears that the modules yast-ntp-client checks only the switch to see if the
firewall starts on boot.

Comment 1 Forgotten User vd_J2WSqeK 2005-08-23 13:34:36 UTC

Created attachment 47207 [details]
yast logs

Comment 2 Lukas Ocilka 2005-08-29 08:05:39 UTC

Yes, that's right. YaST Firewall (Simple one-service dialog) detects whether the
firewall starts on boot and doesn't reflect on the fact that the firewall has
been started manually.

There are more possible checkings for the running firewall:
1.) Enabled in the init scripts and running
2.) Enabled in the init scripts but not running now (manually disabled)
3.) Disabled in the init scripts but running (manually enabled)
4.) Disabled in the init scripts and not running

1.) and 2.) were selected for the right firewall checking.