regulatory_hint_disconnect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regulatory_hint_disconnect(9) β€” the Kernel API Manual, bestie edition

Okay so this is a page from the Kernel API Manual about regulatory_hint_disconnect β€” yes it's a mouthful, no you don't have to say it out loud at a party. It's giving "quietly important helper function" and honestly? Iconic. Let's get into it 🫢


✨ NAME ✨

regulatory_hint_disconnect β€” the function that informs all devices have been disconnected (yes, that's the whole vibe: it's the "everyone's gone, time to reset" signal) πŸ’€


🌸 SYNOPSIS 🌸

void regulatory_hint_disconnect (void );

πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. Zero. None. Not a single one. She takes nothing and she gives everything ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea πŸ“ β€” regulatory rules can be enhanced even further upon scanning and upon connection to an AP. Cute, right? But those rules become stale if we disconnect and go to another country, whether or not we suspend and resume. Like, the rules are still wearing last season's fit. Not slay.

And if we do suspend, go to another country, and resume? We'll automatically get disconnected shortly after resuming, and things will be reset as well. So it kinda handles itself, but not fully, iykyk.

This routine is a helper to restore regulatory settings to how they were prior to our first connect attempt. That's the whole job, and she does it well πŸ‘‘

This includes ignoring country IE and beacon regulatory hints. Very "not me ignoring the red flags" energy, except here it's literal and correct and good.

The ieee80211_regdom module parameter will always be respected β€” no cap, that one's non-negotiable. But if a user had set the regulatory domain, that will take precedence πŸ’… (user wins, always).

⚠️ Real talk though: this must be called from process context. Not interrupt context, not "wherever, it'll be fine" context. Process context. Periodt.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./net/wireless/reg.h β€” and the whole friend group:


Anyways bestie, that's the page πŸ’– huge shoutout to ./net/wireless for hosting this whole situation, and to October 2026 for being the date on the tin. Go forth and disconnect responsibly 🌈🧚

πŸ“¦ where this page comes from