documentation.suse.com / SUSE Linux Enterprise Micro Documentation / Administration Guide / Networking / NetworkManager and wicked
Applies to SUSE Linux Enterprise Micro 5.4

6 NetworkManager and wicked

 

This chapter focuses on the difference between NetworkManager and wicked and provides a description how to switch from wicked to NetworkManager.

NetworkManager is a program that manages the primary network connection and other connection interfaces. NetworkManager has been designed to be fully automatic by default. NetworkManager is handled by systemd and is shipped with all necessary service unit files.

wicked is a network management tool that provides network configuration as a service and enables changing the network configuration dynamically.

NetworkManager and wicked provide similar functionality; however, they differ in the following points:

root privileges

If you use NetworkManager for network setup, you can easily switch, stop, or start your network connection at any time. NetworkManager also makes it possible to change and configure wireless card connections without requiring root privileges.

wicked also provides some ways to switch, stop, or start the connection with or without user intervention, like user-managed devices. However, this always requires root privileges to change or configure a network device.

Types of network connections

Both wicked and NetworkManager can handle network connections with a wireless network (with WEP, WPA-PSK, and WPA-Enterprise access) and wired networks using DHCP and static configuration. They also support connection through dial-up and VPN. With NetworkManager, you can also connect a mobile broadband (3G) modem or set up a DSL connection, which is not possible with the traditional configuration.

NetworkManager tries to keep your computer connected at all times using the best connection available. If the network cable is accidentally disconnected, it tries to reconnect. NetworkManager can find the network with the best signal strength from the list of your wireless connections and automatically use it to connect. To get the same functionality with wicked, more configuration effort is required.

k8s integration

Some k8s plugins require NetworkManager to run and are not compatible with wicked.

6.1 Switching from wicked to NetworkManager

 
Important
Important

Even though NetworkManager and wicked are similar in functionalities, we cannot guarantee full feature parity. The conversion of the wicked configuration or automated switching to NetworkManager is not supported.

Note
Note: The wicked configuration compatibility with NetworkManager

The /etc/sysconfig/network/ifcfg-* files are usually compatible except for some rare cases. But when you use the wicked configuration located in /etc/wicked/*.xml, you need to migrate the configuration manually.

To change your networking managing service from wicked to NetworkManager, proceed as follows:

Procedure 6.1: Switching from wicked to NetworkManager
 

  1. Run the following command to create a new snapshot where you perform all other changes to the system: 

    # transactional-update shell

  2. Install NetworkManager: 

    # zypper in NetworkManager

  3. Remove wicked from the system: 

    # zypper rm wicked wicked-service

  4. Enable the NetworkManager service: 

    # systemctl enable NetworkManager

  5. If needed, configure the service according to your needs.

  6. Close the transactional-update shell: 

    # exit

  7. Reboot your system to switch to the new snapshot.