I've been banging my head against the wall trying to get a simple two NIC bond to work. Got really odd behavior from service network restart, then finally decided to disable NetworkManager. Voila! Bonding and the network service script starts working just the way I expect.
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
Chris
On 03/25/2014 10:35 PM, Christopher Jacoby wrote:
I've been banging my head against the wall trying to get a simple two NIC bond to work. Got really odd behavior from service network restart, then finally decided to disable NetworkManager. Voila! Bonding and the network service script starts working just the way I expect.
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
I never use NetworkManager on CentOS-5 or CentOS-6 with static IPs ... but that is more a personal preference than for any other reason.
I basically only use NetworkManager on wireless laptops that are mobile because it is very easy to get an IP or connect to the VPNs I need from many different places. But I am a salty old dog .. and you know what they say about teaching us new tricks :D
On 03/25/2014 11:35 PM Christopher Jacoby wrote:
I've been banging my head against the wall trying to get a simple two NIC bond to work. Got really odd behavior from service network restart, then finally decided to disable NetworkManager. Voila! Bonding and the network service script starts working just the way I expect.
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
Chris
Three or four of five times I tried using it and every time it messed things up much more than it helped. And each time, after a bit more investigation and playing around with configuration files, I got things to work without using NM. So I don't use it anymore... and don't recommend it to anyone else.
On 03/25/2014 11:35 PM, Christopher Jacoby wrote:
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
Hi,
I asked a similar question on the NetworkManager list a while ago:
https://mail.gnome.org/archives/networkmanager-list/2014-January/msg00061.ht...
There's a reply from one of the developers.
On Wed, Mar 26, 2014 at 06:42:28AM -0400, Jorge Fábregas wrote:
On 03/25/2014 11:35 PM, Christopher Jacoby wrote:
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
As the mail thread shows, Fedora is making it more of a base system item.
https://mail.gnome.org/archives/networkmanager-list/2014-January/msg00061.ht...
However, judging by Fedora forums, (but this is hearsay--as another old person disliking change, I remove it on everything, even laptops), it seems to still sometimes cause problems. However, that's hearsay, and quite possibly only causes problems for newcomers, I don't follow any of the threads that closely. It does seem that hand editing /etc/sysconfig/network-scripts/ifcfg-whatever doesn't completely work anymore--however, I can't confirm that, I've run into it at random times, and one can get a card working properly with system-config-network-tui.
(On Fedora, not on CentOS-6.x--on CentOS, hand editing the file works as expected)
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
I don't. I do some fairly complex bonding, and do not use NetworkManager at all. Make sure you have NM_CONTROLLED=no and HWADDR=<MAC address> in your interface config files. I don't even have NetworkManager installed on my servers at all.
On 03/25/2014 11:35 PM, Christopher Jacoby wrote:
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
My RHEL 6 dev server is using NM with four NICs and runs fine. It doesn't seem to add any value, but I've not had any problems with it either. The four NICs aren't bonded, they're on separate VLANs and subnets. One NIC was set up during install, one was setup during firstboot, and the other two were set up in the NM GUI config.
It appears NM will no longer be optional on EL7, though, at least that's my understanding of the current situation. But I reserve the right to be wrong.
On 03/26/2014 10:20 AM, Lamar Owen wrote:
On 03/25/2014 11:35 PM, Christopher Jacoby wrote:
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
My RHEL 6 dev server is using NM with four NICs and runs fine. It doesn't seem to add any value, but I've not had any problems with it either. The four NICs aren't bonded, they're on separate VLANs and subnets. One NIC was set up during install, one was setup during firstboot, and the other two were set up in the NM GUI config.
It appears NM will no longer be optional on EL7, though, at least that's my understanding of the current situation. But I reserve the right to be wrong.
Not optional? You mean I won't be able to ip a s xxxx dev xxxx, etc?
What is you have only a serial console?
On 03/27/2014 03:20 AM, Lamar Owen wrote:
It appears NM will no longer be optional on EL7, though, at least that's my understanding of the current situation. But I reserve the right to be wrong.
They make it appear to not be optional. It's in the core package group, but I was able to do a core install of RHEL7 beta without NM and it runs just fine.
Peter
On Wed, Mar 26, 2014 at 9:05 AM, Christopher Jacoby cjacoby75@gmail.com wrote:
I've been banging my head against the wall trying to get a simple two NIC bond to work. Got really odd behavior from service network restart, then finally decided to disable NetworkManager. Voila! Bonding and the network service script starts working just the way I expect.
Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason to use it on a server.
IMO, Network Manager is for desktop users who may connect to the 'Net in various ways, wired LAN, WiFi, USB data dongles (from Telcom providers).
With bridging and bonding scenarios, it causes more heartburn than ease of use. Server installs that I undertake personally, it is turned OFF.
However, when I have had to service other admin's installation, for networking issues, I turn OFF the Network Manager.
-- Arun Khan
-
Arun Khan -
Barry Brimer -
Christopher Jacoby -
Johnny Hughes -
Jorge Fábregas -
ken -
Lamar Owen -
Peter -
Scott Robbins -
Steve Clark