894

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".

top 50 comments
sorted by: hot top controversial new old
[-] mlg@lemmy.world 1 points 1 hour ago

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

[-] blackstrat@lemmy.fwgx.uk 28 points 2 days ago

As someone who worked on a pre-systemd linux system with multiple NICs and needed them all configured automatically from an OS image based on where it was in the rack, I can't stress enough how good deterministic interface names are.

Booting up a system and each time having different names for each NIC was a nightmare.

Frankly 90+% of what systemd has done is tremendously positive and makes linux a better operating system to use, both for sys admins and end users.

[-] laurelraven@lemmy.blahaj.zone 3 points 2 days ago

Couldn't they be configured to always set each interface to a particular name? I'd think that would be the better solution anyway...

[-] NegativeLookBehind@lemmy.world 26 points 2 days ago

eth0? No no, we need wlps0n1pn2d4es6vsd9c69420

[-] neclimdul@lemmy.world 9 points 2 days ago

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.

[-] maxinstuff@lemmy.world 18 points 2 days ago* (last edited 2 days ago)

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@programming.dev 9 points 2 days ago

enp2s0, wlp3s0, and my fav enp4s0f3u1u3

[-] NutWrench@lemmy.world 10 points 2 days ago

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.

[-] Allero 83 points 3 days ago

Love the explainer to the meme.

Keep up the good work!

[-] renzev@lemmy.world 26 points 3 days ago

Thanks! Memes as education material / propaganda FTW

load more comments (1 replies)
load more comments (1 replies)
[-] fossphi@lemm.ee 121 points 3 days ago

Good lord, this is a top tier meme!

[-] renzev@lemmy.world 65 points 3 days ago

Thanks, glad you like it! I spent quite some time re-making the template from scratch in inkscape, because the original meme din't have enough space for the text

[-] fossphi@lemm.ee 34 points 3 days ago

Heck yeah, vectorised libre memes ftw!

load more comments (2 replies)
[-] orwellianlocksmith@lemmy.world 94 points 3 days ago

I have no idea at all of what this is about but I feel strongly that OP is right and we must urgently fix this disgusting problem we are facing with the interfaces. Get em, OP, get the bastards. Solidarity

[-] Simon@lemmy.dbzer0.com 51 points 3 days ago* (last edited 3 days ago)

Having no idea what this is about and being on a Linux meme subreddit is absolutely peak Lemmy.

load more comments (3 replies)
[-] NaoPb@eviltoast.org 30 points 3 days ago

I actually prefer the eth0 and wlan0.

[-] caden@lemmy.sdf.org 22 points 3 days ago

That's what the meme is saying too

[-] Laser@feddit.org 8 points 2 days ago
[-] jagungal@lemmy.world 6 points 2 days ago

This time it isn't (I think)

[-] MacNCheezus 3 points 2 days ago

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

[-] jadedwench@lemmy.world 7 points 2 days ago

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.

[-] notabot@lemm.ee 73 points 3 days ago

It's amazing how many linux problems stem from 'Redhat, however, found this solution too simple and instead devised their own scheme'. Just about every over complex, bloated bit of nonsense we have to fight with has the same genesis.

[-] renzev@lemmy.world 28 points 3 days ago

What I really don't understand is why distro maintainers feel the need to actually go along with these changes. Like, sure, if this predictable interface naming thing worked as intended, I can definitely see how it can be useful for server administrators. You could just hardcode the automatic interface names instead of assigning them manually in /etc/mactab. But why would the rest of us ever need this? Most personal machines have at most one wifi card and one ethernet device, so wlan0 and eth0 are perfectly predictable. And even if you have multiple wifi or ethernet adapters, your networking is probably handled by network-manager, so you never actually have to put interface names into config files. Why force enterprise-grade bloat on users who just want a simple desktop experience?

load more comments (16 replies)
[-] Count042@lemmy.ml 22 points 3 days ago

It's amazing how many of those started with Lennart, too.

[-] notabot@lemm.ee 15 points 3 days ago

He's definitely off my Christmas card list. He seems desperate to leave a legacy, but he keeps trying to turn Linux into windows instead.

load more comments (7 replies)
load more comments (26 replies)
[-] cheddar@programming.dev 41 points 3 days ago

I laughed so hard. Then I cried remembering good old days of eth0.

load more comments (2 replies)
[-] ace@lemmy.ananace.dev 46 points 3 days ago

The predictable interface naming has solved a few issues at work, mainly in regards to when we have to work with expensive piece-of-shit (enterprise) systems, since they sometimes explode if your server changes interface names.
Normally wouldn't be an issue, but a bunch of our hardware - multiple vendors and all - initialize the onboard NIC pretty late, which causes them to switch position almost every other boot.

I've personally stopped caring about interface names nowadays though, I just use automation to shove NetworkManager onto the machine and use it to get a properly managed connection instead, so it can deal with all the stupid things that the hardware does.

load more comments (4 replies)
[-] bitwaba@lemmy.world 29 points 3 days ago

"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@lemmy.nekusoul.de 22 points 3 days ago

Cries in nvme1n1p6, which is my current OS partition.

load more comments (2 replies)
[-] thisisnotgoingwell@programming.dev 6 points 2 days ago* (last edited 2 days ago)

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.

load more comments (4 replies)
[-] Fades@lemmy.world 2 points 2 days ago

life-long Kali fan

[-] cypherpunks@lemmy.ml 30 points 3 days ago

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

I somehow first read "Redhat" as "Reddit" in this sentence, and so was briefly thinking that perhaps this bad idea originated there ๐Ÿ˜‚

[-] renzev@lemmy.world 38 points 3 days ago

"reddit makes a linux distro" would be hilarious and terrifying

[-] ouRKaoS 25 points 3 days ago

I'm getting "Twitch plays Pokemon" vibes...

load more comments (4 replies)
[-] apfelwoiSchoppen@lemmy.world 26 points 3 days ago

I miss seeing this meme format on Lemmy. It's so good, and this one is no exception.

[-] renzev@lemmy.world 31 points 3 days ago

Thanks! I love this format so much. I can't find it now, but one of my favourite memes in this genre was something like this:

STOP DOING

  • Tasks were never meant to be completed
  • Years of working, but there's STILL MORE SHIT TO DO
  • Wanted to get some work done anyway, for a laugh? We had a tool for that: it was called SIMULATION GAMES
  • "Please let me sacrifice a third of my life to justify my existence. Please let me spend eight hours a day working just to be able to do it again the next day" - statements dreamt up by the utterly deranged

Look at what people have been demanding our respect for all this time, with all the schedules and todo lists we have built for them:

These are REAL things done by REAL people

<Pictures of gmail, microsoft outlook, and some TODO list app>

They have played us for absolute fools

load more comments (1 replies)
[-] MonkderDritte@feddit.de 13 points 3 days ago

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

load more comments
view more: next โ€บ
this post was submitted on 27 Jun 2024
894 points (96.5% liked)

linuxmemes

19676 readers
73 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS