Bug 191461 - Firewall - Stop and Start buttons questionable
Summary: Firewall - Stop and Start buttons questionable
Status: RESOLVED DUPLICATE of bug 145841
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i586 SuSE Linux 10.1
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-11 00:08 UTC by Scott Couston
Modified: 2006-07-11 10:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Couston 2006-07-11 00:08:24 UTC
1.Change firewall to Start Manually>Next>Accept

2.RE:Boot

3.Start firewall, changes status to "Firewall is running" > Next >Accept.

4.Go to ANY application in Network Services and you will find "Open Port in Firewall" is inaccible - greyed out.

Firewall appears not to be running despite status.

5.Go back into firewall or add any service or "Save Settings and re-start "Service Start" to "When Booting" Next>Finish

Firewall appears to be running NOW as if you enter any "Network Service", 'Open Port in Firewall" IS now accessible - presume working.

6. Stop Firewall - change nothing else. Status changes to "Not Running" >Next>Accept


7.Go to ANY application in Network Services and you will find "Open Port in Firewall" is accessible.

This would indicate firewall IS running.

It appears that the Start and Stop firewall buttons alone have no effect on the status of the firewall. There MUST be a change of some type to either service start, an addition or deletion of a service.

Suggest that functionality of "Save Settings and Restart" should replace "Start Firewall and replacement for stop firewall be changed to Save Settings and Stop Firewall

100% reproduciable.
Comment 1 Lukas Ocilka 2006-07-11 10:52:50 UTC
This is an issue with CWMFirewallInterfaces library that doesn't report the current state well. Something like: Firewall is running but not enabled, Firewall is enabled but not running, etc.

This library is planned to be rewritten, at least partly.

*** This bug has been marked as a duplicate of 145841 ***