STRUCT MESH_CONFIG(9)
π NAME π
struct mesh_config β the 802.11s mesh configuration, bestie. Yes it's a (9) kernel API manual page, and yes it's kind of a lot, but we're gonna get through it together π«Ά
β¨ SYNOPSIS β¨
struct mesh_config {
u16 dot11MeshRetryTimeout;
u16 dot11MeshConfirmTimeout;
u16 dot11MeshHoldingTimeout;
u16 dot11MeshMaxPeerLinks;
u8 dot11MeshMaxRetries;
u8 dot11MeshTTL;
u8 element_ttl;
bool auto_open_plinks;
u32 dot11MeshNbrOffsetMaxNeighbor;
u8 dot11MeshHWMPmaxPREQretries;
u32 path_refresh_time;
u16 min_discovery_timeout;
u32 dot11MeshHWMPactivePathTimeout;
u16 dot11MeshHWMPpreqMinInterval;
u16 dot11MeshHWMPperrMinInterval;
u16 dot11MeshHWMPnetDiameterTraversalTime;
u8 dot11MeshHWMPRootMode;
bool dot11MeshConnectedToMeshGate;
bool dot11MeshConnectedToAuthServer;
u16 dot11MeshHWMPRannInterval;
bool dot11MeshGateAnnouncementProtocol;
bool dot11MeshForwarding;
s32 rssi_threshold;
u16 ht_opmode;
u32 dot11MeshHWMPactivePathToRootTimeout;
u16 dot11MeshHWMProotInterval;
u16 dot11MeshHWMPconfirmationInterval;
enum nl80211_mesh_power_mode power_mode;
u16 dot11MeshAwakeWindowDuration;
u32 plink_timeout;
bool dot11MeshNolearn;
};
Yeah that's 31 fields. We're listing every single one. Buckle up π
π Members π
Okay so here's the whole cast, one by one, no skipping, no "etc." β the way that a manpage respects you enough to name all of them? Iconic behavior.
dot11MeshRetryTimeoutβ the initial retry timeout in millisecond units, used by the Mesh Peering Open message β±οΈdot11MeshConfirmTimeoutβ the initial retry timeout in millisecond units, used by the Mesh Peering Open message. And yes, before you @ me β the docs say exactly the same thing for this one as fordot11MeshRetryTimeout. That's just how it's written, I'm not making it up πdot11MeshHoldingTimeoutβ the confirm timeout in millisecond units, and the mesh peering management uses it to close a mesh peering πͺdot11MeshMaxPeerLinksβ the maximum number of peer links allowed on this mesh interface, i.e. how many friends this interface is allowed to have β¨dot11MeshMaxRetriesβ the maximum number of peer link open retries that can be sent to establish a new peer link instance in a mesh. So how many times we're allowed to knock before we accept it π«Άdot11MeshTTLβ the value of the TTL field set at a source mesh STAelement_ttlβ the value of the TTL field set at a mesh STA for path selection elementsauto_open_plinksβ whether we should automatically open peer links when we detect compatible mesh peers. The "do we shoot our shot unprompted" flag πdot11MeshNbrOffsetMaxNeighborβ the maximum number of neighbors to synchronize to, for the 11s default synchronization methoddot11MeshHWMPmaxPREQretriesβ the number of action frames containing a PREQ that an originator mesh STA can send to a particular path targetpath_refresh_timeβ how frequently to refresh mesh paths, in milliseconds πmin_discovery_timeoutβ the minimum length of time to wait until giving up on a path discovery, in milliseconds. The "when do I stop waiting for a text back" number πdot11MeshHWMPactivePathTimeoutβ the time (in TUs) for which mesh STAs receiving a PREQ shall consider the forwarding information from the root to be valid. (TU = time unit β³)dot11MeshHWMPpreqMinIntervalβ the minimum interval of time (in TUs) during which a mesh STA can send only one action frame containing a PREQ element. One. At a time. Patience, queen πdot11MeshHWMPperrMinIntervalβ the minimum interval of time (in TUs) during which a mesh STA can send only one Action frame containing a PERR elementdot11MeshHWMPnetDiameterTraversalTimeβ the interval of time (in TUs) that it takes for an HWMP information element to propagate across the mesh πdot11MeshHWMPRootModeβ the configuration of a mesh STA as root mesh STAdot11MeshConnectedToMeshGateβ if set to true, we advertise that this STA is connected to a mesh gate in mesh formation info. If false, the value in mesh formation is determined by the presence of root paths in the mesh path table πͺdot11MeshConnectedToAuthServerβ if set to true then this mesh STA will advertise that it is connected to a authentication server in the mesh formation fielddot11MeshHWMPRannIntervalβ the interval of time (in TUs) between root announcements are transmitted. Yes, "between ... are transmitted" β grammar is on vacation, the meaning is "how often root announcements go out" π’dot11MeshGateAnnouncementProtocolβ whether to advertise that this mesh station has access to a broader network beyond the MBSS. Trust, this one comes with lore: (This is missnamed in draft 12.0:dot11MeshGateAnnouncementProtocolset to true only means that the station will announce others it's a mesh gate, but not necessarily using the gate announcement protocol. Still keeping the same nomenclature to be in sync with the spec.) So the name is lowkey lying but we keep it fr fr π·οΈdot11MeshForwardingβ whether the Mesh STA is forwarding or non-forwarding entity (default isTRUEβ forwarding entity) πrssi_thresholdβ the threshold for average signal strength of candidate station to establish a peer link πΆht_opmodeβ mesh HT protection modedot11MeshHWMPactivePathToRootTimeoutβ The time (in TUs) for which mesh STAs receiving a proactive PREQ shall consider the forwarding information to the root mesh STA to be validdot11MeshHWMProotIntervalβ The interval of time (in TUs) between proactive PREQs are transmitteddot11MeshHWMPconfirmationIntervalβ The minimum interval of time (in TUs) during which a mesh STA can send only one Action frame containing a PREQ element for root path confirmationpower_modeβ The default mesh power save mode, which will be the initial setting for new peer links. (enum nl80211_mesh_power_mode, if you were wondering what type it is) π΄dot11MeshAwakeWindowDurationβ The duration in TUs the STA will remain awake after transmitting its beacon. The post-beacon scroll session πplink_timeoutβ If no tx activity is seen from a STA we've established peering with for longer than this time (in seconds), then remove it from the STA's list of peers. Default is 30 minutes π°οΈdot11MeshNolearnβ Try to avoid multi-hop path discovery (e.g. PREQ/PREP for HWMP) if the destination is a direct neighbor. But heads up β note that this might not be the optimal decision as a multi-hop route might be better. So if using this setting you will likely also want to disabledot11MeshForwardingand use another mesh routing protocol on top. Not a "set it and forget it" girlie, got it? π
πΈ Description πΈ
These parameters can be changed while the mesh is active. Live edits, no restart required β slay π
β¨ SEE ALSO β¨
okay bestie, deep breath π this is the "you liked this, so go read 350 other pages" section, and no cap it is enormous. it's basically the entire cfg80211 chapter of the kernel docs dumped out in one go. i'm keeping it in the exact same order so you can follow along like a playlist, and sprinkling commentary where my brain lit up. let's go π
the file itself, the origin story ποΈ
Kernel file ./include/net/cfg80211.h
like, if you only click one thing, click this one. it's the header all of this lives in.
start at the very beginning π
Introduction(9)Device registration(9)
these two are literally the opening acts, read them first or you'll be lost in the sauce fr.
channels, rates, bands & caps π‘
the whole "what radio are we even talking about" era of your journey:
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)
ht, vht, he, eht, uhrβ¦ the alphabet soup is real π it's giving "every generation of wifi got its own struct".
the sband iftype data situation (iconic) π
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)
and then the very important little family around it:
_ieee80211_set_sband_iftype_data(9)ieee80211_set_sband_iftype_data(9)for_each_sband_iftype_data(9)
that leading underscore one is the internal twin, iykyk π«Ά
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)
actions and configuration π οΈ
this is a whole chapter of the docs, and it comes with its own cast:
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)
chandef city, population: yes ποΈ
the channel-definition girlies are thriving here:
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)
dfs required vs dfs usable vs dfs cac time β three separate pages, three separate moods π
survey, crypto, AP settings & beaconing πΈ
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)
the AP girls are booked and busy π
interface combos & stations π―
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)
note the del variants are separate pages, don't @ me, that's just how it is π«
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)
SAR (the power police) π¨
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)
monitor, mesh & OCB era π¦
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_setup(9)struct ocb_setup(9)struct ieee80211_txq_params(9)
scanning and BSS list handling π
whole chapter, whole vibe:
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)
auth, assoc, deauth, disassoc (the social life of a station) π
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)
the way that auth and deauth are both here and they're not even on speaking terms π
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)
wowlan, coalesce & power saving π΄
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)
NAN, aka Neighbor Awareness Networking π§
(this is the group chat that also shows up as its own chapter)
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)
pmk, external auth, measurement & OWE π
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)
the wiphy mothership π
everything orbits these:
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)
wiphy lifecycle & friends (the whole friend group) π«Ά
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)
create β register β then the RCU-flavoured pointer magic:
and the graceful exit:
plus the locking era π
wiphy work queues (yes, both flavours) β°
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)
regular, delayed, and hrtimer β three whole flavours, all with queue/cancel/flush, and the delayed one also gets a pending. queen behaviour honestly π
wireless_dev & regulatory power πΈ
enum ieee80211_ap_reg_power(9)struct wireless_dev(9)wdev_priv(9)wdev_chandef(9)
utility functions π§°
whole chapter, then the individual helpers:
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)
channel β freq, khz and non-khz versions, both directions β pick your fighter π
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)
element hunting (find those IEs) π
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)
yes, elem and ie both get a match version and a plain version. four for four. we love consistency π
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)
and the internals, lowkey spicy πΆοΈ
Internal regulatory db functions(9)reg_query_regdb_wmm(9)
scan results & BSS notifications πΆ
cfg80211_scan_done(9)cfg80211_sched_scan_results(9)cfg80211_sched_scan_stopped(9)cfg80211_sched_scan_stopped_locked(9)
note the _locked one β different function, different rules, do not swap them π
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)
ref and put are a matched set, pls don't leak π«
mlme mgmt, assoc responses & mic failures π
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)
RFkill integration π΄
RFkill integration(9)wiphy_rfkill_set_hw_state_reason(9)wiphy_rfkill_start_polling(9)wiphy_rfkill_stop_polling(9)
vendor commands π€
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 π§ͺ
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 era π«
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)
connect, connected, roamed, disconnectedβ¦ the full relationship arc π
channel stays & mgmt tx π
station info bookkeeping π
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 frames & control port π¨
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)
CQM & radar & CAC stuff π‘π₯
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)
the notify girlies (all of them) π
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)
and the last one, saving the best for the end π
struct cfg80211_beaconing_check_config(9)
so yeah, that's the roster π literally hundreds of cross-references, and that's only the pointers β the actual legal / author-y bits are still coming, so don't wander off just yet.
okay so the cross-reference list for this one is long β like, genuinely a whole scroll β but every single one is here because that's the whole point of a good SEE ALSO: you're never lost, bestie, you're just one man away from whatever you actually needed πΈ
cfg80211_reg_check_beaconing(9)cfg80211_reg_can_beacon(9)cfg80211_reg_can_beacon_relax(9)cfg80211_ch_switch_notify(9)cfg80211_ch_switch_started_notify(9)ieee80211_operating_class_to_band(9)ieee80211_operating_class_to_chandef(9)ieee80211_chandef_to_operating_class(9)ieee80211_chandef_to_khz(9)cfg80211_tdls_oper_request(9)cfg80211_calculate_bitrate(9)cfg80211_unregister_wdev(9)cfg80211_register_netdevice(9)cfg80211_unregister_netdevice(9)struct cfg80211_ft_event_params(9)cfg80211_ft_event(9)cfg80211_get_p2p_attr(9)ieee80211_ie_split_ric(9)ieee80211_ie_split(9)ieee80211_fragment_element(9)cfg80211_report_wowlan_wakeup(9)cfg80211_crit_proto_stopped(9)
like, that first chunk is already giving networking main character energy π and we're not even done. keep scrolling, bestie π
ieee80211_get_num_supported_channels(9)cfg80211_check_combinations(9)cfg80211_iter_combinations(9)cfg80211_get_radio_idx_by_chan(9)cfg80211_stop_link(9)cfg80211_stop_iface(9)cfg80211_shutdown_all_interfaces(9)wiphy_ext_feature_set(9)wiphy_ext_feature_isset(9)cfg80211_free_nan_func(9)struct cfg80211_nan_match_params(9)cfg80211_nan_match(9)cfg80211_nan_func_terminated(9)cfg80211_nan_sched_update_done(9)cfg80211_external_auth_request(9)cfg80211_pmsr_report(9)cfg80211_pmsr_complete(9)cfg80211_iftype_allowed(9)cfg80211_assoc_comeback(9)cfg80211_update_owe_info_event(9)cfg80211_bss_flush(9)
midway scroll check: you're doing amazing π«Ά the NAN girls are all accounted for, the feature-flag besties too, and yes there's more. always more β¨
cfg80211_bss_color_notify(9)cfg80211_obss_color_collision_notify(9)cfg80211_color_change_started_notify(9)cfg80211_color_change_aborted_notify(9)cfg80211_color_change_notify(9)cfg80211_6ghz_power_type(9)cfg80211_links_removed(9)struct cfg80211_mlo_reconf_done_data(9)cfg80211_mlo_reconf_add_done(9)cfg80211_schedule_channels_check(9)cfg80211_epcs_changed(9)cfg80211_next_nan_dw_notif(9)cfg80211_nan_cluster_joined(9)cfg80211_nan_ulw_update(9)cfg80211_nan_channel_evac(9)wiphy_locked_debugfs_read(9)wiphy_locked_debugfs_write(9)cfg80211_s1g_get_start_freq_khz(9)cfg80211_s1g_get_end_freq_khz(9)cfg80211_s1g_get_primary_sibling(9)cfg80211_incumbent_signal_notify(9)
and that's the whole roll call, bestie β all sixty-four of them, not a single one skipped, no cap π if you got this far you're lowkey a kernel networking girlie now, and honestly? iconic behavior π
fr fr though: if you're jumping into any of these, read that page's own DESCRIPTION and OPTIONS before you start poking structs β cross-references are a map, not a vibe check π
okay and finally, the cute lil sign-off π this page ships out of ./include/net β that's the source path, mwah β dated October 2026, and the page itself is struct mesh_config(9). slay, documented, periodt π¦
π¦ 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