ENUM MONITOR_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ enum monitor_flags(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual entry for enum monitor_flags β€” it's giving tiny enum, very specific monitor-interface business. πŸ’…βœ¨


🌸 NAME 🌸

enum monitor_flags β€” monitor flags. periodt.

✨ SYNOPSIS ✨

enum monitor_flags {
    MONITOR_FLAG_CHANGED ,
    MONITOR_FLAG_FCSFAIL ,
    MONITOR_FLAG_PLCPFAIL ,
    MONITOR_FLAG_CONTROL ,
    MONITOR_FLAG_OTHER_BSS ,
    MONITOR_FLAG_COOK_FRAMES ,
    MONITOR_FLAG_ACTIVE ,
    MONITOR_FLAG_SKIP_TX

};

🧩 Constants 🧩

  • MONITOR_FLAG_CHANGED β€” set if the flags were changed. like, the little β€œbestie, the flags moved” signal. βœ…
  • MONITOR_FLAG_FCSFAIL β€” pass frames with bad FCS. yes, even the messy ones. 🫢
  • MONITOR_FLAG_PLCPFAIL β€” pass frames with bad PLCP. letting the questionable ones through too. πŸ’«
  • MONITOR_FLAG_CONTROL β€” pass control frames. control-frame girlies, this one's for you. πŸŽ€
  • MONITOR_FLAG_OTHER_BSS β€” disable BSSID filtering. no BSSID gatekeeping here. πŸšͺ✨
  • MONITOR_FLAG_COOK_FRAMES β€” deprecated, will unconditionally be refused. not a slay, do not rely on it, bestie. πŸ’€
  • MONITOR_FLAG_ACTIVE β€” active monitor, ACKs frames on its MAC address. main character energy: it ACKs frames on its MAC address. πŸ‘‘
  • MONITOR_FLAG_SKIP_TX β€” do not pass locally transmitted frames. local TX? skipped. 🫑

πŸ¦‹ Description πŸ¦‹

Monitor interface configuration flags. Note that these must be the bits according to the nl80211 flags β€” no mixing up the bit vibes, iykyk. 🌈

🌈 SEE ALSO 🌈

okay so this is the part where the page is basically like "and here is literally everyone else" and honestly? it ate. πŸ’… the whole thing hangs off one file β€” Kernel file ./include/net/cfg80211.h β€” and then it just starts naming names. grab a snack, bestie, this list is long.

first up, the starter pack: Introduction(9), Device registration(9), then the channel-and-rate girlies β€” enum ieee80211_channel_flags(9), struct ieee80211_channel(9), enum ieee80211_rate_flags(9), enum ieee80211_bss_type(9), enum ieee80211_privacy(9), struct ieee80211_rate(9), struct ieee80211_he_obss_pd(9), struct cfg80211_he_bss_color(9), struct ieee80211_sta_ht_cap(9), struct ieee80211_sta_vht_cap(9), struct ieee80211_sta_he_cap(9), struct ieee80211_eht_mcs_nss_supp(9), struct ieee80211_sta_eht_cap(9), struct ieee80211_sta_uhr_cap(9). πŸ¦‹

then the band-capability squad: struct ieee80211_sband_iftype_data(9), enum ieee80211_edmg_bw_config(9), struct ieee80211_edmg(9), struct ieee80211_sta_s1g_cap(9), struct ieee80211_supported_band(9), _ieee80211_set_sband_iftype_data(9), ieee80211_set_sband_iftype_data(9), for_each_sband_iftype_data(9), ieee80211_get_sband_iftype_data(9), ieee80211_get_he_iftype_cap(9), ieee80211_get_he_6ghz_capa(9), ieee80211_get_eht_iftype_cap(9), ieee80211_get_uhr_iftype_cap(9), and wiphy_read_of_freq_limits(9). note the lowercase _ieee80211_set_sband_iftype_data(9) sitting right there next to its public sibling β€” they're twins, one's just shy. 🫢


Actions and configuration(9) β€” this is the big one, main character energy fr. struct vif_params(9), struct key_params(9), struct cfg80211_chan_def(9), struct cfg80211_tid_cfg(9), struct cfg80211_tid_config(9), struct cfg80211_fils_aad(9), struct cfg80211_set_hw_timestamp(9), cfg80211_get_chandef_type(9), cfg80211_chandef_create(9), cfg80211_chandef_identical(9), cfg80211_chandef_is_edmg(9), cfg80211_chandef_is_s1g(9), cfg80211_chandef_compatible(9), nl80211_chan_width_to_mhz(9), cfg80211_chandef_get_width(9), cfg80211_chandef_valid(9), cfg80211_chandef_usable(9), cfg80211_chandef_dfs_required(9), cfg80211_chandef_dfs_usable(9), cfg80211_chandef_dfs_cac_time(9), cfg80211_chandef_primary(9), cfg80211_chandef_npca_valid(9), cfg80211_chandef_add_npca(9), cfg80211_chandef_add_dbe(9), nl80211_send_chandef(9), ieee80211_chandef_max_power(9), cfg80211_chandef_s1g_pri_width(9), cfg80211_any_usable_channels(9). that's a whole lot of chandef and every single one of them is doing its own little job ✨

still riding the config wave: enum survey_info_flags(9), struct survey_info(9), struct cfg80211_crypto_settings(9), struct cfg80211_mbssid_config(9), struct cfg80211_mbssid_elems(9), struct cfg80211_rnr_elems(9), struct cfg80211_beacon_data(9), struct cfg80211_acl_data(9), struct cfg80211_fils_discovery(9), struct cfg80211_unsol_bcast_probe_resp(9), struct cfg80211_s1g_short_beacon(9), struct cfg80211_ap_settings(9), struct cfg80211_ap_update(9), struct cfg80211_csa_settings(9), struct cfg80211_color_change_settings(9), struct iface_combination_params(9). beacon era πŸŽ€

then the station files, lowkey my fave section because look at this lineup: enum station_parameters_apply_mask(9), struct sta_txpwr(9), struct link_station_parameters(9), struct link_station_del_parameters(9), struct cfg80211_ttlm_params(9), struct station_parameters(9), struct station_del_parameters(9), enum cfg80211_station_type(9), cfg80211_check_station_change(9), enum rate_info_flags(9), enum rate_info_bw(9), struct rate_info(9), enum bss_param_flags(9), struct sta_bss_parameters(9), struct cfg80211_txq_stats(9), struct cfg80211_tid_stats(9), struct link_station_info(9), struct station_info(9). the way station_parameters(9) and station_del_parameters(9) are just sitting there being opposites 😭

and to close out this whole config era: struct cfg80211_sar_sub_specs(9), struct cfg80211_sar_specs(9), struct cfg80211_sar_freq_ranges(9), struct cfg80211_sar_capa(9), cfg80211_get_station(9), enum mpath_info_flags(9), struct mpath_info(9), enum wiphy_bss_param_flags(9), struct bss_parameters(9), struct mesh_config(9), struct mesh_setup(9), struct ocb_setup(9), struct ieee80211_txq_params(9). mesh girlies rise 🧚


πŸ’« the scan section and its extended family πŸ’«

Scanning and BSS list handling(9) β€” huge. iconic. struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9), struct cfg80211_scan_request(9), struct cfg80211_match_set(9), struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9), enum cfg80211_signal_type(9), struct cfg80211_inform_bss(9), struct cfg80211_bss_ies(9), struct cfg80211_bss(9), ieee80211_bss_get_elem(9), ieee80211_bss_get_ie(9). all the BSS besties in one place πŸ¦‹

