NetworkManager is not managing the lo interface

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux (RHEL) 7.
  • Red Hat Enterprise Linux (RHEL) 6.
  • NetworkManager.service

Issue

  • The lo interface is shown as "unmanaged" in NetworkManager.
  • How do I manage the lo interface using NetworkManager?

Resolution

  • NetworkManager leaves the lo interface unmanaged by design. Refer
  • If another loopback address is needed, you can also add a secondary loopback address to the ifcfg-lo file and bring the interface up using the network service scripts.
  • Please open a support case with Red Hat if you feel that you have a deployment requirement that necessitates using NetworkManager to manage the lo interface.

Diagnostic Steps

  • Check the device state using NetworkManager :
#  nmcli device show
DEVICE      TYPE      STATE      CONNECTION    
virbr0      bridge    connected  virbr0        
enp0s25     ethernet  connected  enp0s25       
lo          loopback  unmanaged  --            
virbr0-nic  tun       unmanaged  --

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.