ieee80211_nullfunc_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to ieee80211_nullfunc_get(9) from the Kernel API Manual β€” the page about retrieving a nullfunc template. It’s giving kernel Wi-Fi internals with a cute little bow on top. πŸŽ€βœ¨

🌸 NAME 🌸

ieee80211_nullfunc_get β€” retrieve a nullfunc template.

✨ SYNOPSIS ✨

struct sk_buff * ieee80211_nullfunc_get (struct ieee80211_hw *hw ,
struct ieee80211_vif *vif , int link_id , bool qos_ok );

πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” a pointer you got from ieee80211_alloc_hw. That’s the source, bestie.
  • vif β€” a struct ieee80211_vif pointer from the add_interface callback.
  • link_id β€” if the vif is an MLD, this gets a frame with the link addresses for the given link ID. For a link_id < 0 you get a frame with MLD addresses, however useful that might be β€” yes, that’s the original’s own little dry joke, keep it.
  • qos_ok β€” QoS NDP is acceptable to the caller, and this should be set if at all possible. fr fr, set it if you can.

πŸ¦‹ DESCRIPTION πŸ¦‹

Creates a Nullfunc template which can, for example, be uploaded to hardware. The template must be updated after association so that the correct BSSID and address is used.

If qos_ndp is set and the association is to an AP with QoS/WMM, the returned packet will be QoS NDP. Heads up: the original text says qos_ndp right here, so I’m keeping that spelling exactly β€” no β€œfixing” the lore.

πŸ’… NOTE πŸ’…

Caller (or hardware) is responsible for setting the IEEE80211_FCTL_PM bit as well as Duration and Sequence Control fields. Not me, not you, not the vibe β€” caller or hardware.

πŸ‘‘ RETURN πŸ‘‘

The nullfunc template. NULL on error.

🌈 SEE ALSO 🌈

bestie, the SEE ALSO list is huge and I’m not skipping a single one:

mwah πŸ’‹ β€” this page is from the ./include/net source, dated October 2026, and it’s serving ieee80211_nullfunc_get(9) energy. Bye bestie! 🫢🌈

πŸ“¦ where this page comes from