Bug 511395

Summary: NTP Services Cannot Open the Firewall if Network is Controlled ny Network Manager
Product: [openSUSE] openSUSE 11.1 Reporter: Scott Couston <scott>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: lnussel, scott
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screen shot showing all the errors described above
1 of 1 screen shots

Description Scott Couston 2009-06-09 19:45:18 UTC
Created attachment 297053 [details]
screen shot showing all the errors described above

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-1.1.1 Firefox/3.0.10

In the attached screen shot we can see
1. The Network is being controlled by Network Manager
2. The system tray show that Network Manager is connected using a static IP - if it was using DHCP the icon is a green ball.
3. we can see in the NTP settings the the firewall that NTP Services want to open is controlled by DHCP - which was the condition of IFUP way before I configured any NTP Services.

In this situation if you configure NTP services to open the firewall and save the config as soon as you open the NTP services again the firewall is closed

I also doubt if the firewall is managing IFUP or Network Manager at all?

Reproducible: Always

Steps to Reproduce:
1.See above
2.
3.
Actual Results:  
NTP services cannot open the firewall because of network manager

Expected Results:  
If works!

Do not even think about asking for logs - this is easily and 100% reproducible
Comment 1 Scott Couston 2009-06-09 19:46:24 UTC
NTP and Firewall Services are Major concern - upg status
Comment 2 Scott Couston 2009-06-11 00:25:57 UTC
I am now of the opinion that the opensuse firewall does NOT even do anything, once the user elects to use Network Manager 9 KDE3 - which they have to, in 11.1 for obtain a static IP.

I am of the opinion that the firewall can only consider an interface that is defined in Yast>Network Devices. - Upgrading Priority until resolution.

Reference:
https://bugzilla.novell.com/show_bug.cgi?id=498307
Comment 3 Marcus Meissner 2009-07-02 07:26:36 UTC
susefirewall works on devicenames (like eth0) or so, so it is of course managing it during NetworkManager usage.

The device names wont change with networkmanager.

Also the NTP does not need to be opened for NTP to work as far as I know.
Comment 4 Scott Couston 2009-07-02 08:38:00 UTC
Created attachment 302235 [details]
1 of 1 screen shots

This complete exercise on suse.de point of view and my own was totally a waist of time, Time None of us have! Words fail me in comment reply and closed
Comment 5 Scott Couston 2009-07-02 08:43:49 UTC
RE comment #3Have you tried to duplicate this and found no issue.
To say the device name does not change with Network Manager is totally false. Network Manager only identifies and names active connections. It can see the device card info on the NIC.

QA - Please do not assign this bug to author of comment #3 if this can be helped. Neither of us have time to waist on emotive, non tested and non verified closure of any bug
Comment 6 Scott Couston 2009-07-03 21:38:57 UTC
https://bugzilla.novell.com/show_bug.cgi?id=516699

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