[opensuse-factory] Need to add boot message Warning about duplicate fixed IP address on subnet
List,
Moving machines between subnets yesterday, I was faced with the problem of a box completing the boot process and then hanging just before login was reached. No message, no log entry and no warnings. The only thing shown on the console was miscellaneous smb and normal nmb browse master messages but nothing concerning a duplicate IP.
The conflict arose when before moving the box from subnet to subnet the last thing I did before shutting the machine down was to use yast so set the IP of the box to the new subnet. I was certain (I thought) that the assigned IP wasn't used. Several hours later when the box was started on the new subnet, thinking about a possible IP conflict was the last thing on my mind. Nevertheless, the box would not boot.
To investigate I booted to repair mode and started shutting down the activation of processes in reverse order of activation to eliminate messages on the console and hopefully find out why the box wouldn't reach login. (shutting down xinetd, smb, ksysguardd, etc..) Nothing provided a glimpse of the error. (There was one obscure smb socket message that hinted at an IP conflict, but I doubt anyone other than samba developers would have clicked to the relationship)
Finally, just shooting in the dark, I started yast and started picking through the settings. Somewhat on a whim, I decided to step through the network configuration again. Global, Overview and Routing were fine so I decided to edit the adapter configuration. All settings were fine. Just by chance, instead of clicking "abort" to leave the settings unchanged, I decided to click "finish" and -- Wham! -- yast issued the "Address already taken on network" error message that identified the conflict. Just exactly what yast should have done. Problem solved.
In the openSuSE boot process, when the network card is activated, this same check should be performed and a message displayed and logged concerning the conflict. In its current state the boot process proceeds right through network activation without giving any indication of a conflicting IP. (I know, I watched the boot messages for the network probably 10 times during this process).
The boot process needs to be smart enough to conduct this check and warn when a conflict occurs. It seems like this would just required taking the few lines of code from the yast2 card configuration check and putting it in the network activation script. Yes, I know this is just a check to protect people from their own stupidity, but that is what good software is supposed to do.
I added https://bugzilla.novell.com/show_bug.cgi?id=526495
On Wed, Jul 29, 2009 at 02:15:19PM -0500, David C. Rankin wrote: [ 8< ]
/etc/sysconfig/network/config:CHECK_DUPLICATE_IP="yes". See my comment in bugzilla too.
The current default is no which is wrong. At least for openSUSE and the desktop we must consider to change this.
Lars
Am Mittwoch 29 Juli 2009 schrieb Lars Müller:
On Wed, Jul 29, 2009 at 02:15:19PM -0500, David C. Rankin wrote: [ 8< ]
/etc/sysconfig/network/config:CHECK_DUPLICATE_IP="yes". See my comment in bugzilla too.
The current default is no which is wrong. At least for openSUSE and the desktop we must consider to change this.
Considered and rejected: # Also be aware that this takes one second per interface; consider that when # setting up a lot of interfaces.
The world talks about booting faster, not longer
Greetings, Stephan
On Thu, Jul 30, 2009 at 09:32:39AM +0200, Stephan Kulow wrote:
Am Mittwoch 29 Juli 2009 schrieb Lars Müller:
On Wed, Jul 29, 2009 at 02:15:19PM -0500, David C. Rankin wrote: [ 8< ]
/etc/sysconfig/network/config:CHECK_DUPLICATE_IP="yes". See my comment in bugzilla too.
The current default is no which is wrong. At least for openSUSE and the desktop we must consider to change this.
Considered and rejected: # Also be aware that this takes one second per interface; consider that when # setting up a lot of interfaces.
The world talks about booting faster, not longer
a) A system with a lot of interfaces is very likely not a desktop system where booting fast is the most important goal of the world(tm).
A usual desktop system will have a cable and wireless interface.
b) Apple does it with Mac OS X and if they do it it must be the right approach.
c) Checking for duplicate IP usage costs approximately 1 second.
And the check is very likely only required if the interface is not in autoconfiguration/ DHCP mode.
d) Aren't we executing the init scripts in parallel?
The world talks about usable systems. Better: The world expects a working network configuration and doesn't talk about it. Our users don't even like to think about this case. It just has to work.
Lars
On Thu, Jul 30, 2009 at 03:21:28PM +0100, Peter Nikolic wrote:
On Thursday 30 Jul 2009 12:30:10 Lars Müller wrote:
b) Apple does it with Mac OS X and if they do it it must be the right approach.
Please explain why just because "Jobs" bunch does something it has got to be right that seems like noise .
Sorry for missing to add :) after the sentence.
But in general the userfriendlyness of products made my Apple (most of the time) provide good hints in which direction Linux might evolve.
But even completely independent of the Apple approach a smart way to handle duplicate IP address assignement will end users help a lot.
Think of a dbus message displayed by your window manager and informing you about this type of network misconfiguration issue.
Lars
On Thu, Jul 30, 2009 at 10:31 AM, Lars Müllerlmuelle@suse.de wrote:
On Thu, Jul 30, 2009 at 03:21:28PM +0100, Peter Nikolic wrote:
On Thursday 30 Jul 2009 12:30:10 Lars Müller wrote:
b) Apple does it with Mac OS X and if they do it it must be the right approach.
Please explain why just because "Jobs" bunch does something it has got to be right that seems like noise .
Sorry for missing to add :) after the sentence.
But in general the userfriendlyness of products made my Apple (most of the time) provide good hints in which direction Linux might evolve.
But even completely independent of the Apple approach a smart way to handle duplicate IP address assignement will end users help a lot.
Think of a dbus message displayed by your window manager and informing you about this type of network misconfiguration issue.
Lars
If the drive for short boot times is causing debug boot info to disappear, opensuse should offer a "debug" boot. ie. I don't mean failsafe that reduces functionality, I'm talking about something that provides greater feedback for troubleshooting purposes.
Greg
On Thursday 30 July 2009 09:43:20 am Greg Freemyer wrote:
I'm talking about something that provides greater feedback for troubleshooting purposes.
It is good idea, as in that case it doesn't matter how long it will boot.
On Thursday 30 July 2009 02:32:39 am Stephan Kulow wrote:
Am Mittwoch 29 Juli 2009 schrieb Lars Müller:
On Wed, Jul 29, 2009 at 02:15:19PM -0500, David C. Rankin wrote: [ 8< ]
/etc/sysconfig/network/config:CHECK_DUPLICATE_IP="yes". See my comment in bugzilla too.
The current default is no which is wrong. At least for openSUSE and the desktop we must consider to change this.
Considered and rejected: # Also be aware that this takes one second per interface; consider that when # setting up a lot of interfaces.
The world talks about booting faster, not longer
Greetings, Stephan
Stephan will be the downfall of opensuse. This "don't do it right" philosophy has got to stop....
On 8/6/2009 at 17:59, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
Stephan will be the downfall of uyl. This "don't do it right" philosophy has got to stop....
So we vote for DAVID in the position of the eternal decision taker! Oh please enlighten us with all your wisdom!
I'm honestly surprised that everybody is so smart and yet, there are so many bugs to be fixed. If you get to duplicate IP addresses, then you have probably more to worry in your network than one single computer showing you a dialog that you completely messed up your network. If you end up with DUP IPs in your network, latest THEN should you ask yourself: am I taking care in a good way of my network?
And NO: Joe Average will probably never get this message. He's the one that has his entire network configured on DHCP (even though he does not know about it) and is just blazing amazed that his system just works. A Message box telling him that an address is used twice on his network will help him as much as a pack full of sand while driving through the desert.
Dominique
Am Donnerstag 06 August 2009 schrieb Dominique Leuenberger:
On 8/6/2009 at 17:59, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
Stephan will be the downfall of uyl. This "don't do it right" philosophy has got to stop....
So we vote for DAVID in the position of the eternal decision taker! Oh please enlighten us with all your wisdom!
I'm honestly surprised that everybody is so smart and yet, there are so many bugs to be fixed. If you get to duplicate IP addresses, then you have probably more to worry in your network than one single computer showing you a dialog that you completely messed up your network. If you end up with DUP IPs in your network, latest THEN should you ask yourself: am I taking care in a good way of my network?
And NO: Joe Average will probably never get this message. He's the one that has his entire network configured on DHCP (even though he does not know about it) and is just blazing amazed that his system just works. A Message box telling him that an address is used twice on his network will help him as much as a pack full of sand while driving through the desert.
_And_ his friends will tell him just how great, usable and fast ubuntu is and that he should change if he doesn't understand openSUSE's weird messages.
Greetings, Stephan
-
David C. Rankin -
Dominique Leuenberger -
Greg Freemyer -
Lars Müller -
Peter Nikolic -
Rajko M. -
Stephan Kulow