{"id":4091,"date":"2014-12-24T19:03:28","date_gmt":"2014-12-24T11:03:28","guid":{"rendered":"http:\/\/rmohan.com\/?p=4091"},"modified":"2014-12-24T19:03:28","modified_gmt":"2014-12-24T11:03:28","slug":"how-to-change-a-network-interface-name-on-centos-7","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=4091","title":{"rendered":"How to change a network interface name on CentOS 7"},"content":{"rendered":"

Traditionally, network interfaces in Linux are enumerated as eth[0123…], but these names do not necessarily correspond to actual hardware slots, PCI geography, USB port number, etc. This introduces a unpredictable naming problem (e.g., due to undeterministic device probing behavior) which can cause various network misconfigurations (e.g., disabled interface or firewall bypass resulting from unintentional interface renaming). MAC address based udev<\/tt> rules are not so much helpful in a virtualized environment where MAC addresses are as euphemeral as port numbers.<\/p>\n

CentOS\/RHEL 6 has introduced a method for consistent and predictable network device naming<\/a> for network interfaces. These features uniquely determine the name of network interfaces in order to make locating and differentiating the interfaces easier and in such a way that it is persistent across later boots, time, and hardware changes. However, this naming rule is not turned on by default on CentOS\/RHEL 6.<\/p>\n

Starting with CentOS\/RHEL 7, the predictable naming rule is adopted by default. Under this rule, interface names are automatically determined based on firmware, topology, and location information. Now interface names stay fixed even if NIC hardware is added or removed without re-enumeration, and broken hardware can be replaced seamlessly.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n<\/td>\n
\n
\n
* Two character prefixes based on the <\/code>type<\/code> of interface:<\/code><\/div>\n
*\u00a0\u00a0 en -- ethernet<\/code><\/div>\n
*\u00a0\u00a0 sl -- serial line IP (slip)<\/code><\/div>\n
*\u00a0\u00a0 wl -- wlan<\/code><\/div>\n
*\u00a0\u00a0 ww -- wwan<\/code><\/div>\n
*<\/code><\/div>\n
* Type of names:<\/code><\/div>\n
*\u00a0\u00a0 b<number>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- BCMA bus core number<\/code><\/div>\n
*\u00a0\u00a0 ccw<name>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- CCW bus group name<\/code><\/div>\n
*\u00a0\u00a0 o<index>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- on-board device index number<\/code><\/div>\n
*\u00a0\u00a0 s<slot>[f<<\/code>function<\/code>>][d<dev_port>]\u00a0\u00a0\u00a0\u00a0 -- hotplug slot index number<\/code><\/div>\n
*\u00a0\u00a0 x<MAC>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- MAC address<\/code><\/div>\n
*\u00a0\u00a0 [P<domain>]p<bus>s<slot>[f<<\/code>function<\/code>>][d<dev_port>]<\/code><\/div>\n
*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- PCI geographical location<\/code><\/div>\n
*\u00a0\u00a0 [P<domain>]p<bus>s<slot>[f<<\/code>function<\/code>>][u<port>][..]1[i<interface>]<\/code><\/div>\n
*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -- USB port number chain<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

A minor disadvantage of this new naming scheme is that the interface names are somewhat harder to read than the traditional names. For example, you may find names like enp0s3<\/tt>. Besides, you no longer have any control over such interface names.<\/p>\n

 <\/p>\n

\"eth0001\"<\/a><\/p>\n

 <\/p>\n

If, for some reason, you prefer the old way, and want to be able to assign any arbitrary name of your choice to an interface on CentOS\/RHEL 7, you need to override the default predictable naming rule, and define a MAC address based udev<\/tt> rule.<\/p>\n

Here is how to rename a network interface on CentOS or RHEL 7<\/b>.<\/p>\n

 <\/p>\n

\"eth0002\"<\/a><\/p>\n

 <\/p>\n

First, let’s disable the predictable naming rule. For that, you can pass “net.ifnames=0” kernel parameter during boot. This is achieved by editing \/etc\/default\/grub and adding “net.ifnames=0” to GRUB_CMDLINE_LINUX variable.<\/p>\n

[root@localhost ~]# grub2-mkconfig -o \/boot\/grub2\/grub.cfg
\nGenerating grub configuration file …
\nFound linux image: \/boot\/vmlinuz-3.10.0-123.el7.x86_64
\nFound initrd image: \/boot\/initramfs-3.10.0-123.el7.x86_64.img
\nFound linux image: \/boot\/vmlinuz-3.10.0-123.13.1.el7.x86_64
\nFound initrd image: \/boot\/initramfs-3.10.0-123.13.1.el7.x86_64.img
\nFound linux image: \/boot\/vmlinuz-0-rescue-11510efe0881461cb2aa7cb613f65395
\nFound initrd image: \/boot\/initramfs-0-rescue-11510efe0881461cb2aa7cb613f65395.img
\ndone<\/p>\n

 <\/p>\n

Next, edit (or create) a udev<\/tt> network naming rule file (\/etc\/udev\/rules.d\/70-persistent-net.rules), and add the following line. Replace MAC address and interface with your own.<\/p>\n

$ vi \/etc\/udev\/rules.d\/70-persistent-net.rules<\/div>\n
<\/div>\n
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:0c:29:58:a6:b7″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”mohan”<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
\"eth0003\"<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"

Traditionally, network interfaces in Linux are enumerated as eth[0123…], but these names do not necessarily correspond to actual hardware slots, PCI geography, USB port number, etc. This introduces a unpredictable naming problem (e.g., due to undeterministic device probing behavior) which can cause various network misconfigurations (e.g., disabled interface or firewall bypass resulting from unintentional interface […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4,17],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4091"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4091"}],"version-history":[{"count":1,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4091\/revisions"}],"predecessor-version":[{"id":4095,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4091\/revisions\/4095"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4091"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4091"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4091"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}