What's the point of wicked?

English Open Chat
#1

Hello.
I have been trying to answer this question: Why the openSUSE project created wicked? I understand the old method with ifup has several problems but couldn’t we just use iproute2. Which advantages/features does wicked offer compared with using just iproute2?
Thanks.

#2

On Wed, 24 Dec 2014 12:06:01 +0000, GNW wrote:

> Hello.
> I have been trying to answer this question: Why the openSUSE project
> created wicked? I understand the old method with ifup has several
> problems but couldn’t we just use iproute2. Which advantages/features
> does wicked offer compared with using just iproute2?
> Thanks.

This is probably a good starting point:

https://en.opensuse.org/Portal:Wicked

(Found using Google with “opensuse wicked network”, FYI)

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#3

On Wed, 24 Dec 2014 12:06:01 GMT
GNW <GNW@no-mx.forums.opensuse.org> wrote:

>
> Hello.
> I have been trying to answer this question: Why the openSUSE project
> created wicked? I understand the old method with ifup has several
> problems but couldn’t we just use iproute2. Which advantages/features
> does wicked offer compared with using just iproute2?
> Thanks.

I’ve also wondered why they created a networking manager named “wicked”
when there’s already one for Linux named “wicd”, pronounced “wicked”.
https://launchpad.net/wicd

Judging by my experience of the expletive-deleted thing when connecting
wirelessly - or more correctly, not connecting wirelessly - I can only
conceive that they introduced it in order to force us to use Network
Manager. However, I think this is the official line:
http://www.susecon.com/doc/2014/sessions/TUT7562.pdf

–
Graham Davis [Retired Fortran programmer - now a mere computer user]
openSUSE 13.2 (64-bit); KDE 4.14.3; AMD Phenom II X2 550 Processor;
Kernel: 3.17.4; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)

#4

I know that they want support for VLAN, bridging, bonding, tun, tap, etc, but iproute2 supports them all. Also they want a system that is integrated with systemd but iproute2 can also be integrated with systemd (https://bbs.archlinux.org/viewtopic.php?id=187138)

So why create a new tool. Also, does wicked depend on iproute2?

Thanks, bye.

#5

They wanted a service that maintains and monitors the connection, iproute2 is only used to configure the interface(s).

#6

I found the complete answer here:
https://github.com/openSUSE/wicked/blob/master/doc/WhyWicked.txt
It looks very ambitious.

That is explained at the end of https://github.com/openSUSE/wicked/blob/master/README
After skimming through the first link above I think wicked’s aim is much more wide;
it seeks to be a tool for high-end applications, whereas wicd seems to be just for
home needs.

Regards, Bye.