Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

Props to Alpine and Kali for disabling this bullshit out of the box

Context for newbies: Linux refers to network adapters (wifi cards, ethernet cards, etc.) by so called "interfaces". For the longest time, the interface names were assigned based on the type of device and the order in which the system discovered it. So, eth0, eth1, wlan0, and wwan0 are all possible interface names. This, however, can be an issue: "the order in which the system discovered it" is not deterministic, which means hardware can switch interface names across reboots. This can be a real issue for things like servers that rely on interface names staying the same.

The solution to this issue is to assign custom names based on MAC address. The MAC address is hardcoded into the network adaptor, and will not change. (There are other ways to do this as well, such as setting udev rules).

Redhat, however, found this solution too simple and instead devised their own scheme for assigning network interface names. It fails at solving the problem it was created to solve while making it much harder to type and remember interface names.

To disable predictable interface naming and switch back to the old scheme, add net.ifnames=0 and biosdevname=0 to your boot paramets.

The template for this meme is called "stop doing math".

mlg ,
@mlg@lemmy.world avatar

me setting my interface into monitor mode manually because it can't handle being split into mon and managed.

Fades ,

life-long Kali fan

neclimdul ,

I really appreciate this change. Prior to it was always a struggle to deploy servers successfully. You'd reboot and your database would be on the wrong interface and you could even remote in because the management interface was suddenly on a firewalled external only network. Ask me how I know.

With virtualization and containers this just got more complicated. I would constantly have to rewrite kvm entire configs because I'd drop a new nic in the machine. A nightmare.

Sure, it's gibberish for the desktop user but you can just use the UI and ignore the internal name. Not even sure the last time I saw it on my laptop. So no big deal.

fruitycoder ,

No idea what mactab is, but maybe it solves it for me, but being able to go from interface name back to a rack full of heterogeneous PCI cards and go "yep it should be this port" was a wildly useful feature.

I feel like there should be automatic alias creation for simply interface names though.

jadedwench ,

I had to change mine to mac address naming on my proxmox server after the second time the name changed due to a GPU or SSD being added. It was kind of like, so what, if an SSD dies suddenly or I have some issue with a device you are going to rename my fucking nic card again while I am trying to troubleshoot? Absolutely deranged.

NutWrench ,
@NutWrench@lemmy.world avatar

Also, make sure your password contains L's, 1's, 0's and O's in a font deliberately chosen to make them hard to tell apart.

interdimensionalmeme ,

Wlan1? how would you bridge different channels with only wlan0?

NegativeLookBehind ,
@NegativeLookBehind@lemmy.world avatar

eth0? No no, we need wlps0n1pn2d4es6vsd9c69420

maxinstuff ,
@maxinstuff@lemmy.world avatar

