e1000_set_rx_mode(9)

📦 version 7.3.1, in nixpkgs unstable

💅 e1000_set_rx_mode — the e1000 glow-up for your RX filters

okay so real talk, this is a page out of the Kernel API Manual (section 9, driver-functions territory), and bestie it's lowkey iconic. It's the vibes manual for e1000_set_rx_mode(9), and it's short but it carries. Sit down, hydrate, let's go 🫶

✨ NAME ✨

e1000_set_rx_mode — Secondary Unicast, Multicast and Promiscuous mode set 🎀

(Note the word "Secondary" up there — that's the function's whole name, not me being dramatic. Okay maybe a little me being dramatic.)

🦋 SYNOPSIS 🦋

void e1000_set_rx_mode (struct net_device *netdev );

That's it. That's the whole signature. One function, one argument, returns nothing, no notes. It's giving minimalist main character energy 🌸

💖 ARGUMENTS 💖

  • netdev — the network interface device structure. Yes, the struct. The whole interface's little ID card and diary combined. It's the network device you're doing all this for 💜

👑 DESCRIPTION 👑

So here's the tea ☕ — set_rx_mode is the entry point that gets called whenever:

  • the unicast address list gets updated, or
  • the multicast address list gets updated, or
  • the network interface flags get updated.

That's the whole trigger squad, no cap. Any one of those three updates and this function gets the call 🙈

And what does it do with this moment in the spotlight? It's responsible for configuring the hardware so the NIC actually knows how to behave for:

  • proper unicast 🌈
  • multicast 🍓
  • promiscuous mode (yeah, that one 🔥)
  • and all-multi behavior ⭐

Basically: whenever the address lists or the flags change, this routine is the one that goes and tells the hardware "bestie, here's the new plan," so the card filters packets the way the kernel intends. The lists changed, the flags changed, the vibe changed — and e1000_set_rx_mode is the one who actually updates the hardware about it. Slay 💅

fr fr though — the whole point is the hardware gets configured here. It's not just bookkeeping, it's the actual "go tell the chip" step.

🧚 SEE ALSO 🧚

Here's the squad — the whole friend group all lives in one very long file, and honestly, spending time with all of them:

Kernel file 📁

./drivers/net/ethernet/intel/e1000/e1000_main.c

The friends 🫶 (every single one of them, bestie, no skipping — I said what I said):

Like. Fifty-something cross-references. This driver has more friends than me and I'm literally the one writing this. Respect it 😭

🎀 And that's the whole page, babe. Short, sweet, and every single cross-reference accounted for — not me counting them twice to make sure. Okay maybe me counting them twice. 💀

<x-purple>Sign-off time 🌟 — this little beauty comes to you from the file path that got tragically cropped at ./drivers/net/ethernet/intel/e..., dated October 2026, and it's living its best life as e1000_set_rx_mode(9) in the Kernel API Manual.</x-purple> Go configure that hardware, bestie. iykyk 💜

📦 where this page comes from