cfg80211_nan...c_terminated(9)
π cfg80211_nan_func_terminated(9) β kernel API manual, but make it make sense
okay so this is cfg80211_nan_func_terminated, straight out of the kernel API manual, and bestie it is exactly what it sounds like: it's the little messenger that goes "hey, that NAN function? yeah, it's done. terminated. gone. π" No cap.
β¨ NAME β¨
cfg80211_nan_func_terminated β notify about NAN function termination. that's the whole job. it reports the ending. the finale. the last episode. π¬
π¦ SYNOPSIS π¦
void cfg80211_nan_func_terminated (struct wireless_dev *wdev , u8
inst_id , enum nl80211_nan_func_term_reason reason , u64 cookie , gfp_t
gfp );
it returns void, meaning it hands you nothing back β it's giving generous, it's giving "the reward is the friends we made along the way". π«Ά
π ARGUMENTS π
wdevβ the wireless device reporting the match. yeah, this is the one spilling the tea. π’inst_idβ the local instance id. it's theu8lil' name tag so everyone knows which instance we're talking about.reasonβ termination reason, and it's gotta be one of theNL80211_NAN_FUNC_TERM_REASON_*values. no homemade reasons, no vibes-based reasons, only the canon list. πreason... jk not twice βcookieβ unique NAN function identifier. it's literally the function's main character ID. πͺgfpβ allocation flags. the classicgfp_tmoment, because the kernel always needs to know how you want your memory served. πΈ
π DESCRIPTION π
so what does it actually do? simple, iconique: this function reports that a NAN function is terminated. that's it. that's the whole plot. it's the "we need to talk" text but for a NAN function's lifecycle. β¨
lowkey important: it's a report. it's announcing the termination, not doing the dramatic breaking-up for you. don't come for me, that's literally what the page says. π
more parts coming, don't go anywhere bestie π
π SEE ALSO π
okay bestie, this is the part where the page just... lists everything. and i mean everything. it's giving "the author found every single symbol in the header and went 'yes, all of them'". no cap, it's a whole vibe. here's the complete list, in the exact order it's given, nothing cut π«Ά
- the kernel file itself:
./include/net/cfg80211.hβ andIntroduction(9)to hold your hand through it
πΈ the header intro & the band/capability era π¦
Device registration(9)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)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)wiphy_read_of_freq_limits(9)
lowercase _ieee80211_set_sband_iftype_data(9) sitting right next to the regular one β that's the internal twin, bestie. they really said "you get both versions" π
β¨ Actions and configuration β the whole saga π
Actions and configuration(9)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)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)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)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 monitor_flags(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)
π¦ Scanning and BSS list handling π₯
Scanning and BSS list handling(9)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)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)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)
π Neighbor Awareness Networking (NAN) β our main character β¨
Neighbor Awareness Networking (NAN)(9)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)
okay that's the NAN section and yes it's literally the icon of this whole page π keep going, there's more π
π more structs: auth, PMK, FTM, PMSR π
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)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)
π the wiphy life cycle era π«Ά
struct wiphy(9)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_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)enum ieee80211_ap_reg_power(9)struct wireless_dev(9)wdev_priv(9)wdev_chandef(9)
look at all those wiphy_*_work_* and wiphy_hrtimer_work_* pairs β queue, cancel, flush, pending, four times over. they really said "consistency is free, do it for everything" ππ
π§ Utility functions π
Utility functions(9)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)
β Data path helpers π
Data path helpers(9)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)
πΈ Regulatory enforcement infrastructure π
Regulatory enforcement infrastructure(9)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)Internal regulatory db functions(9)reg_query_regdb_wmm(9)
note the difference betweenregulatory_set_wiphy_regd(9)andregulatory_set_wiphy_regd_sync(9)β one's got the_syncglow-up, iykyk π
π₯ scan/BSS notifications, MLME & friends π
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)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)
the __-prefixed __cfg80211_get_bss(9) is the lowkey twin of cfg80211_get_bss(9), it's giving internal-helper energy π
π RFkill integration, Vendor commands, Test mode π
RFkill integration(9)wiphy_rfkill_set_hw_state_reason(9)wiphy_rfkill_start_polling(9)wiphy_rfkill_stop_polling(9)Vendor commands(9)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)Test mode(9)cfg80211_testmode_alloc_reply_skb(9)cfg80211_testmode_reply(9)cfg80211_testmode_alloc_event_skb(9)cfg80211_testmode_event(9)
π connect / roam / disconnect notifications π
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)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)
π rx/tx mgmt, control port, CQM, radar etc. π¦
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_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)
aaaaand that's the entire SEE ALSO list, every single one, nothing skipped π and yeah the page keeps going after this so don't you dare close the tab yet, bestie ππ
...and the rest of the extended fam, bestie β the whole group chat is here, no one got left on read π
cfg80211_reg_check_beaconing(9)β the regulatory vibe check for beaconingcfg80211_reg_can_beacon(9)β can you even beacon, or nah?cfg80211_reg_can_beacon_relax(9)β same question, chiller energycfg80211_ch_switch_notify(9)β "we moved channels, fyi"cfg80211_ch_switch_started_notify(9)β the "omw" of channel switchesieee80211_operating_class_to_band(9)β operating class β‘οΈ band, glow-up completeieee80211_operating_class_to_chandef(9)β operating class β‘οΈ channel definitionieee80211_chandef_to_operating_class(9)β the reverse slayieee80211_chandef_to_khz(9)β chandef but make it kHzcfg80211_tdls_oper_request(9)β TDLS operations, requested β¨cfg80211_calculate_bitrate(9)β math era, we love to see itcfg80211_unregister_wdev(9)β bye, wireless device π«Άcfg80211_register_netdevice(9)β hello, netdevice πcfg80211_unregister_netdevice(9)β and goodbye again πstruct cfg80211_ft_event_params(9)β the fast-transition event params structcfg80211_ft_event(9)β the fast-transition event itselfcfg80211_get_p2p_attr(9)β grab that P2P attributeieee80211_ie_split_ric(9)β splittin' IEs, RIC editionieee80211_ie_split(9)β same but the plain versionieee80211_fragment_element(9)β chomping that element into fragmentscfg80211_report_wowlan_wakeup(9)β "wake up bestie, WoWLAN's calling" πcfg80211_crit_proto_stopped(9)β critical protocol has left the chatieee80211_get_num_supported_channels(9)β count those channels, periodtcfg80211_check_combinations(9)β the combos check, very main charactercfg80211_iter_combinations(9)β iterate them comboscfg80211_get_radio_idx_by_chan(9)β which radio owns this chan, iykykcfg80211_stop_link(9)β link, you're donecfg80211_stop_iface(9)β iface too, sorry bestiecfg80211_shutdown_all_interfaces(9)β the full shutdown, dramatic on purpose π₯wiphy_ext_feature_set(9)β born to set extended featureswiphy_ext_feature_isset(9)β born to check if they're setcfg80211_free_nan_func(9)β free the NAN function, be responsible π§struct cfg80211_nan_match_params(9)β the NAN match params structcfg80211_nan_match(9)β it's a NAN match, it's giving discoverycfg80211_nan_sched_update_done(9)β schedule update, wrapped βcfg80211_external_auth_request(9)β auth, but outsourcedcfg80211_pmsr_report(9)β peer measurement, reportedcfg80211_pmsr_complete(9)β and now it's complete, we cheeredcfg80211_iftype_allowed(9)β allowed iftype? Let's find outcfg80211_assoc_comeback(9)β the comeback era of association πcfg80211_update_owe_info_event(9)β OWE info event, updatedcfg80211_bss_flush(9)β flush those BSS entries π½β¨cfg80211_bss_color_notify(9)β notify about BSS colorcfg80211_obss_color_collision_notify(9)β color collision, uh oh πcfg80211_color_change_started_notify(9)β color change: startedcfg80211_color_change_aborted_notify(9)β color change: aborted, sadcfg80211_color_change_notify(9)β color change: just notifycfg80211_6ghz_power_type(9)β 6 GHz power type, very modern of itcfg80211_links_removed(9)β links gone, we don't talk about itstruct cfg80211_mlo_reconf_done_data(9)β MLO reconfig done data struct πΈcfg80211_mlo_reconf_add_done(9)β MLO reconfig add, done and dustedcfg80211_schedule_channels_check(9)β schedule that channel checkcfg80211_epcs_changed(9)β EPCS changed, notedcfg80211_next_nan_dw_notif(9)β next NAN discovery window notificationcfg80211_nan_cluster_joined(9)β bestie joined the NAN cluster π«Άcfg80211_nan_ulw_update(9)β ULW update, iconiccfg80211_nan_channel_evac(9)β evacuate that NAN channel πββοΈwiphy_locked_debugfs_read(9)β debugfs read, but locked πwiphy_locked_debugfs_write(9)β debugfs write, also lockedcfg80211_s1g_get_start_freq_khz(9)β S1G start freq in kHzcfg80211_s1g_get_end_freq_khz(9)β S1G end freq in kHzcfg80211_s1g_get_primary_sibling(9)β find that primary siblingcfg80211_incumbent_signal_notify(9)β incumbent signal, notified π‘
That's the whole roster β 63 cross-refs, not one dropped, because we don't do incomplete lists in this house π
And that's a wrap on the whole page, bestie π This iteration came straight out of ./include/net, dated October 2026 β so go forth, register your netdevices, free your NAN funcs, and stay slay β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms