cfg80211_reg_can_beacon(9)

📦 version 7.3.1, in nixpkgs unstable

✨ cfg80211_reg_can_beacon(9) ✨

ok so bestie, welcome to cfg80211_reg_can_beacon — she's from the Kernel API Manual (section 9, iykyk) and she's literally here to answer one iconic question: can we beacon here or not? 🎀

🌸 NAME 🌸

cfg80211_reg_can_beacon — check if beaconing is allowed 💅

🦋 SYNOPSIS 🦋

bool cfg80211_reg_can_beacon (struct wiphy *wiphy , struct
       cfg80211_chan_def *chandef , enum nl80211_iftype iftype );

like... she takes three things and gives you back a bool. simple queen behavior, no cap. 👑

💖 ARGUMENTS 💖

  • wiphy — the wiphy 🧚 (yes that's the whole description, she's mysterious like that)
  • chandef — the channel definition, aka the whole vibe of the channel you're asking about ✨
  • iftype — interface type, the enum nl80211_iftype situation 🌈

⭐ RETURN ⭐

Returns true if there is no secondary channel — or if the secondary channel(s) can actually be used for beaconing. 🎀 (read: it's not a radar channel etc. etc., so you're lowkey good to go 🫶)

fr fr, if you get true back it means no secondary channel exists at all, OR the secondary channel(s) passed the vibe check and aren't stuff like radar channels. that's the whole deal 💀

ok that's part 1 bestie, stay tuned, there's more 👀💜

✨ SEE ALSO ✨

okay bestie, this is the whole extended friend group 💖 grab a lil snack, because every single cross-reference is about to walk in looking iconic. no skips, no cuts, we're naming everyone. periodt.

And that's a wrap, bestie 🎀✨ This lil' beauty lives over in ./include/net and it's dated October 2026 — so future vibes, current knowledge, no cap 💅🦋 Go forth and beacon responsibly 🫶💖

📦 where this page comes from