then the connecting-and-leaving crew: struct cfg80211_auth_request(9), struct cfg80211_assoc_link(9), struct cfg80211_ml_reconf_req(9), enum cfg80211_assoc_req_flags(9), struct cfg80211_assoc_request(9), struct cfg80211_deauth_request(9), struct cfg80211_disassoc_request(9), struct cfg80211_ibss_params(9), struct cfg80211_bss_selection(9), struct cfg80211_connect_params(9), enum cfg80211_connect_params_changed(9), enum wiphy_params_flags(9), struct cfg80211_pmksa(9), struct cfg80211_pkt_pattern(9). auth β†’ assoc β†’ deauth β†’ disassoc, the full friendship cycle tbh πŸ’€

and the power-save / wowlan-adjacent stack: struct cfg80211_wowlan_tcp(9), struct cfg80211_wowlan(9), struct cfg80211_coalesce_rules(9), struct cfg80211_coalesce(9), struct cfg80211_wowlan_nd_match(9), struct cfg80211_wowlan_nd_info(9), struct cfg80211_wowlan_wakeup(9), struct cfg80211_gtk_rekey_data(9), struct cfg80211_update_ft_ies_params(9), struct cfg80211_mgmt_tx_params(9), struct cfg80211_dscp_exception(9), struct cfg80211_dscp_range(9), struct cfg80211_qos_map(9). QoS map said "I'm ending this paragraph" and she did πŸ‘‘


Neighbor Awareness Networking (NAN)(9) β€” okay she got her own heading, respect. struct cfg80211_nan_band_config(9), struct cfg80211_nan_conf(9), struct cfg80211_nan_channel(9), struct cfg80211_nan_local_sched(9), struct cfg80211_nan_peer_map(9), struct cfg80211_nan_peer_sched(9), enum cfg80211_nan_conf_changes(9), struct cfg80211_nan_func_filter(9), struct cfg80211_nan_func(9). nan girlies we see you 🌸

right after: struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9), struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9), struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9), struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9). ranging and OWE, we love a measurement moment πŸ“


then the wiphy infrastructure β€” genuinely the backbone, no cap: struct cfg80211_ops(9), enum wiphy_flags(9), struct ieee80211_iface_limit(9), struct ieee80211_iface_combination(9), enum wiphy_wowlan_support_flags(9), struct wiphy_wowlan_support(9), struct wiphy_coalesce_support(9), enum wiphy_vendor_command_flags(9), enum wiphy_opmode_flag(9), struct sta_opmode_info(9), struct wiphy_vendor_command(9), struct wiphy_iftype_ext_capab(9), cfg80211_get_iftype_ext_capa(9), struct cfg80211_pmsr_capabilities(9), struct wiphy_iftype_akm_suites(9), struct wiphy_radio_cfg(9), struct wiphy_radio_freq_range(9), struct wiphy_radio(9), enum wiphy_nan_flags(9), struct wiphy_nan_capa(9), struct wiphy(9). that's the whole wiphy cinematic universe πŸ’œ

and the accessor/allocation crew: wiphy_priv(9), priv_to_wiphy(9), set_wiphy_dev(9), wiphy_dev(9), wiphy_name(9), wiphy_new_nm(9), wiphy_new(9), wiphy_register(9), rcu_dereference_wiphy(9), wiphy_dereference(9), get_wiphy_regdom(9), wiphy_unregister(9), wiphy_free(9), wiphy_lock(9), wiphy_unlock(9). wiphy_new_nm(9) and wiphy_new(9) right next to each other β€” the named one and the one without a name, it's giving siblings 🫢

oh and the workqueue girlies, they get a whole run: wiphy_work_queue(9), wiphy_work_cancel(9), wiphy_work_flush(9), wiphy_delayed_work_queue(9), wiphy_delayed_work_cancel(9), wiphy_delayed_work_flush(9), wiphy_delayed_work_pending(9), wiphy_hrtimer_work_queue(9), wiphy_hrtimer_work_cancel(9), wiphy_hrtimer_work_flush(9), wiphy_hrtimer_work_pending(9). queue, cancel, flush, pending β€” the four moods, repeated three times for regular, delayed, and hrtimer ✨

wrapping this chunk: enum ieee80211_ap_reg_power(9), struct wireless_dev(9), wdev_priv(9), wdev_chandef(9). wdev said "my turn" πŸŽ€


Utility functions(9) β€” the little helpers nobody thanks but everybody calls: ieee80211_channel_equal(9), ieee80211_channel_to_khz(9), ieee80211_channel_to_freq_khz(9), ieee80211_channel_to_frequency(9), ieee80211_freq_khz_to_channel(9), ieee80211_frequency_to_channel(9), ieee80211_get_channel_khz(9), ieee80211_get_channel(9), cfg80211_channel_is_psc(9), ieee80211_radio_freq_range_valid(9), cfg80211_radio_chandef_valid(9), cfg80211_wdev_channel_allowed(9), ieee80211_get_response_rate(9), ieee80211_mandatory_rates(9), struct ieee80211_radiotap_iterator(9), ieee80211_get_hdrlen_from_skb(9), ieee80211_hdrlen(9), ieee80211_get_mesh_hdrlen(9). channel ↔ frequency in both directions, khz and non-khz flavours, because of course there's both 😭

