Switch from wicked to NetworkManager
Hi, as you may have already noticed, openSUSE MicroOS and openSUSE Kubic are using now NetworkManager as default instead of wicked. This was very often requested by various groups, as e.g. wicked has no 5G modem support or as there are k8s network plugins, which only support NetworkManager. And MicroOS Desktop was using NetworkManager already anyways. As of today we have no plans to automatically switch a system from wicked to NetworkManager. But this does not mean wicked will stay maintained forever, so you should think about migrating to NetworkManager. While the files in /etc/sysconfig/network/ifcfg-* should be compatible, I'm not even sure if there are not corner cases where they are incompatible. If you use a native wicked xml configuration, migration will become more work. But if you did create the network configuration during installation or you are using only the ifcfg-* files, a switch to NetworkManager should be very simple: # transactional-update shell -> zypper in --no-recommends NetworkManager -> rpm -e wicked wicked-service -> systemctl enable --now NetworkManager -> exit # reboot I migrated all of my machines with this and didn't run into any problems. For better integration with NetworkManager, is anybody using netconfig directly? If yes, for which use cases? Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)
On Thu, Apr 14, 2022 at 4:23 AM Thorsten Kukuk
Hi,
as you may have already noticed, openSUSE MicroOS and openSUSE Kubic are using now NetworkManager as default instead of wicked. This was very often requested by various groups, as e.g. wicked has no 5G modem support or as there are k8s network plugins, which only support NetworkManager. And MicroOS Desktop was using NetworkManager already anyways. As of today we have no plans to automatically switch a system from wicked to NetworkManager. But this does not mean wicked will stay maintained forever, so you should think about migrating to NetworkManager. While the files in /etc/sysconfig/network/ifcfg-* should be compatible, I'm not even sure if there are not corner cases where they are incompatible. If you use a native wicked xml configuration, migration will become more work.
But if you did create the network configuration during installation or you are using only the ifcfg-* files, a switch to NetworkManager should be very simple:
# transactional-update shell -> zypper in --no-recommends NetworkManager -> rpm -e wicked wicked-service -> systemctl enable --now NetworkManager -> exit # reboot
I migrated all of my machines with this and didn't run into any problems.
For better integration with NetworkManager, is anybody using netconfig directly? If yes, for which use cases?
Are we even building the ifcfg plugin in NetworkManager right now? I don't recall if we are... -- 真実はいつも一つ!/ Always, there's only one truth!
participants (2)
-
Neal Gompa
-
Thorsten Kukuk