CentOS 7.3 interface name changes every reboot Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionNetwork Manager Connected - No wifiLinux network stops functioning after random time (wired)Setting interface NM_CONTROLLED to yes using nmcli in CentOS 7?How to detect / prevent systemd network startup failuresNew network interface created after reboot - OEL 6Forcing HWADDR to correct itself in ifcfg-eth0 network script on boot CentOS 7File /etc/resolv.conf deleted on every reboot, why or what?NetworkManager service interfering with my connection in kaliCentos 7 auto reboot every 12 daysLogin page is not reachable with arch linux
Overriding an object in memory with placement new
What LEGO pieces have "real-world" functionality?
Single word antonym of "flightless"
3 doors, three guards, one stone
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
How to align text above triangle figure
Why do we bend a book to keep it straight?
porting install scripts : can rpm replace apt?
If a contract sometimes uses the wrong name, is it still valid?
Output the ŋarâþ crîþ alphabet song without using (m)any letters
How to answer "Have you ever been terminated?"
Why did the rest of the Eastern Bloc not invade Yugoslavia?
How do I stop a creek from eroding my steep embankment?
Coloring maths inside a tcolorbox
Should I discuss the type of campaign with my players?
What's the purpose of writing one's academic biography in the third person?
What does this icon in iOS Stardew Valley mean?
How to call a function with default parameter through a pointer to function that is the return of another function?
Is it true that "carbohydrates are of no use for the basal metabolic need"?
How come Sam didn't become Lord of Horn Hill?
Fundamental Solution of the Pell Equation
Check which numbers satisfy the condition [A*B*C = A! + B! + C!]
How to find all the available tools in mac terminal?
List *all* the tuples!
CentOS 7.3 interface name changes every reboot
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionNetwork Manager Connected - No wifiLinux network stops functioning after random time (wired)Setting interface NM_CONTROLLED to yes using nmcli in CentOS 7?How to detect / prevent systemd network startup failuresNew network interface created after reboot - OEL 6Forcing HWADDR to correct itself in ifcfg-eth0 network script on boot CentOS 7File /etc/resolv.conf deleted on every reboot, why or what?NetworkManager service interfering with my connection in kaliCentos 7 auto reboot every 12 daysLogin page is not reachable with arch linux
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have this annoying problem that every time I restart my CentOS7.3, my interface name changes (all of them). Here is how I use my CentOS7.3:
Host Machine: CentOS7.0
VM: CentOS7.3 (recently updated, run via kvm)
Here is the background. I recently updated my VM that has CentOS7.0 to CentOS7.3 via yum update (offline upgrade via ISO). All was working in CentOS7.0, I did not have any persistent rules in /usr/lib/udev/rules.d. But when I updated it to CentOS7.3, the problem started. Every time I reboot the VM, the interface name changes from ethX to lanX. This happens every time I reboot (soft reboot/hard reboot). I found some article in RedHat that says refer to this article. Somewhat resembles my problem but not entirely the same, just went on and tried the fix but still the problem is there. Interface name still changes from ethX to lanX on every reboot.
I tried to single out the problem and arrived at NetworkManager. What I did was I added a field NM_CONTROLLEDon each of the ifcfg-ethX and set to no and it fixed the problem. But I need it to be managed by NetworkManager.
Is there any issue with NetworkManager in CentOS7.3?
Additional Info:
NetworkManager-1.4.0-12 ← this is my version of NM
UPDATES 1
After trying the answer of @Sagar, it somewhat cleared things but did not fix the problem. Interface name still changes every reboot. But it did point me to Consistent Network Device Naming wherein it tells you the details of the naming scheme of red hat. Makes sense though as what @Sagar is saying you need to put net.ifnames=0 biosdevname=0on the kernel command line to revert back to old naming convention. As mention on that article, RHEL has some new name scheme being implemented. But still i can't seem to revert back to the old naming scheme. Any more inputs about the naming convention?
centos networkmanager nmcli
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
add a comment |
I have this annoying problem that every time I restart my CentOS7.3, my interface name changes (all of them). Here is how I use my CentOS7.3:
Host Machine: CentOS7.0
VM: CentOS7.3 (recently updated, run via kvm)
Here is the background. I recently updated my VM that has CentOS7.0 to CentOS7.3 via yum update (offline upgrade via ISO). All was working in CentOS7.0, I did not have any persistent rules in /usr/lib/udev/rules.d. But when I updated it to CentOS7.3, the problem started. Every time I reboot the VM, the interface name changes from ethX to lanX. This happens every time I reboot (soft reboot/hard reboot). I found some article in RedHat that says refer to this article. Somewhat resembles my problem but not entirely the same, just went on and tried the fix but still the problem is there. Interface name still changes from ethX to lanX on every reboot.
I tried to single out the problem and arrived at NetworkManager. What I did was I added a field NM_CONTROLLEDon each of the ifcfg-ethX and set to no and it fixed the problem. But I need it to be managed by NetworkManager.
Is there any issue with NetworkManager in CentOS7.3?
Additional Info:
NetworkManager-1.4.0-12 ← this is my version of NM
UPDATES 1
After trying the answer of @Sagar, it somewhat cleared things but did not fix the problem. Interface name still changes every reboot. But it did point me to Consistent Network Device Naming wherein it tells you the details of the naming scheme of red hat. Makes sense though as what @Sagar is saying you need to put net.ifnames=0 biosdevname=0on the kernel command line to revert back to old naming convention. As mention on that article, RHEL has some new name scheme being implemented. But still i can't seem to revert back to the old naming scheme. Any more inputs about the naming convention?
centos networkmanager nmcli
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05
add a comment |
I have this annoying problem that every time I restart my CentOS7.3, my interface name changes (all of them). Here is how I use my CentOS7.3:
Host Machine: CentOS7.0
VM: CentOS7.3 (recently updated, run via kvm)
Here is the background. I recently updated my VM that has CentOS7.0 to CentOS7.3 via yum update (offline upgrade via ISO). All was working in CentOS7.0, I did not have any persistent rules in /usr/lib/udev/rules.d. But when I updated it to CentOS7.3, the problem started. Every time I reboot the VM, the interface name changes from ethX to lanX. This happens every time I reboot (soft reboot/hard reboot). I found some article in RedHat that says refer to this article. Somewhat resembles my problem but not entirely the same, just went on and tried the fix but still the problem is there. Interface name still changes from ethX to lanX on every reboot.
I tried to single out the problem and arrived at NetworkManager. What I did was I added a field NM_CONTROLLEDon each of the ifcfg-ethX and set to no and it fixed the problem. But I need it to be managed by NetworkManager.
Is there any issue with NetworkManager in CentOS7.3?
Additional Info:
NetworkManager-1.4.0-12 ← this is my version of NM
UPDATES 1
After trying the answer of @Sagar, it somewhat cleared things but did not fix the problem. Interface name still changes every reboot. But it did point me to Consistent Network Device Naming wherein it tells you the details of the naming scheme of red hat. Makes sense though as what @Sagar is saying you need to put net.ifnames=0 biosdevname=0on the kernel command line to revert back to old naming convention. As mention on that article, RHEL has some new name scheme being implemented. But still i can't seem to revert back to the old naming scheme. Any more inputs about the naming convention?
centos networkmanager nmcli
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
I have this annoying problem that every time I restart my CentOS7.3, my interface name changes (all of them). Here is how I use my CentOS7.3:
Host Machine: CentOS7.0
VM: CentOS7.3 (recently updated, run via kvm)
Here is the background. I recently updated my VM that has CentOS7.0 to CentOS7.3 via yum update (offline upgrade via ISO). All was working in CentOS7.0, I did not have any persistent rules in /usr/lib/udev/rules.d. But when I updated it to CentOS7.3, the problem started. Every time I reboot the VM, the interface name changes from ethX to lanX. This happens every time I reboot (soft reboot/hard reboot). I found some article in RedHat that says refer to this article. Somewhat resembles my problem but not entirely the same, just went on and tried the fix but still the problem is there. Interface name still changes from ethX to lanX on every reboot.
I tried to single out the problem and arrived at NetworkManager. What I did was I added a field NM_CONTROLLEDon each of the ifcfg-ethX and set to no and it fixed the problem. But I need it to be managed by NetworkManager.
Is there any issue with NetworkManager in CentOS7.3?
Additional Info:
NetworkManager-1.4.0-12 ← this is my version of NM
UPDATES 1
After trying the answer of @Sagar, it somewhat cleared things but did not fix the problem. Interface name still changes every reboot. But it did point me to Consistent Network Device Naming wherein it tells you the details of the naming scheme of red hat. Makes sense though as what @Sagar is saying you need to put net.ifnames=0 biosdevname=0on the kernel command line to revert back to old naming convention. As mention on that article, RHEL has some new name scheme being implemented. But still i can't seem to revert back to the old naming scheme. Any more inputs about the naming convention?
centos networkmanager nmcli
centos networkmanager nmcli
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
edited Jul 4 '17 at 14:52
lemoncodes
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
asked Jul 3 '17 at 15:13
lemoncodeslemoncodes
1013
1013
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05
add a comment |
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05
add a comment |
1 Answer
1
active
oldest
votes
Try this article. This may help you to put your interface to old native names as it was before RHEL/CentOS 7.
To restore the old naming convention, you need to edit the /etc/default/grub file and add net.ifnames=0 biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/swap vconsole.keymap=us crashkernel=auto rd.lvm.lv=centos/root vconsole.font=latarcyrheb-sun16 rhgb quiet net.ifnames=0 biosdevname=0"
Then, test the new configuration to see if no mistake has been made:
# grub2-mkconfig
If everything is fine, update the grub2 configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Dont forgot to rename your ifcfg-* file to appropriate once your network is up and interface name is stable.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f374996%2fcentos-7-3-interface-name-changes-every-reboot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try this article. This may help you to put your interface to old native names as it was before RHEL/CentOS 7.
To restore the old naming convention, you need to edit the /etc/default/grub file and add net.ifnames=0 biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/swap vconsole.keymap=us crashkernel=auto rd.lvm.lv=centos/root vconsole.font=latarcyrheb-sun16 rhgb quiet net.ifnames=0 biosdevname=0"
Then, test the new configuration to see if no mistake has been made:
# grub2-mkconfig
If everything is fine, update the grub2 configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Dont forgot to rename your ifcfg-* file to appropriate once your network is up and interface name is stable.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
add a comment |
Try this article. This may help you to put your interface to old native names as it was before RHEL/CentOS 7.
To restore the old naming convention, you need to edit the /etc/default/grub file and add net.ifnames=0 biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/swap vconsole.keymap=us crashkernel=auto rd.lvm.lv=centos/root vconsole.font=latarcyrheb-sun16 rhgb quiet net.ifnames=0 biosdevname=0"
Then, test the new configuration to see if no mistake has been made:
# grub2-mkconfig
If everything is fine, update the grub2 configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Dont forgot to rename your ifcfg-* file to appropriate once your network is up and interface name is stable.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
add a comment |
Try this article. This may help you to put your interface to old native names as it was before RHEL/CentOS 7.
To restore the old naming convention, you need to edit the /etc/default/grub file and add net.ifnames=0 biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/swap vconsole.keymap=us crashkernel=auto rd.lvm.lv=centos/root vconsole.font=latarcyrheb-sun16 rhgb quiet net.ifnames=0 biosdevname=0"
Then, test the new configuration to see if no mistake has been made:
# grub2-mkconfig
If everything is fine, update the grub2 configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Dont forgot to rename your ifcfg-* file to appropriate once your network is up and interface name is stable.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
Try this article. This may help you to put your interface to old native names as it was before RHEL/CentOS 7.
To restore the old naming convention, you need to edit the /etc/default/grub file and add net.ifnames=0 biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/swap vconsole.keymap=us crashkernel=auto rd.lvm.lv=centos/root vconsole.font=latarcyrheb-sun16 rhgb quiet net.ifnames=0 biosdevname=0"
Then, test the new configuration to see if no mistake has been made:
# grub2-mkconfig
If everything is fine, update the grub2 configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Dont forgot to rename your ifcfg-* file to appropriate once your network is up and interface name is stable.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
42.1k1484142
answered Jul 3 '17 at 15:36
SagarSagar
168110
answered Jul 3 '17 at 15:36
SagarSagar
168110
answered Jul 3 '17 at 15:36
SagarSagar
168110
168110
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
add a comment |
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
1
1
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
link-only answers are susceptible to link-rot. Please edit your answer to include enough relevant information from the linked article to provide a stand-alone explanation.
– user4556274
Jul 3 '17 at 15:41
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Im gonna try this feedback you in a bit
– lemoncodes
Jul 4 '17 at 0:11
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
Somewhat cleared somethings but did not fix the problem. please refer to the updates on the post. Thanks
– lemoncodes
Jul 4 '17 at 14:45
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
This may be coz your guest is running inside kvm. Your kvm configuration might be causing something to alter the udev. I read this article from the redhat, This somewhat resembles to your problem : access.redhat.com/solutions/2592561
– Sagar
Jul 6 '17 at 11:02
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f374996%2fcentos-7-3-interface-name-changes-every-reboot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-centos, networkmanager, nmcli
NetworkManager never renames interfaces. That is commonly done by udev. Note that there is an udev rule that checks ifcfg-rh files whether they mention a Mac address and an interface. if so, the interfaces are renamed.
– thaller
Jul 3 '17 at 18:59
Do you mean that persistent rules in udev? I have none. I am also greping my mac address in my udev folder and found none. Which rules are you refering to?
– lemoncodes
Jul 4 '17 at 0:05