[wicked-devel] Wicked totally fails for eth card if the link is physically down at startup
Hi all, I'm having a problem with (apparently) wicked daemon as per stock opensuse 13.2. I'm observing that my manually specified static ip configuration for my eth card is not applied in case the link is physically down (e.g. the cable in unplugged) at boot time (and is not applied later too, even if the link restores somehow, but it wouldn't matter much anyway, see below). Also, I've just found the following rather strange statement in the wicked's README, quote: - The nanny daemon (if enabled) helps to automatically bring up configured interfaces as soon as the device is available (interface hotplugging) and set up IP configuration when a link (carrier) is detected. https://github.com/openSUSE/wicked/blob/master/README Please notice "when a link (carrier) is detected" in this fragment. It means the implicite "tiny" assumption that IP configuration is unneeded until the link is physically up. I believe this assumption is totally wrong and terrific. Well maybe its ok for a cellphone kind of environment, but on a server there might be e.g. a network service which wants to bind to a specific ip address at startup, and it will then certainly fail to start if no such ip address exists, etc etc. Generally such kind of behaviour easily screws a server one way or another (if I read it correctly). I've also filled a report for opensuse 13.2 here: http://bugzilla.suse.com/show_bug.cgi?id=970774 Thank you. Regards, Nikolai -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
Hi all, Replying to myself, in case someone else meets the trouble and wonders. In short: use wicked package from updates to opensuse 13.2 and manually add: LINK_REQUIRED=no I can confirm yes it helps. However, this knowledge of how to "fix" fixed ip came with unnecessary frustration and waste of time. IMHO it would make sense to use "LINK_REQUIRED=no" per default in case of manually specified static ip, even for an interface as simple as a plain ethernet card, for reasons perfectly highlighted already in https://bugzilla.opensuse.org/show_bug.cgi?id=911562. Regards, Nikolai Zhubr 17.03.2016 12:21, Nikolai Zhubr:
Hi all,
I'm having a problem with (apparently) wicked daemon as per stock opensuse 13.2.
I'm observing that my manually specified static ip configuration for my eth card is not applied in case the link is physically down (e.g. the cable in unplugged) at boot time (and is not applied later too, even if the link restores somehow, but it wouldn't matter much anyway, see below).
Also, I've just found the following rather strange statement in the wicked's README, quote:
- The nanny daemon (if enabled) helps to automatically bring up configured interfaces as soon as the device is available (interface hotplugging) and set up IP configuration when a link (carrier) is detected.
https://github.com/openSUSE/wicked/blob/master/README
Please notice "when a link (carrier) is detected" in this fragment. It means the implicite "tiny" assumption that IP configuration is unneeded until the link is physically up. I believe this assumption is totally wrong and terrific. Well maybe its ok for a cellphone kind of environment, but on a server there might be e.g. a network service which wants to bind to a specific ip address at startup, and it will then certainly fail to start if no such ip address exists, etc etc. Generally such kind of behaviour easily screws a server one way or another (if I read it correctly).
I've also filled a report for opensuse 13.2 here:
http://bugzilla.suse.com/show_bug.cgi?id=970774
Thank you.
Regards, Nikolai
-- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
participants (1)
-
Nikolai Zhubr