Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am aware that many people prefer to disable NetworkManager, but I don't believe it will be going away and I decided to try to learn how to use it properly. I thought I would begin with something simple, like setting a static IP.

I updated /etc/sysconfig/network-scripts/ifcfg-eth0 to match the settings I want it to have, then saved the file. From what I have read, NetworkManager is supposed to update the settings immediately, but it does not. In fact, after both restarting NM and after a reboot, eth0 keeps using dhcp. I am using a minimal install of Fedora 18 and have installed dhcp, but not yet configured it. ifconfig is no longer part of a minimal install, apparently it is headed towards deprecation.

Below is my ifcfg-eth0 file.


Below is output from ip addr:

#ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:24:75:2f brd ff:ff:ff:ff:ff:ff
    inet brd scope global eth0
    inet6 fe80::20c:29ff:fe24:752f/64 scope link
       valid_lft forever preferred_lft forever

Below is /etc/sysconfig/network:

share|improve this question
Can you give some more debug information? - What is in /etc/sysconfig/network? - Output of ifconfig -a – Andy Shinn Apr 12 '13 at 3:05
Addded your requested info. ifconfig is no longer part of a default minimal install. I provided an ip addr output instead, as it is intended to replace ifconfig going into the future. – fishpen0 Apr 12 '13 at 3:11
Congratulations, you're now beginning to learn why people dislike NetworkManager. – MadHatter Apr 12 '13 at 6:06
up vote 1 down vote accepted

The MAC address of your actual interfaces differs from your configured ifcfg script. It is likely ignoring the script because the MAC doesn't match. This is usually a safeguard to avoid adding IP addresses to the wrong interfaces in case the ifcfg-eth# names changed.

Try updating the HWADDR line in your file to be HWADDR=00:0c:29:24:75:2f. If this isn't the MAC you are expecting (as the name could have changed if this system has 2 NICs) you might also be interested in checkout out the /etc/udev/rules.d/70-persistent-net.rules file.

One last thing to note, this is coming from my knowledge of RHEL 5/6 and it looks like there is also a UUID in your more up to date Fedora implementation. If still have issues after fixing the MAC, you might try removing the UUID (I'm not sure how to verify that on Fedora).

share|improve this answer
Hmm, good find. This is likely because this is a linked clone. I am betting VMware changed the macs, but doesn't change the files. Everything is set now. – fishpen0 Apr 13 '13 at 15:35

The scripts in that directory are used by the 'network' service, not NetworkManager. You can choose which you would like to use. 'network' is for servers where the networking config changes rarely. You'll need to disable NetworkManager to use network.

To edit NetworkManager settings, use the nmcli tool, or the GUI.

share|improve this answer
Turns out the mac was incorrect in my settings. After fixing that, the changes kicked in immediately. NetworkManager does use those files. – fishpen0 Apr 13 '13 at 15:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.