http://bugzilla.novell.com/show_bug.cgi?id=488985
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=488985#c25
Marius Tomaschewski
I am happy to leave this bug as invalid although I will leave an end comment of my own. I do NOT know what Network Manager has to do with this bug which is solely about IFUP.
They're mutually exclusive: NETWORKMANAGER=yes -->> IFUP == off NETWORKMANAGER=no -->> IFUP == on
This bugs log data probably contains many many combinations of NM and IFUP for testing purposes.
Then reset them with "logrotate -f /etc/logrotate.conf" and provide clean logs.
This bug is 100% reproducible and perhaps language translation is at fault. The term "Static IP" used in this bug refers to the user configuration of IP, Subnet, Gateway and 2 x DNS Server IP's. To reproduce this bug please follow these simple steps that I have written about adnauseous. 1. Use a test LAN environment that DOES NOT provide ANY DHCP Services. 2. Configure a static IP, Subnet, Gateway and 2 x DNS Server IP's 3. Attempt to communicate with the DNS Servers via a browser - This will fail!
No, it generally does not fail. Except in your case because of invalid gateway( 192.168.1.1) configuration, that is not inside/member of the directly attached network (192.168.100.0/24, that is 192.168.100.<1..254> as specified in the IPADDR field). As effect, the default route, that is required to reach the DNS server IPs can not be set.
The reason is that when BOTH DNS Server IP's are specified AND the LAN environment does NOT provide any DHCP Services at all THEN both DNS Server IP's so specified are taken from the Yast Screen and BOTH IP addresses are set in config as 1 single address.
Where? They're written into /etc/resolv.conf in two lines: nameserver 123.200.191.17 nameserver 123.200.191.18
For Example. IF I configure Yast with the DNS Servers of 123.200.191.17 AND 123.200.191.18 the fields that are taken from Yast into the actual config are either run together nor make no sense as the PC, under test conditions, cannot reach ANY DNS Server IP's.
Where are they "run together"?
If you CANNOT provide a LAN environment WHERE no DHCP Services are present this test will fail.
Why is this bug a huge problem? ANY secure LAN environment does not provide any DHCP Services and valid IP's are NOT handed out to any PC that connects to a secure LAN. This lack of DHCP Services being present escapes just about all testing for some unknown reason, perhaps because the lack of experience of developers that have never been exposed to highly secure LAN Environments.
This bug is neither a huge problem nor closed because of missed test LAN without DHCP server. It is simply a problem we can't solve because the configuration is not correct and the reporter does not want to accept this. -- 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.