wickedd-dhcp4 and static ip?

English Network/Internet
1

Hi,

I’m new to opensuse and trying to learn wicked ( instead of NetworkManager)

I’ve set a server with static ip but it seems a bit annoying to have the following processes:

/usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground
/usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground
/usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground

Is there a way to disable them?

I’ve tried the “systemctl disable…” but that does no seem to work :frowning:

Any links to a good manual about wicked?

Any other hints?

Thanks in advance,

Michael

2

Maybe you should even drop wicked (Ia lso do not understand what those daeoms are doing all the time, once the network is up, that is it folks).

Using systemd-network.

Create /etc/systemd/network/20-wired.network (change wired.network to your liking) with contents

[Match]
Name=eth0

[Network]
Address=1.2.3.4/24
Gateway=1.2.3.138

Again change to your needs.

When /etc/resolv.conf is a symlink, remove it. Create a new one or edit the existing one to have your DNS server(s) and when needed search statement(s).

Use YaST > System > Services Manager to switch off all with wicked (I later even masked them).
Use the same to switch systemd-networkd on and start on boot.

Reboot and test.

3

I see similar processes, but I have pretty much decided to just ignore them.

4

I did also for a long time. But I always wondered what they were doing.

5

Thanks for all answers!

I managed to disable them the hard way :wink:

Example:

systemctl stop wickedd-dhcp4
systemctl disable wickedd-dhcp4

systemctl** mask **wickedd-dhcp4

I did that on all 3 and the network is still working fine and I’ve saved a few kb of memory :slight_smile:

I wish there was an option in wicked to that instead.

Coming from fedora/centos/arch I still don’t see the big benefit of using wicked compared network manager where you only have one deamon/process
instead of a bunch of them. Maybe someone will improve that in future versions or enlighten me.

B.t.w Using the systemd-networkd is a good option but then it’s not integrated in yast? (this is a newly installed machine)
All settings are done outside i.e. not “the opensuse way of system adminstration”.

6

Sorry, my memory is a bit slow. The trigger that made me convert to systemd-network is that it took about 8 - 10 secs to strat Wicked at boot, of which about half of the time no other starting was done. Thus I was staring ~4secs to the screen where nothing happened. As said for such a simple task as doing two statements: upping the NIC and setting the default router.

Then I saw this thread https://forums.opensuse.org/showthread.php/535043-et0-not-(auto)-enabled-at-boot-time-no-static-ip-addresses-are-assigned?p=2896953#post289695 where @karlmistelberger shows the way. Tried it and it worked fantastic. Use it on both systems here since then.

7

That is true. When you start YaST > System > Network Settings, you will see in the General Options tab: Network Services switched off.

But you are doing the same. Switching off those daemons is not how YaST > System > Network Settings did it for you and I have no idea how that YaST module will react on this. Maybe it will not notice, but it will probably assume they are running.

The choice between using Network Manager or Wicked (formerly not Wicked but Ifup) is normally not done by comparing the number of background processes involved. It is about using a fixed network connection all the time (computer room, desktop, laptop that is not carried around) and configured by the system manager vs. a walk around device (laptop, netbook, other) to the airport, working place, etc., where the end-user, logged in in a GUI, wants to take the descision to what network to connect at that moment in time.