Bugzilla – Bug 106713
yast2-ntp-client does not correctly detect manually started firewall
Last modified: 2006-11-20 18:51:42 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.
Created attachment 47207 [details] yast logs
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.