eno1, ens and eth devices - how is this possible?

[Pechvogel]

Hi guys,
like the headline says: how is it possible to have eno1, ens and eth network devices?
I have to additional nics installed, one with 4 ports (ens, works fine) and one with 2 ports that show eth. Also the number of the eth is totally random between 1 and 4.

If you need any more information, let me know and i hope someone here can help me to understand this and solve this problem. Because of this my network is broken after every reboot.
Thanks in advance

 

[maxim.webster]

See https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

 

[Pechvogel]

Thanks for your reply and after I read the text really carefully I found the part I didn't know about:

1 Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
2 Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
3 Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
4 Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
5 Classic, unpredictable kernel-native ethX naming (example: eth0)

By default, systemd v197 will now name interfaces following policy 1) if that information from the firmware is applicable and available, falling back to 2) if that information from the firmware is applicable and available, falling back to 3) if applicable, falling back to 5) in all other cases. Policy 4) is not used by default, but is available if the user chooses so.

So as far as I understand, please correct me if I am wrong, the problem is that the information from the firmware is not available?! (rule 5 applies then)

Is there a possibility to get these information?