http://bugzilla.novell.com/show_bug.cgi?id=516699 User locilka@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c3 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@novell.com |tambet@novell.com --- Comment #3 from Lukas Ocilka 2009-07-03 02:50:52 MDT --- Maybe I don't understand you correctly but what I think you wanted to say is: If a network is controlled by NetwotkManager, it doesn't create any interface that could be used by YaST/SuSE firewall and thus it seems you can't, for instance, allow any service on such interface. However, there are two options left: * SuSEfirewall2 considers all unassigned interface to be assigned to EXT zone by default. * You can write 'any' custom string into firewall External Zone that makes SuSEfirewall2 consider all unassigned interfaces to be in EXT zone without explicitly reporting that while starting SuSEfirewall2. I'm reassigning this bug to maintainer of NetworkManager as I can't do anything with NetworkManager not providing these interfaces and/or I can't do anything with Network Module not giving me any information about these interfaces. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c5 --- Comment #5 from Scott Couston 2009-07-03 15:33:53 MDT --- Created an attachment (id=302927) --> (http://bugzilla.novell.com/attachment.cgi?id=302927) 1 of 2 screen shot -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c7 --- Comment #7 from Scott Couston 2009-07-03 15:38:57 MDT --- *** Bug 511395 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=511395 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User locilka@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c9 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@novell.com |mzugec@novell.com --- Comment #9 from Lukas Ocilka 2009-07-07 02:28:41 MDT --- Miso, Tambet suggests using some API to get interfaces from NM. Network could maybe use that API. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c11 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | AssignedTo|mzugec@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #11 from Scott Couston 2009-07-07 04:33:04 MDT --- UNACCEPTABLE! CLOSURE OF WONTFIX. Yast made the decision to remove the control of NM from Yast?Network Devices as in 11.0 is was still in Yast>Network Devices. As they have made this huge decision, they need to accept the consequences, of hindsight, and insufficient testing before they put it up for this change. I would be interested in who and for what reason or who request that NM was removed from Yast in 11.1. As a the PC IP is not controlled by Yast, the Suse Firewall makes the assumption at boot, that no zone exists and auto assigns EXT in Yast Firewall. Now if the user wants to use ANY YAST application that requires them to open the Firewall, they cannot as Yast is not managing the device - If the user uses NM and wants to use ANY Yast Network service they cannot open the firewall port as Yast is not managing the device, yet the IP has been defaulted to the ext zone during boot. So if a user needs to use a static IP in 11.1 - we already know IFUP cannot do this - they now cannot use any YAST Network Service as they cannot open the firewall in the defaulted ext zone. Would you have the user totally halt the firewall completely or go into the firewall and manually add the service I.E NFS, to that the Yast function can actually work QA - IF YOU ARE GOING TO REASSIGN THIS BUG - please do not assign to author of comment #10 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User visnov@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c13 Stanislav Visnovsky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com AssignedTo|bnc-team-screening@forge.pr |alpha096@virginbroadband.co |ovo.novell.com |m.au --- Comment #13 from Stanislav Visnovsky 2009-07-07 04:44:03 MDT --- Yes. We removed the functionality because it was not working good. And with introduction of NM 0.7, even the pieces that worked unreliably stopped to work completely. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c15 --- Comment #15 from Scott Couston 2009-07-07 20:53:03 MDT --- The reason for the status Block I have used is for reporting stats only. I know block is reserved to halt release beta into RC or to halt a RC. I have left status as block as I believe that 11.1 should never have got to RC due to the enormity of issues surrounding it. 1. IFUP cannot assign a static IP 2. Network Manager is still KDE3 but can assign a static IP 3. NO Yast service can effect any control over the NIC only NM has been selected. 4. The user has to either turn off the firewall completely and not re-start it if they use NM and want to use ANY Network Service OR 5. Manually add each service type to the ext firewall service to use NM and any Network Service. 6.The existence of 2 NIC's in a PC cannot be controlled by NM as NM is the only was to assign a static IP. 7.Installation fails if NM is activated during non-Automated Installation. 8.The field presentation and the ability to successfully assign a static IP via NM is diabolical. The fields justification and demanding of a 3 character, including a space character, is expected in ever field for NM to function correctly. So to re-cap we released 11.1 without being able to control its connection to the Internet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=516699#c17 --- Comment #17 from Scott Couston 2009-07-08 01:47:31 MDT --- RE comment #16 - Sorry Incorrect see Bug 488985, for details backed up by Yast Logs and discussion AND Bug 487466 for details backed up by Yast Logs and discussion -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516699 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|alpha096@virginbroadband.co |bnc-team-screening@forge.pr |m.au |ovo.novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.