On 10/16/2012 4:27 AM, Reindl Harald wrote:

Am 16.10.2012 04:58, schrieb JD:
I googled this and came across 2 purported
solutions, neither of which worked.
1. Uninstall package biosdevname and reboot.

That did not prevent udevd from renaming eth0 to em1.

2. Add the line
biosdevname=0
to /boot/grub2/grub.cfg

That did not work either.
Any other way to get around this renaming?
find out your MAC-address with "ifconfig -a"
make a udev-rule like below (ONE line) for the MAC
reboot the machine after that and you are done

[root@rh:~]$ cat /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x8086:0x1502 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="78:ac:c0:b1:76:e4", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"



I can confirm that this is the way to go.  It works.

I tried the new names on three servers and didn't like it.  On one server my first ethernet device is em1; on another it is p14p1.   I find myself having to use ifconfig just to find out what name to use when I need to take a tcpdump.  (humor intended :-)  Then I have other interfaces like: p16p1 & p16p2 (dual card), and p17p1.  What if I move a card to a different slot?  Will my configuration suddenly fail?

On all the other boxen, eth0 is the LAN and eth1 is the interwebz.  Nothing much to remember for that.

Bill
PS.  See how cool I am?  I said boxen and interwebz.  :-)