Thanks Barry,
On 15/7/24 7:09 pm, Barry wrote:
On 14 Jul 2024, at 11:44, fedora@xxxxxxxxxxxxxx wrote:
I notice that the network interface 'eth1' is now renamed 'enp2s0' but eth0 is left alone.
The reason for the renaming is to ensure that the interface names are consistent in every boot. It is an issue on some systems that an interface may be eth0 on one boot the eth1 on the next.
I do not understand the logic. If the name is assigned to a MAC then it will be stable regardless, on every boot.
Consider using the new naming so you have stability.
FYI it’s been this way for many years, not sure why this
was not the case in f38 for you.
Also the use of the ifcfg files is legacy, you should migrate to NetworkManager.
I agree, I need to bite the bullet. A difficult new trick for an old dog.
I see that I can use nm-connection-editor (GUI) or nmcli (cli).
Is the "old" 'interface' term equivalent to nm 'connection' or 'device'? For example when used with tcpdump?
'nmcli device show' lists two devices, enp2s0 and eth0.
'nmcli connection show' lists 4 ether connections,
'nmcli' shows
enp2s0: connected to Wired connection 2
eth0: unmanaged
'nm-connection-editor; lists 4 ether connections, two have 1/2 days "Last Used", two say 4-years/never.
Probably safe to delete the two old ones. Then sort out the other two.
So a mishmash...
In f41 the ifcfg support is proposed to be fully remived from Fedora.
Barry
--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
