Skip to main content

NetworkManager Is Supposed To Be Disabled But the Network Service is Deprecated!

Comments

5 comments

  • cPRex Jurassic Moderator

    Hey there!  That document is still correct - if NetworkManager was not automatically disabled you can follow the instructions in the guide or work with your host to get that turned off.

    0
  • consultant

    Yes, I already did that.  This actually can turn out to be quite tricky on some hosting instances as I discovered, in addition to editing /etc/sysconfig/network-scripts/ifcfg-eth0  (best to use static net config than DHCP on a server), and disabling network config of cloud-init which a lot of hosting providers use to configure the instance to use DHCP, manually creating the IP routing in /etc/sysconfig/network-scripts/route-eth0 is also required on some instances.  (I am just mentioning this for other users that wind up beating their head against the wall while their static net config isn't working - I know this is a bit separate issue from just disabling NetworkManager)

    However, your reply didn't address #2 pointing out Cpanel is essentially using deprecated network service and it is warning network-scripts could be removed in the future.  Isn't this something Cpanel has to address?

     

    0
  • cPRex Jurassic Moderator

    Sorry about that!  In AlmaLinux 9 and higher, cPanel doesn't disable NetworkManager, so it's addressed in future operating systems.

    0
  • consultant

    Thanks. So to make sure I understand correctly, NetworkManager needs to be disabled for AlamaLinux and Rocky versions earlier than 9.  The deprecation of network.service is not an issue as long as you stay on version 8 of those operating systems as the network-scripts removal only applies to newer versions than version 8.

     

    0
  • cPRex Jurassic Moderator

    Yes, that's exactly correct.

    0

Please sign in to leave a comment.