struct_ieee80211_vif(9) [centos man page]
STRUCT
IEEE80211_VIF(9) The basic mac80211 driver inte STRUCT IEEE80211_VIF(9) NAME
struct_ieee80211_vif - per-interface data SYNOPSIS
struct ieee80211_vif { enum nl80211_iftype type; struct ieee80211_bss_conf bss_conf; u8 addr[ETH_ALEN]; bool p2p; u8 cab_queue; u8 hw_queue[IEEE80211_NUM_ACS]; struct ieee80211_chanctx_conf __rcu * chanctx_conf; u32 driver_flags; #ifdef CONFIG_MAC80211_DEBUGFS struct dentry * debugfs_dir; #endif u8 drv_priv[0]; }; MEMBERS
type type of this virtual interface bss_conf BSS configuration for this interface, either our own or the BSS we're associated to addr[ETH_ALEN] address of this interface p2p indicates whether this AP or STA interface is a p2p interface, i.e. a GO or p2p-sta respectively cab_queue content-after-beacon (DTIM beacon really) queue, AP mode only hw_queue[IEEE80211_NUM_ACS] hardware queue for each AC chanctx_conf The channel context this interface is assigned to, or NULL when it is not assigned. This pointer is RCU-protected due to the TX path needing to access it; even though the netdev carrier will always be off when it is NULL there can still be races and packets could be processed after it switches back to NULL. driver_flags flags/capabilities the driver has for this interface, these need to be set (or cleared) when the interface is added or, if supported by the driver, the interface type is changed at runtime, mac80211 will never touch this field debugfs_dir debugfs dentry, can be used by drivers to create own per interface debug files. Note that it will be NULL for the virtual monitor interface (if that is requested.) drv_priv[0] data area for driver use, will always be aligned to sizeof(void *). DESCRIPTION
Data in this structure is continually present for driver use during the life of a virtual interface. AUTHOR
Johannes Berg <johannes@sipsolutions.net> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT IEEE80211_VIF(9)
Check Out this Related Man Page
STRUCT
CFG80211_BSS(9) Scanning and BSS list handling STRUCT CFG80211_BSS(9) NAME
struct_cfg80211_bss - BSS description SYNOPSIS
struct cfg80211_bss { struct ieee80211_channel * channel; const struct cfg80211_bss_ies __rcu * ies; const struct cfg80211_bss_ies __rcu * beacon_ies; const struct cfg80211_bss_ies __rcu * proberesp_ies; struct cfg80211_bss * hidden_beacon_bss; s32 signal; u16 beacon_interval; u16 capability; u8 bssid[ETH_ALEN]; u8 priv[0]; }; MEMBERS
channel channel this BSS is on ies the information elements (Note that there is no guarantee that these are well-formed!); this is a pointer to either the beacon_ies or proberesp_ies depending on whether Probe Response frame has been received. It is always non-NULL. beacon_ies the information elements from the last Beacon frame (implementation note: if hidden_beacon_bss is set this struct doesn't own the beacon_ies, but they're just pointers to the ones from the hidden_beacon_bss struct) proberesp_ies the information elements from the last Probe Response frame hidden_beacon_bss in case this BSS struct represents a probe response from a BSS that hides the SSID in its beacon, this points to the BSS struct that holds the beacon data. beacon_ies is still valid, of course, and points to the same data as hidden_beacon_bss->beacon_ies in that case. signal signal strength value (type depends on the wiphy's signal_type) beacon_interval the beacon interval as from the frame capability the capability field in host byte order bssid[ETH_ALEN] BSSID of the BSS priv[0] private area for driver use, has at least wiphy->bss_priv_size bytes DESCRIPTION
This structure describes a BSS (which may also be a mesh network) for use in scan results and similar. AUTHOR
Johannes Berg <johannes@sipsolutions.net> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT CFG80211_BSS(9)