What is the clean way of disabling NetworkManager

[johannlo]

I want to go back to the good old days.....
So I turned off networkmanager and turned on network. Didn't work for whatever reason, so I gung-hoed it and yum remove networkmanager.

Reboot later, I don't even see any network devices aside from lo...... network fails to start as it can't find any interfaces... ok.... what the..... why would removing networkmanager remove the system's ability to see the NIC? (which is still happily showing up in dmesg logs and lspci).

So after that experience I rebuilt my machine, and left networkmanager to its own devices (its a server with a LAN cable and static IP).

But I'm curious: whats the clean way in F15 to disable networkmanager and use the traditional RH way of configuring eth0?

[glennzo]

These commands should work:

PHP Code:

systemctl stop NetworkManager.service
systemctl disable NetworkManager.service 


Then you enable the network service in a similar fashion.

PHP Code:

systemctl enable network.service
systemctl start network.service 


[JohnVV]

mjmwired's old fedora 14 guide will help
http://www.mjmwired.net/resources/mjm-services-f14.html

[jpollard]

You may need to redefine your network interfaces. NetworkManager uses the same files, and the removal most likely removed the configuration files too.

[johannlo]

OK cheers

I used the traditional RH 'service XYZ stop/start' method, I'm guessing systemctl is the new way of doing things?

For some reason stopping/starting NM and network using service didn't work but maybe systemctl will.

Will definitely NOT remove networkmanager lol I ahve no idea how to define interfaces

[johannlo]

FWIW the systemctl method worked perfectly, but I had to manually add a default route.
The impressive (?) thing was that the static IP I had set via networkmanager seemed to be seamlessly carried across. Though why it didn't carry the default route across, no idea. Oh well

[smr54]

From time to time, (when I've done default installs, which include NM), it seems that stopping it still leaves various things running, such as dhclient, which NM assumes you want. Nowadays, I do minimal installs, which don't include NM. These days, I usually run system-config-network-tui. I used to just manually configure ifcfg-eth0, but stevea has pointed out elsewhere that there are various other files and/or scripts (I don't remember the exact details) that are affected, so one is better off using the tool.

However, even after doing that, I have to manually edit the file, which will choose to not start it at boot and will assume it is controlled by NM--there's a line in there NM_CONTROLLED="yes" that seems to get set after running system-config-network-tui.

The old chkconfig and service commands should still work, they've worked to make it compatible, though chkconfig --list no longer works, IIRC.

[JohnVV]

i normally use ifup
on fedora and cent and SL i turn off NM .That is UNLESS there is a wireless connection like a laptop .

on suse 11.4i use ifup

99% of the time the older network tool will get the ip from dhcp ( set to NOT change DNS) -- i like 8.8.8.8

now 15 IS A BIT different the boot process changed , and it it time i learn the new programs .

[boinc]

Originally Posted by glennzo

These commands should work:

PHP Code:

systemctl stop NetworkManager.service
systemctl disable NetworkManager.service 


Then you enable the network service in a similar fashion.

PHP Code:

systemctl enable network.service
systemctl start network.service 


Tried this on FC16, but I'm not able to disable it - only stop it. But after next boot my network is gone!

How can I manually set the IP address and get rid of the Network Manager once and for all??

[jpollard]

Make sure the network configuration files have "NM_CONTROLLED=no" AND has "ONBOOT=yes".

[boinc]

I did that, but it did not seem to work.
Later I found out that the network script was not executed during startup. A link in /etc/rc3.d was missing. Adding it fixed the problem.