ieee80211_connection_loss(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to ieee80211_connection_loss(9) from the Kernel API Manual β€” this is the page where the hardware has to fess up that it lost the AP πŸ˜­πŸ’”. No cap, it's short but important.

πŸ’– NAME πŸ’–

ieee80211_connection_loss β€” inform hardware has lost connection to the AP. That's the whole plot: the driver tells mac80211 the AP link is gone. 🫢

✨ SYNOPSIS ✨

void ieee80211_connection_loss (struct ieee80211_vif *vif );

πŸŽ€ ARGUMENTS πŸŽ€

  • vif β€” a struct ieee80211_vif pointer from the add_interface callback. That's the one you pass in, bestie πŸ’…

🌸 DESCRIPTION 🌸

okay so here's the vibe check: when beacon filtering is enabled with IEEE80211_VIF_BEACON_FILTER, and IEEE80211_CONF_PS and IEEE80211_HW_CONNECTION_MONITOR are set, the driver needs to inform if the connection to the AP has been lost. That's literally the job. ✨

The function may also be called if the connection needs to be terminated for some other reason, even if IEEE80211_HW_CONNECTION_MONITOR isn't set. So yeah, it's not only for the beacon-filtering setup β€” sometimes you just gotta end it, iykyk πŸ¦‹

⚠️ Heads up: this function will cause immediate change to disassociated state, without connection recovery attempts. It's giving clean break, no trying to text the AP back 😭 no cap.

πŸ‘‘ SEE ALSO πŸ‘‘

okay this section is a whole festival lineup β€” every single one is invited, no cap. πŸ’œ


source/version: ./include/net; date: October 2026 β€” that's the footer tea, and this was ieee80211_connection_loss(9), mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from