Hello all,
16.06.2016 13:52, Marius Tomaschewski:
Am 18.05.2016 um 18:16 schrieb Jason Schultz:
I hope I am not starting a new thread with this, I am attempting to reply to
Nikolai Zhubr's last message from his thread:
https://lists.opensuse.org/wicked-devel/2016-03/msg00004.html
I had started a similar thread a couple weeks before that here, which also did
not get a response:
https://lists.opensuse.org/wicked-devel/2016-03/msg00000.html
The reason for replying again is to agree with the conclusion that
"LINK_REQUIRED=no" should be the default
in order to prevent this type of issue when there's no physical link.
Definitely not. Many, many things (in the kernel and elsewhere) starts
after the carrier detection / cannot start without carrier, e.g. ipv6,
bond + bridge protocols, any kind of link authentication (wpa), any
autoconfiguration incl. dhcp, duplicate address detection [required
(except in obsolete RFCs) and enabled also for ipv4] ...
Ok, then you should disallow BOOTPROTO='static' and also all those tons
of software that are not designed to bind dynamically to randomly
appearing interfaces, so as to be truly consistent.
No, there is nothing wrong with this (fully-dynamic) behaviour in
itself. It may appear handy and fit in many cases, e.g. for mobiles.
However problem is:
- compatibility,
- expectations,
- consistency.
(-and still not all of us run Suse on mobiles but some do on servers and
desktops!)
If you force a beautifull new behaviour that is horribly incompatible
with (a lot of regular) existing software, incompatible with people's
expectations, and introduces inconsistencies like silently treating
BOOTPROTO='static' as kind of bogus or obsolete, then you should really
really make it clear that this new shiny solution is still NOT something
that can be relied upon as a proper REPLACEMENT of old buggy scriptware.
But better yet... make it reasonably compatilble, please.
Don't take me wrong, I understand and appreciate the amount of hard
thinking and effort wickedd developers have invested into it already,
and I'd really like it success and good acceptance. I seriously hope
wickedd helps to avoid some ancient and annoying network issues (that
I'm quite aware of and suffer from time to time on non-wickedd
installations).
But still again: unexpectidly broken BOOTPROTO='static' does not add
much joy, especially when you suddenly find your server inaccessible. I
really see no reason for not defaulting to LINK_REQUIRED=no when
BOOTPROTO=static. In such case dhcp does not need to even be mentioned.
Regarding duplicate address detection I'm not exactly sure how it should
work in all detail, but I'd suppose it would need to somehow deal with
link going physically up and down repratedly anyway? So what is the
benefit of bothering so much at some particular moment then?
Thank you,
Regards,
Nikolai
See also "man ifcfg", where it is described already until some extent
and also https://github.com/openSUSE/wicked/blob/master/doc/FAQ.txt.
Make sure, nanny use is enabled (<use-nanny>true</use-nanny> in the
/etc/wicked/common.xml) -- it will set it up once a carrier is there.
As I explained in my previous post, I thought there would already be a solution
to this issue that would
require less manual configuration, such as setting LINK_REQUIRED=no in
/etc/sysconfig/network/config
but this did not work for me. I spent some time looking at the source
code to see if I could find an
option in the XML files that would work to change the default
behavior, but I was unsuccessful.
Currently, there is none. Same as there is no possibility to set
e.g. BOOTPROTO=dhcp by default.
But... https://github.com/openSUSE/wicked/pull/657 adds it now
to make some people that like to break rules happy :-)
Gruesse / Regards,
Marius Tomaschewski<m...@suse.de>,<m...@suse.com>
--
To unsubscribe, e-mail: wicked-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: wicked-devel+ow...@opensuse.org
