![](https://seccdn.libravatar.org/avatar/e6e477fc4ab7634f3ed96f356b548e1c.jpg?s=120&d=mm&r=g)
John, On Sun, Feb 01, 2015 at 10:29:07PM +0000, John S wrote:
<grantksupport <at> operamail.com> writes:
Upgrade from 13.1 -> 13.2 removed support for traditional/stable
if-up/if-down network control,
replacing it with wicked.
[...]
Any progress on replacing this horrible network management approach?
If this is about a defect in openSUSE 13.2 please use bugzilla to track the issue. It's also of some value to report the bug IDs back to the general openSUSE lists aka opensuse@opensuse.org No, we don't need 13.2 bug report IDs here. Also ensure to have the recent wicked update installed (0.6.14-4.1).
I have only ever used the traditional/stable if-up/if-down network control on my laptop. In previous versions, individuals could chose between a the largely broken NetworkManager and a reliable set of scripts. A horrible decision was made here to force users into a choice between a largely broken NetworkManager and the broken and untested wicked.
I highly doubt that anyone has done any serious code review on the project from a security perspective. This alone is reason for me to avoid it for years.
I'm using wicked with my openSUSE Factory install and it works reliable. But here the actual use case might make the difference.
Is there a plan to use update-alternatives to offer a choice between the reliable, working set of if-up/if-down network control and the "sexy", non-working wicked?
Please be more productive. Such general criticism - I could even name it FUD ;) - doesn't bring the project forward. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany