Comment posted Fix eth changing network interface names from new Linux naming scheme ens, eno, em1 to legacy eth0, eth1, eth2 on CentOS Linux by .
Recent comments by
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Hey long time now see, thanks for dropping back again! 🙂
Previoust Post:
Next Post:
Tags: autogenerated name, CentOS, ems1, eno, eth0, eth1, eth2, fix wrong ethernet naming, linux?, scheme
This entry was posted
on Thursday, March 28th, 2024 at 4:27 pm and is filed under Everyday Life, Linux, System Administration.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
test
View CommentView CommentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
After reboot, my server is showing an "eno1" device but NOT the configured name for the device (enp1s0f0). In /etc/sysconfig/network-scripts/ there isn't even an eno1 config file, but there IS a config file for enp1s0f0 – why isn't it taking the enp1s0f0 information?
View CommentView CommentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
Sorry for really late reply.
perhaps you have to create it or rename the ifcfg-eno1 to ifcfg-eth1 or you have some old ifcfg-enp1s0f0 or ifcfg-eno still under /etc/sysconfig/network-scripts/ interfering
View CommentView Comment