If you're using a static or manual configuration for your networking, you're going to want to learn about the changes that have been implemented affecting your configuration.
https://wiki.debian.org/NetworkInterfaceNames
https://wiki.debian.org/NetworkConfiguration
O.O look at this I totally forgot this was possible...
https://wiki.debian.org/NetworkInterfaceNames
https://wiki.debian.org/NetworkConfiguration
O.O look at this I totally forgot this was possible...
THE ORIGINAL SIMPLE SCHEME
Back in the nineties, eth0, eth1, etc were simply assigned by the kernel.
Why it was abandoned
At least in theory, if module probes completed in a different order, eth0 and eth1 might switch places on successive boots. As boot processes became less linear and interfaces became more hotpluggable this became more of a concern.
How to get it back
If you wipe out all other name-assignment mechanisms then you'll be left with this one.
The simple way of disabling the whole current interface naming scheme (which you might want to try for one-off testing) is just to boot with the kernel parameter net.ifnames=0, which can be set in an interactive grub session at boot or made persistent by editing /etc/default/grub and running update-grub.
Statistics: Posted by Linuxgaming1824 — 2024-04-18 13:56