hi all,
on F30, i would like to swap enp4s0 to eth0.
outside the network ifcfg* files, any other place(file) to update?
i scanned /etc/ find no additional references.
also any wisdom that sez this idea is folly??
tia, jackc...
On Fri, 10 Apr 2020 11:53:11 -0700 Jack Craig wrote:
on F30, i would like to swap enp4s0 to eth0.
You have to get the system to stop inventing "immutable" names first, which means adding net.ifnames=0 biosdevname=0 to the kernel boot parameters which means learning how to use grub2-editenv since the BLS stuff moved all kernel parameters into the environment file.
thanks tom, i knew there was more to it. thx, jackc...
On Fri, Apr 10, 2020 at 12:03 PM Tom Horsley horsley1953@gmail.com wrote:
On Fri, 10 Apr 2020 11:53:11 -0700 Jack Craig wrote:
on F30, i would like to swap enp4s0 to eth0.
You have to get the system to stop inventing "immutable" names first, which means adding net.ifnames=0 biosdevname=0 to the kernel boot parameters which means learning how to use grub2-editenv since the BLS stuff moved all kernel parameters into the environment file. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Fri, Apr 10, 2020 at 9:03 PM Tom Horsley horsley1953@gmail.com wrote:
On Fri, 10 Apr 2020 11:53:11 -0700 Jack Craig wrote:
on F30, i would like to swap enp4s0 to eth0.
You have to get the system to stop inventing "immutable" names first, which means adding net.ifnames=0 biosdevname=0 to the kernel boot parameters which means learning how to use grub2-editenv since the BLS stuff moved all kernel parameters into the environment file.
If you edit "/etc/default/grub" and run grub2-mkconfig, grubenv is updated with changed kernel options (via "/etc/grub.d/10_linux").
thx frank,
tom got me pointed in the right direction and your info here is a Big push down that path.
thx again, jackc...
On Fri, Apr 10, 2020 at 12:13 PM Frank Elsner frank.elsner@mailbox.org wrote:
On Fri, 10 Apr 2020 11:53:11 -0700 Jack Craig wrote:
hi all,
on F30, i would like to swap enp4s0 to eth0.
For this my /etc/default/grub contains
GRUB_CMDLINE_LINUX="net.ifnames=0 ..."Greetings, Frank _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Fri, Apr 10, 2020 at 8:54 PM Jack Craig jack.craig.aptos@gmail.com wrote:
on F30, i would like to swap enp4s0 to eth0.
outside the network ifcfg* files, any other place(file) to update?
i scanned /etc/ find no additional references.
The simplest is to add "net.ifnames=0" to "GRUB_CMDLINE_LINUX" in "/etc/default/grub" and run grub2-mkconfig.
On 2020-04-10 20:53, Jack Craig wrote:
hi all,
on F30, i would like to swap enp4s0 to eth0.
outside the network ifcfg* files, any other place(file) to update?
Having a proper ifcfg*, including the HWADDR MAC address used to be enough (but be sure you rebuild your initrd since renaming happens there).
https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-Und...
Is that not working anymore?
Messing with grub kernel options looks definitely overkill.
Regards.
a big thanks to those that commented on this thread.
further reading of some RH portal docs, i decided my notion was an unacceptable step backward in techs stream of forward progress.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...
Thx again, jackc...
On Sun, Apr 12, 2020 at 9:10 AM Roberto Ragusa mail@robertoragusa.it wrote:
On 2020-04-10 20:53, Jack Craig wrote:
hi all,
on F30, i would like to swap enp4s0 to eth0.
outside the network ifcfg* files, any other place(file) to update?
Having a proper ifcfg*, including the HWADDR MAC address used to be enough (but be sure you rebuild your initrd since renaming happens there).
https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-Und...
Is that not working anymore?
Messing with grub kernel options looks definitely overkill.
Regards.
-- Roberto Ragusa mail at robertoragusa.it _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Sun, 12 Apr 2020 13:33:50 -0700 Jack Craig wrote:
further reading of some RH portal docs, i decided my notion was an unacceptable step backward in techs stream of forward progress.
I consider the "improvement" a step backwards. Certainly for a desktop system with one and only one ethernet port. The immutable name for a single ethernet port should always be "eth0" :-).
(Especially since "immutable" names have changed several times with new kernels, switching to systemd in charge instead of biosdevname etc).
it is not a step back for enterprise servers with 2 or more vendors ethernet cards.
We were doing a udev rule (by pci-busid) so the right cards were in the right places, and had (pci-busid) rules for each model so that the names were always the same. The "new" standard makes what we (and probably others) were doing no longer required since the new naming scheme matches the scheme we were using. The pci-busid scheme also would allow us to swap a bad chassis (mb+cards) with one of the same model and it would just work. Using the mac-address naming made these swaps a big mess (the mac addresses had to be updated), where-as the new naming scheme worked for that seamlessly.
The only negative part I have seen is that on one of my desktop systems at home removing/adding a pci card changes the PCI-busid of the built-in network card (guessing badly designed/coded bios).
On Sun, Apr 12, 2020 at 3:40 PM Tom Horsley horsley1953@gmail.com wrote:
On Sun, 12 Apr 2020 13:33:50 -0700 Jack Craig wrote:
further reading of some RH portal docs, i decided my notion was an unacceptable step backward in techs stream of forward progress.
I consider the "improvement" a step backwards. Certainly for a desktop system with one and only one ethernet port. The immutable name for a single ethernet port should always be "eth0" :-).
(Especially since "immutable" names have changed several times with new kernels, switching to systemd in charge instead of biosdevname etc). _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On 13/04/2020 07:47, Roger Heflin wrote:
The only negative part I have seen is that on one of my desktop systems at home removing/adding a pci card changes the PCI-busid of the built-in network card (guessing badly designed/coded bios).
And that's exactly why the whole naming this is a PITA and doesn't solve much anyway. It really is not that easier now playing guess the NIC than it was when everything was eth*. Besides the supposed slot numbering system often does match reality for the same reasons you say... the BIOS being stupid.
If you are managing 1 or 10 that are not the same, then yes, but if one is managing 10,000+ physical linu servers with a very few models/layouts (spanning the 5-9 year life you are dealing with) and you up front determine the mappings by model then by pcid mapping is great.
Prior to the pciids naming scheme, it depended on the order the drivers were loaded, and if you added the cards after the fact it showed up after the current cards (udev rule mapping by mac address and/or mac address mapping in ifcfg files).
And if you involve the mac addresses anywhere replacing any failing hardware becomes a complicated process, as you have to find the udev rule/ifcfg-hwaddr and fix it, and if the node was dead when you do the replacement one has to often take it to single user mode and sort out the mac addresses. With the pciids, then replacement with a like identical replacement is easy, as the new machine just boots up and works, with mac addresses, it does boot up, but the network fails and has to be manually fixed. And when one is managing a bunch of systems this becomes a problem, the pciids also result in the configurations of a like model all having the exact same names for the same physical cards at the same locations which make things much simpler for the automation building systems and the people cabling the systems.
On Sat, Apr 18, 2020 at 5:42 AM Ian Chapman packages@amiga-hardware.com wrote:
On 13/04/2020 07:47, Roger Heflin wrote:
The only negative part I have seen is that on one of my desktop systems at home removing/adding a pci card changes the PCI-busid of the built-in network card (guessing badly designed/coded bios).
And that's exactly why the whole naming this is a PITA and doesn't solve much anyway. It really is not that easier now playing guess the NIC than it was when everything was eth*. Besides the supposed slot numbering system often does match reality for the same reasons you say... the BIOS being stupid.
-- Regards, Ian Chapman _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Sun, Apr 12, 2020 Tom Horsley horsley1953@gmail.com wrote:
On Sun, 12 Apr 2020 Jack Craig wrote:
further reading of some RH portal docs, i decided my notion was an unacceptable step backward in techs stream of forward progress.
I consider the "improvement" a step backwards. Certainly for a desktop system with one and only one ethernet port. The immutable name for a single ethernet port should always be "eth0" :-).
The improvement's when you have a multiple NICs and swap one out. You no longer have to edit "/etc/udev/rules.d/<something>.rules" in order to have the swapped-in NIC keep the name of the swapped-out NIC.
(Especially since "immutable" names have changed several times with new kernels, switching to systemd in charge instead of biosdevname etc).
systemd over-promised in [1] when it claimed "Stable interface names when kernels or drivers are updated/changed".
In [2], there's a more realistic "Newer versions of udev take more of these attributes into account, improving (and thus possibly changing) the names and addresses used for the same devices", assuming that this is referring to a driver or firmware change.
[1] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac...
[2] https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.h...
On Tue, 14 Apr 2020 00:26:28 +0200 Tom H wrote:
The improvement's when you have a multiple NICs
Right, but they should have special cased a single NIC system and just left the name eth0, would have avoided vast amounts of trouble for people with common desktops that only have a single NIC.
On Tue, Apr 14, 2020 at 12:44 AM Tom Horsley horsley1953@gmail.com wrote:
On Tue, 14 Apr 2020 00:26:28 +0200 Tom H wrote:
The improvement's when you have a multiple NICs
Right, but they should have special cased a single NIC system and just left the name eth0, would have avoided vast amounts of trouble for people with common desktops that only have a single NIC.
They could have but there are at least two reasons why it wasn't really necessary.
1) It's extra code to maintain.
2) _MOST_ users with one NIC, eth0 or wlan0, or with two NICs, eth0 and wlan0, will use NetworkManager and not care about the NIC names. The connections'll be, IIRC, "Wired connection 1" or "SSID".
I wish that they'd exposed non-kernel names to networking tools, like Solaris' "netX", with a correspondence to the index- and slot-based names. The names would've been stable and usable. That's how I set up my systems, even those with one NIC.
On Tue, 2020-04-14 at 00:26 +0200, Tom H wrote:
The improvement's when you have a multiple NICs and swap one out. You no longer have to edit "/etc/udev/rules.d/<something>.rules" in order to have the swapped-in NIC keep the name of the swapped-out NIC.
My understanding of how the device names were generated was that if you didn't replace a NIC with an identical model, in the exact same spot, you could well end up with a different device name.
There was an order of how to name things, starting at the top, going down the list if that scheme wasn't do-able:
Firmware or BIOS can form the device name.
Board location can form the name (derived from things like PCI slot 2).
Number of connectors on the board can be used in forming the name (adding more details to the above naming scheme).
Heck knows what mine's derived from (enp0s31f6 is the motherboard's own built in ethernet), and I can never remember that.
On Mon, Apr 13, 2020 at 10:48 PM Tim via users users@lists.fedoraproject.org wrote:
On Tue, 2020-04-14 at 00:26 +0200, Tom H wrote:
The improvement's when you have a multiple NICs and swap one out. You no longer have to edit "/etc/udev/rules.d/<something>.rules" in order to have the swapped-in NIC keep the name of the swapped-out NIC.
My understanding of how the device names were generated was that if you didn't replace a NIC with an identical model, in the exact same spot, you could well end up with a different device name.
If the PCI bus setup does not change the location and naming does not change.
On some cards there is a extra pci piece of hw that changes the final numbering usually because one 4pt card is directly attached to the pci bus but the other 4pt card is really 2 - 2pt cards sitting on a piece of hw that allows that to happen. Once a given node was installed it was very very rare to change the card setup, we accepted that.
And we only have one model of nic card per model of actual machine, so we replace with identical 99% of the time, and when we don't we move to the defined udev rule for the new config (new udev rule when dissimilar hardware models were use on 5/6 to force the mapping to work, just renamed ifcfg- names and device= on 7 based on a mapping table that we had).
There was an order of how to name things, starting at the top, going down the list if that scheme wasn't do-able:
Firmware or BIOS can form the device name.
That seems to be pretty inconsistent even with the server vendors I have dealt with, and generally it completely goes out the window with any pci add-in cards. With the desktop vendors and/or vmware it seems to not exist. The 7 naming scheme says using bios name first then move to the pci bus naming, so yours having an odd names means your bios did set it.
Board location can form the name (derived from things like PCI slot 2).
Number of connectors on the board can be used in forming the name (adding more details to the above naming scheme).
Heck knows what mine's derived from (enp0s31f6 is the motherboard's own built in ethernet), and I can never remember that.
On Sun, Apr 12, 2020 Roberto Ragusa mail@robertoragusa.it wrote:
On 2020-04-10 20:53, Jack Craig wrote:
on F30, i would like to swap enp4s0 to eth0.
outside the network ifcfg* files, any other place(file) to update?
Having a proper ifcfg*, including the HWADDR MAC address used to be enough (but be sure you rebuild your initrd since renaming happens there).
https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-Und...
Is that not working anymore?
AFAIK, you can't rename NICs via /etc/sysconfig/network-scripts/ifcfg-*" any longer. If you use nmcli, you can set "NAME=name" to refer to "name" in the commands.
Using "net.ifnames=0" at the kernel cmdline is the simplest solution.
But there are other methods:
1) You can rename NICs, NOT_TO "ethX", via
/etc/udev/rules.d/*.rules
or
/etc/systemd/network/*.link
2) You can keep "ethX" via
/etc/systemd/network/99-default.link
in which you set
NamePolicy=kernel
instead of
NamePolicy=keep kernel database onboard slot path
as in
/usr/lib/systemd/network/99-default.link
3) You can keep "ethX" via an empty
/etc/udev/rules.d/80-net-setup-link.rules
but this file was called something else ("80-net-name-slot.rules"?) previously, so...
Messing with grub kernel options looks definitely overkill.
Why? It's just one file edit.
-
Frank Elsner -
Ian Chapman -
Jack Craig -
Joe Zeff -
Roberto Ragusa -
Roger Heflin -
Tim -
Tom H -
Tom Horsley