http://bugzilla.novell.com/show_bug.cgi?id=516699 Summary: Yast>Firewall Cannot Control or Effect a PC's IP Controlled by Network Manager KDE3 V11.1 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: qa@suse.de Found By: --- 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 If V 11.1 we removed ALL Routing and IP and DHCP Services to the KDE3 Network Manager Applet. As the name given to the interface has nothing to do with the physical location of the NIC, Suse Firewall cannot define nor identify the device. The name of the IP connection given to a wired connection via KDE3 Network Manager is nothing but a name. - It does not associate this name by any device. This further accounts for the other major bug previously reported about KDE3 Network Manager will also not auto connect after PC re-boot despite the auto connection being on. It just grabs an IP from what is available despite the LAN being configured NOT to offer any DHCP Services. All is NOT lost, as the boot process recognise that the NIC device is not defined in any config and assumes 'EXT' in the boot procedure. In the highly unlikely even you cannot reproduce the above - I will be happy to provide what logs you may require. Reproducible: Always Steps to Reproduce: 1.As above 2. 3. Actual Results: As Above Expected Results: It works! -- 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.