Thursday, 28th March 2024

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

Share this on:

Tags: , , , , , , , , ,

No Responses to “…”

  1. admin says:
    Google Chrome 79.0.3945.130 Google Chrome 79.0.3945.130 Mac OS X  10.13.6 Mac OS X 10.13.6
    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 Comment
  2. Sudz says:
    Google Chrome 114.0.0.0 Google Chrome 114.0.0.0 Windows 10 x64 Edition Windows 10 x64 Edition
    Mozilla/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 Comment
  3. admin says:
    Google Chrome 91.0.4472.114 Google Chrome 91.0.4472.114 GNU/Linux x64 GNU/Linux x64
    Mozilla/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