Data path helpers(9) β€” down here we're doing the actual packet wrangling: ieee80211_data_to_8023_exthdr(9), ieee80211_data_to_8023(9), ieee80211_is_valid_amsdu(9), ieee80211_amsdu_to_8023s(9), ieee80211_get_8023_tunnel_proto(9), ieee80211_strip_8023_mesh_hdr(9), cfg80211_classify8021d(9), cfg80211_find_elem_match(9), cfg80211_find_ie_match(9), cfg80211_find_elem(9), cfg80211_find_ie(9), cfg80211_find_ext_elem(9), cfg80211_find_ext_ie(9), cfg80211_find_vendor_elem(9), cfg80211_find_vendor_ie(9), enum cfg80211_rnr_iter_ret(9), cfg80211_iter_rnr(9), cfg80211_defragment_element(9), cfg80211_send_layer2_update(9). yes the _elem / _ie pairs are real and yes you have to pick the right one, iykyk πŸ”₯


Regulatory enforcement infrastructure(9) β€” the vibes police, and I mean that with love: regulatory_hint(9), regulatory_set_wiphy_regd(9), regulatory_set_wiphy_regd_sync(9), wiphy_apply_custom_regulatory(9), freq_reg_info(9), reg_initiator_name(9), regulatory_pre_cac_allowed(9). then Internal regulatory db functions(9) with just reg_query_regdb_wmm(9) holding it down solo. she's internal, she doesn't need company πŸ’…

back to BSS + scan callbacks: cfg80211_scan_done(9), cfg80211_sched_scan_results(9), cfg80211_sched_scan_stopped(9), cfg80211_sched_scan_stopped_locked(9), cfg80211_inform_bss_frame_data(9), cfg80211_gen_new_bssid(9), cfg80211_is_element_inherited(9), cfg80211_merge_profile(9), enum cfg80211_bss_frame_type(9), cfg80211_get_ies_channel_number(9), cfg80211_ssid_eq(9), cfg80211_inform_bss_data(9), __cfg80211_get_bss(9), cfg80211_get_bss(9), cfg80211_ref_bss(9), cfg80211_put_bss(9), cfg80211_unlink_bss(9), cfg80211_bss_iter(9). note __cfg80211_get_bss(9) hiding under cfg80211_get_bss(9) β€” the underscore-prefixed one, you know the drill πŸ™ˆ

mlme and failure notifications: cfg80211_rx_mlme_mgmt(9), cfg80211_auth_timeout(9), struct cfg80211_rx_assoc_resp_data(9), cfg80211_rx_assoc_resp(9), struct cfg80211_assoc_failure(9), cfg80211_assoc_failure(9), cfg80211_tx_mlme_mgmt(9), cfg80211_rx_unprot_mlme_mgmt(9), cfg80211_michael_mic_failure(9), cfg80211_ibss_joined(9), cfg80211_notify_new_peer_candidate(9). michael mic failure is such a dramatic name, she ate 🌈


RFkill integration(9) β€” short and sweet: wiphy_rfkill_set_hw_state_reason(9), wiphy_rfkill_start_polling(9), wiphy_rfkill_stop_polling(9). start polling, stop polling, that's the whole arc πŸŽ€

Vendor commands(9) β€” for the driver besties doing their own thing: cfg80211_vendor_cmd_alloc_reply_skb(9), cfg80211_vendor_cmd_reply(9), cfg80211_vendor_cmd_get_sender(9), cfg80211_vendor_event_alloc(9), cfg80211_vendor_event_alloc_ucast(9), cfg80211_vendor_event(9). alloc, reply, get_sender β€” the vendor trio, plus the event side πŸ’«

Test mode(9) β€” cfg80211_testmode_alloc_reply_skb(9), cfg80211_testmode_reply(9), cfg80211_testmode_alloc_event_skb(9), cfg80211_testmode_event(9). same shape as vendor but test-flavoured, don't mix them up 🧚