Here I am on a laptop with no ethernet ports (probably works over USB-C? No idea, haven't tried), and a single wifi adapter. Guess I'll give it a try:

ip link show

What I expected

wlan0

What I got

wlp242s0

Neat 👍 😎 👍

derpgon ,

enp2s0, wlp3s0, and my fav enp4s0f3u1u3

suction ,

Small world thinking. Because you haven't seen the need for it doesn't mean it doesn't exist. Also, did you lose your CTRL, C, and V keys?

laurelraven ,

Yes, because everyone has need of this solution, and wants to have to copy and paste interface names every time they need to touch them, rather than having deterministic naming be an option to enable for those who actually need it...

suction ,

You know Linux isn’t just used by nerdy kids cosplaying as Mr Robot, right?

laurelraven ,

You know Linux isn't just used by enterprise sysadmins, right?

And even speaking as an enterprise sysadmin myself, I've not had need or use for deterministic interface naming once in my career. I have no clue how common that is, but most of the servers, both physical and virtual, that I've worked on only had one Ethernet port connected.

I see the purpose of this, but don't see a reason why it should be the default, or why it couldn't have been implemented like HHD/SSD UUIDs where the old dev names were left intact for easy use outside of fstab and the like where consistency could become a problem

ETA: you also seemed to miss the part of my initial reply to you about it being something that can be enabled by those who need it... And if you're going to say that the enterprise professionals who need it shouldn't have to turn it on every time they spin up a system, I'll remind you that enterprise admins working at that level where they're setting up enough servers for that to be a hassle are probably using orchestration like Ansible, Chef, or Puppet, and can just add that into their configs once

suction ,

TLDR

laurelraven ,

And I don't care, so whatever

NaoPb ,

I actually prefer the eth0 and wlan0.

caden ,

That's what the meme is saying too

Laser ,

Is it though? Normally it's ironic: https://knowyourmeme.com/memes/stop-doing-math

jagungal ,

This time it isn't (I think)

MacNCheezus ,
@MacNCheezus@lemmy.today avatar

For regular PCs or laptops, which generally have at most one of each type of adapter, I don't see any reason not to.

d00phy ,

So I do HPC installations, and using Mellanox/NVIDIA adapters in Ethernet mode absolutely sucks. First, when you initially install them, they’re named something like ens2f0, where “2” generally corresponds to the PCI slot. Pretty easy, until you install MOFED. Yeah, I know you don’t need MOFED, but the drivers included in RHEL are waaay old. Anyway, after installing the newer drivers, that exact same interface becomes ens2f0np0!

What’s even better is there’s no guarantee that a PCI Ethernet card in PCI slot 2 will be “ens2…” which I would argue is predictive!

MonkderDritte ,

Kernel parameters? This is a udev thing, just change the udev rule.

Allero ,

Love the explainer to the meme.

Keep up the good work!

renzev OP ,

Thanks! Memes as education material / propaganda FTW

DogWater ,

I was going to commend you as well. Top notch. I appreciate it

Murdoc ,

I came here to say this. I don't really do networking so I don't have much care for this issue, but the clarity of the explanation was enjoyable. Plus I learned a couple of little things too.

bitwaba ,

"the order in which the system discovered it" is not deterministic

This is the same problem they had with hard drive names and it seems to have been solved in a sensible way, i.e. /dev/sda still points to the first disk detected by the system, but you can look look in /dev/disk/by-path (or by-uuid, etc) to see the physical address of the devices on the system and what they are symlinked back to, and set your fstab or mdadm arrays to be configured based on those unique identifiers instead.

So, I guess what I'd like to know is why hasn't this been solved the same way? When you boot up they should present every hard wired Ethernet port as ethX, and the hardware address interface should be present as well but aliased back to the eth. Then you can build the your network configs based on either one.

Shouldn't be that hard right?

nekusoul ,
@nekusoul@lemmy.nekusoul.de avatar

Cries in nvme1n1p6, which is my current OS partition.

partizan ,

Taking a sip of Rum and chuckles at the look on the name of my OS partition: /dev/mapper/vg-root and /dev/mapper/vg-home 🙃

phx ,

That's because you're using LVM though.
In most distros you could also use something like:

/dev/vg/root

jj4211 ,

And at least in some distributions, they do exactly that, a number of aliases for the same interface. And you can add your own.

lemmyvore ,

But nobody uses /dev/sdX anymore (not after they wipe the wrong disk once anyway). They either use logical UUIDs or hardware WWN/serial.

renzev OP ,

idk man I use /dev/sdX when running commands interactively and PARTLABELs in my /etc/fstab. All those letters and numbers in UUIDs are too much for my monkey brain to handle lol

bitwaba , (edited )

Yeah, the point is "you can use either one", instead of "we made the choice for you"

thisisnotgoingwell , (edited )

As a data center engineer of 10+ years, I struggled to understand this at first. In my world, the hardware does a POST before the OS boots and has an inventory of what hardware components are available, so it shouldn't matter in what order they are discovered, since the interface names should make a correlation between the interface and the pcie slot that NIC exists in.

Where the water gets muddled is in virtualized servers. The NICs no longer have a correlation to a specific hardware component, and you may need to configure different interfaces in the virtualized OS for different networks. I think in trying to create a methodology that is agnostic to bare metal/virtualized OSs, it was decided that the naming convention should be uniform.

Probably seems like bloat to the average admin who is unconcerned with whether these NICs are physical or virtual, they just want to configure their server.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • linuxmemes@lemmy.world
  • random
  • incremental_games
  • meta
  • All magazines
    •