Is anyone frustrated by Network Manager? I wish CentOS just used the basic configuration files like the ones on BSD-style OSes. Those are so simple in comparison. Each time I reboot, it seems like the configuration file I create for Network Manager gets destroyed and replaced with a default file. Nothing in the default file would actually make sense on my network, so I'm not even really sure how this machine is still connected to the network after a reboot destroys my previous configuration. The only way I seem to be able to keep my proper DNS settings is through the GUI interface to Network Manager. I have to enter the configuration in each time I reboot. At the very least, I just want to stop Network Manager from wiping out my perfectly fine /etc/resolv.conf. There has to be a better way. -- - EJR
John R. Dennison
2014-Apr-27 04:37 UTC
[CentOS] Disappearing Network Manager config scripts
On Sun, Apr 27, 2014 at 12:33:27AM -0400, Evan Rowley wrote:> Is anyone frustrated by Network Manager? I wish CentOS just used the basic > configuration files like the ones on BSD-style OSes. Those are so simple in > comparison.service NetworkManager stop chkconfig NetworkManager off vi /etc/sysconfig/network-scripts/ifcfg-ethX vi /etc/resolv.conf chkconfig network on service network start John -- We don't have education we have inspiration; if I was educated I would be a damn fool. -- Robert Nesta Marley (6 February 1945 - 11 May 1981), better known as Bob Marley, Jamaican singer, guitarist, songwriter, and social activist, in Time Will Tell (1992) a documentary by Declan Lowney -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20140426/fa9cdef2/attachment-0002.sig>
> service NetworkManager stop > chkconfig NetworkManager off > vi /etc/sysconfig/network-scripts/ifcfg-ethX > vi /etc/resolv.conf > chkconfig network on > service network startYes. Burn it with fire!
Marcelo Ricardo Leitner
2014-Apr-27 13:50 UTC
[CentOS] Disappearing Network Manager config scripts
Em 27-04-2014 01:33, Evan Rowley escreveu:> Is anyone frustrated by Network Manager? I wish CentOS just used the basic > configuration files like the ones on BSD-style OSes. Those are so simple in > comparison. > > Each time I reboot, it seems like the configuration file I create for > Network Manager gets destroyed and replaced with a default file. Nothing in > the default file would actually make sense on my network, so I'm not even > really sure how this machine is still connected to the network after a > reboot destroys my previous configuration. > > The only way I seem to be able to keep my proper DNS settings is through > the GUI interface to Network Manager. I have to enter the configuration in > each time I reboot. At the very least, I just want to stop Network Manager > from wiping out my perfectly fine /etc/resolv.conf. > > There has to be a better way.Your report is weird because NM should be able to work with your standard ifcfg-<interface> files, as described in https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-User_and_System_Connections.html If you think it's NM, a 'service NetworkManager restart' probably would reproduce the issue, and we could troubleshoot from there. If not, then something else is removing it and NM is just putting something where it was blank. Nevertheless, it's going to get much better on CentOS 7. NM has been really worked on and now includes a 'nmcli' command, for managing NM through the console/scripts. Marcelo
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/26/2014 11:37 PM, John R. Dennison wrote:> On Sun, Apr 27, 2014 at 12:33:27AM -0400, Evan Rowley wrote: >> Is anyone frustrated by Network Manager? I wish CentOS just used >> the basic configuration files like the ones on BSD-style OSes. >> Those are so simple in comparison. > > service NetworkManager stop chkconfig NetworkManager off vi > /etc/sysconfig/network-scripts/ifcfg-ethX vi /etc/resolv.conf > chkconfig network on service network startAlso helps to throw a line of "NM_CONTROLLED=NO" into /etc/sysconfig/network-scripts/ifcfg-ethX just to further tell it to go away. - -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTXRHLAAoJEBbHyC76Ca13QH8P/1jFOTaO42Iifz6pDkwPwI4r QS4vyITf8b3x9vlqCQFp+mhja8AVEZiq1+BF9T/wkmX6mK7tALh/osBw6V/6Rthu /iGE0sOOIsEPXiOQPeTtrs753EzTAINku6TPW6Oe3IGBwaDvA7dwqNc+bN0L/q0T 7b3maR54JHg8ZYC89A7JE70zNKWtfTWUe746boPckV2IRFGP9vTomo+WIOH6aRS3 NYuqPQZDZVMLhVR1aE7MHt2SG2SbhV+lhxe1W6q9F349sPkkVkdlQcTAlEginZTA 2wIqdWzSzgvIXTXwrJDlx8girNk1N+hcZ6s8xdZoE7rlMjoUf23WlOpdhRlonIYy Cg63RHbr+yd5KiZgYi5Qf6mmh16ZDJYuARU5whK9pgYxp+IsPkMJsAFiExl8yjaJ TG42t6/wuyjqQ+bhVM2XwygdJv+ZBjpmkQJVbtD3PfTsWpkOyvOzLXS6uUtduCZk 8aT5u2ggLky9U8UjMxlqYA/MoZkLGoX39XDNtSA6mplz94/5sayF4fB819XS8n9X ifFfsATgFJKFJv+eiTSGPfH1JNGoVBFfAgLfVgpAU3/rURfvNcpKD6x8pY6RZCTC +6UXAbgFL7ISq69pDJCY1dddh6dIPmBkMw595JwwB4WodSmIGihwE2q/KyDRKdnZ oWlijVAdNSSZ3KTcUcTw =SPTX -----END PGP SIGNATURE-----
On 04/27/2014 10:14 AM, Christopher Jacoby wrote:> I don't use NetworkManager on servers, only my laptop. Makes servers act > weird. >You know, you don't get NetworkManager on a server if you don't install the 'Desktop' group. The list of packages that actually require NetworkManager is very small. I have a development machine that also acts as a server, and it has NetworkManager installed, but it does not act 'weird' in networking.
On Apr 26, 2014, at 10:37 PM, John R. Dennison <jrd at gerdesas.com> wrote:> On Sun, Apr 27, 2014 at 12:33:27AM -0400, Evan Rowley wrote: >> Is anyone frustrated by Network Manager? I wish CentOS just used the basic >> configuration files like the ones on BSD-style OSes. Those are so simple in >> comparison. > > service NetworkManager stop > chkconfig NetworkManager off > vi /etc/sysconfig/network-scripts/ifcfg-ethX > vi /etc/resolv.conf > chkconfig network on > service network startHeh, You forgot... yum remove NetworkManager :-) -- Nate Duehr denverpilot at me.com
On 04/28/2014 06:19 PM, m.roth at 5-cent.us wrote:> Is this an impromptu poll? I think we had one for NM ("it's so much > better in fedora, it was reworked..."), and everyone else, if it's not > a laptop, wants it to Go Away. But will they listen to us?The answer is found in the package set for RHEL7. The time to have voted has long past, and was in the Fedora train. NM is and will be in EL7, and it will be there for ten years, if RH keeps to its support schedule. They won't pull it after the RC. At least in EL6 you can in fact yum remove NM without it taking your whole system away. I haven't tried on EL7. But, I also haven't had any issues with NetworkManager in my use cases, which includes much more than just laptops. I also am aware that others have had issues, particularly with bridging and bonding.