okay final stretch, and it's the events-and-notifications marathon, so buckle up: struct cfg80211_fils_resp_params(9), struct cfg80211_connect_resp_params(9), cfg80211_connect_done(9), cfg80211_connect_bss(9), cfg80211_connect_result(9), cfg80211_connect_timeout(9), struct cfg80211_roam_info(9), cfg80211_roamed(9), cfg80211_port_authorized(9), cfg80211_disconnected(9). the full connect journey from done to result to timeout to roamed to disconnected 😭

channel + management frames: cfg80211_ready_on_channel(9), cfg80211_remain_on_channel_expired(9), cfg80211_tx_mgmt_expired(9), cfg80211_sinfo_alloc_tid_stats(9), cfg80211_link_sinfo_alloc_tid_stats(9), cfg80211_sinfo_release_content(9), cfg80211_new_sta(9), cfg80211_del_sta_sinfo(9), cfg80211_del_sta(9), cfg80211_conn_failed(9), struct cfg80211_rx_info(9), cfg80211_rx_mgmt_ext(9), cfg80211_rx_mgmt_khz(9), cfg80211_rx_mgmt(9), struct cfg80211_tx_status(9), cfg80211_mgmt_tx_status_ext(9), cfg80211_mgmt_tx_status(9), cfg80211_control_port_tx_status(9), cfg80211_rx_control_port(9). cfg80211_del_sta_sinfo(9) vs cfg80211_del_sta(9) β€” one's the deluxe version πŸ’…

then the quality-monitoring crew: cfg80211_cqm_rssi_notify(9), cfg80211_cqm_pktloss_notify(9), cfg80211_cqm_txe_notify(9), cfg80211_cqm_beacon_loss_notify(9), __cfg80211_radar_event(9), cfg80211_sta_opmode_change_notify(9), cfg80211_cac_event(9), cfg80211_background_cac_abort(9), cfg80211_gtk_rekey_notify(9), cfg80211_pmksa_candidate_notify(9), cfg80211_rx_spurious_frame(9), cfg80211_rx_unexpected_4addr_frame(9), cfg80211_probe_status(9), cfg80211_report_obss_beacon_khz(9), cfg80211_report_obss_beacon(9), struct cfg80211_beaconing_check_config(9). __cfg80211_radar_event(9) with the double underscore up front, and cfg80211_report_obss_beacon_khz(9) before the plain cfg80211_report_obss_beacon(9) β€” khz flavour first, that's just how she rolls 🌸

and that's the whole cross-reference pile. 358 entries deep and every single one of them got a mention, bestie. no skipping, no summarizing, we don't do that here. 🫢✨

…and we're back, still deep in the SEE ALSO squad 😭 bestie there are like sixty more of these and I'm not skipping a single one, so buckle up 🫢

First up, the girlies whose names literally have beacon and ch_switch in them ✨ (channel drama, we love to see it):

Next, the operating-class-to-chandef math crew β€” conversions everywhere, it's giving calculator app πŸ’…:

The TDLS / bitrate / device registration lineup πŸŽ€:

Fast transition, P2P attribute hunting, and the IE-splitting icons 🌸:

Wakeup reports, crit proto, channel counting and combination checking πŸ¦‹:

The "shut it down" trio, honestly main character energy πŸ’€:

Extended features + the NAN girlies ✨:

External auth, PMSR, iftype checking, assoc comeback and OWE 🌈:

BSS flushing and the whole colour-change saga (started, aborted, done β€” a whole trilogy fr fr) πŸ’œ:

6 GHz power type + the MLO reconf crew πŸ‘‘:

Channel checks, EPCS, and even more NAN (she's everywhere, she's booked and busy) 🧚:

And the final stretch β€” debugfs lockers, S1G freq stuff, and the incumbent signal icon that closes us out πŸ™ˆ:


That's the whole list, bestie β€” every single one, no skips, no cap πŸ’–

This lil' page lives in ./include/net, it's dated October 2026, and it goes by enum monitor_flags(9). Go forth and slay your kernel docs πŸŽ€βœ¨

πŸ“¦ where this page comes from