Hi,
I'm currently experimenting with CentOS 7 on a couple of installations. I'm reasonably proficient with CentOS 5.x and 6.x.
I'd like to manage networking using a more traditional approach (Keep It Simple Stupid). Here's what I tried so far, starting from a minimal install:
Install net-tools (to be able to use ifconfig).
Get rid of NetworkManager:
# yum remove NetworkManager*
Add 'net.ifnames=0' and 'biosdevname=0' to kernel boot options to name interfaces eth0, eth1, etc.
Edit '/etc/sysconfig/network-scripts/ifcfg-eth{0,1}' like I did under previous versions.
Eventually, edit '/etc/udev/rules.d/70-persistent-net.rules' to switch interfaces:
# /etc/udev/rules.d/70-persistent-net.rules # # eth0 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \ ATTR{address}=="00:1e:c9:42:84:7b", ATTR{type}=="1", \ KERNEL=="eth*", NAME="eth0" # eth1 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \ ATTR{address}=="00:30:f1:6a:2f:40", ATTR{type}=="1", \ KERNEL=="eth*", NAME="eth1"
So far, no way to bring either eth0 or eth1 up. What am I doing wrong here? Is NetworkManager now a mandatory part of the base system? Some other mistake somewhere else? I'm a bit puzzled here.
Cheers,
Niki
Le 10/02/2015 15:35, Niki Kovacs a écrit :
So far, no way to bring either eth0 or eth1 up. What am I doing wrong here? Is NetworkManager now a mandatory part of the base system? Some other mistake somewhere else? I'm a bit puzzled here.
I'll answer that myself, after some more experimenting. Apparently, reverting to the traditional ethX interface naming scheme creates some unexpected behavior. I decided to keep the new persistent naming scheme (enp2s0 and enp3s1 on my server), and from there, everything works like expected.
Niki