cfg80211_not...er_candidate(9)

📦 version 7.3.1, in nixpkgs unstable

✨ cfg80211_notify_new_peer_candidate(9) ✨

okay so bestie, we're diving into the kernel API manual for cfg80211_notify_new_peer_candidate and honestly? this one's a lil gem 💎 it's giving "mesh networking but make it a group chat" energy, and i'm obsessed. buckle up, we're doing this together 🫶

🎀 NAME 🎀

cfg80211_notify_new_peer_candidate — the function that slides into cfg80211's DMs to say "hey girl, we found a new mesh peer candidate" 💅

🌸 SYNOPSIS 🌸

void cfg80211_notify_new_peer_candidate(struct net_device *dev,
                                        const u8 *macaddr,
                                        const u8 *ie,
                                        size_t ie_len,
                                        int sig_dbm,
                                        gfp_t gfp);

like, look at all those parameters. main character energy fr fr 🔥

🦋 ARGUMENTS 🦋

okay so every single one of these matters, no skipping, we're not doing that 🙈

  • dev — the network device. you know, the actual interface doing the thing 💖
  • macaddr — the MAC address of the new candidate. this is who we're talking about, their little hardware identity 🎀
  • ie — the information elements advertised by the peer candidate. like their profile bio, but for 802.11 📝
  • ie_len — length of the information elements buffer. gotta tell us how much bio to read, bestie 📏
  • sig_dbm — signal level in dBm. how loud they're coming through, basically 📶
  • gfp — allocation flags. the usual kernel memory-allocation vibe check ✨

💜 DESCRIPTION 💜

so what does this function actually do? it notifies cfg80211 that the mesh peer candidate has been detected 👀 and the way it usually happens is — most likely — via a beacon 🌈 or, less likely, via a probe response. either way, we caught 'em.

then cfg80211 takes that info and sends a notification to userspace. so it's basically the messenger 🧚 passing the tea along to the people who need it. periodt.

more parts coming, bestie — don't go anywhere 💅✨

✨ SEE ALSO ✨

okay bestie, this is the part where the man page just name-drops the entire extended universe. The kernel file is ./include/net/cfg80211.h, and the cross-refs start right here. no skips, no cap. 💅

Okay bestie, the see-also list is still going — like the manpage said "one more thing" and then kept talking for another 60 entries 😭 but honestly? every single one of these is iconic in its own way. grab a snack, we're finishing the bibliography. 🍓

the regulatory trio 🌸

channel switch announcements, both the "we're doing it" and the "we did it" 💅

the conversion girlies ✨ operating class in, band out, chandef in, kHz out — glow-ups in every direction.

registration and its inevitable reverse 🎀

the struct and the function that loves it, fr fr.

information-element girlies, splitting and fragmenting like it's nothing 🔥

channel-math besties, no cap 🧮✨

the "ok we're done here" trilogy 💀 (the last one is very main character energy, just saying)

set it, check it, iconic duo 🫶

the NAN squad, part one 🌈

the whole color-change notification family 🎨 started, aborted, done — they covered every plot twist.

MLO reconf content, extremely 2026 of them 💜

the NAN squad, part two — they really said "and another thing" 🦋

debugfs read/write, locked and loaded 🔒

S1G trio, start / end / primary sibling, all in kHz, all iconic ⭐

and the finale 🎬 slay.

and that's the whole list, bestie — we ate, we left no crumbs, and we did not skip a single reference 😤👑

sign-off time 🎀 this page lives under the source path ./include/net, it's dated October 2026, and the version line reads cfg80211_not...er_candidate(9) — so if you ever need to cite it in the group chat, now you know exactly what to say 🫶✨

📦 where this page comes from