DOT11_PHY_TYPE enumeration
Applies to: desktop apps only
The DOT11_PHY_TYPE enumeration defines an 802.11 PHY and media type.
Syntax
typedef enum _DOT11_PHY_TYPE {
dot11_phy_type_unknown = 0,
dot11_phy_type_any = 0,
dot11_phy_type_fhss = 1,
dot11_phy_type_dsss = 2,
dot11_phy_type_irbaseband = 3,
dot11_phy_type_ofdm = 4,
dot11_phy_type_hrdsss = 5,
dot11_phy_type_erp = 6,
dot11_phy_type_ht = 7,
dot11_phy_type_IHV_start = 0x80000000,
dot11_phy_type_IHV_end = 0xffffffff
} DOT11_PHY_TYPE, *PDOT11_PHY_TYPE;
Constants
- dot11_phy_type_unknown
-
Specifies an unknown or uninitialized PHY type.
- dot11_phy_type_any
-
Specifies any PHY type.
- dot11_phy_type_fhss
-
Specifies a frequency-hopping spread-spectrum (FHSS) PHY. Bluetooth devices can use FHSS or an adaptation of FHSS.
- dot11_phy_type_dsss
-
Specifies a direct sequence spread spectrum (DSSS) PHY type.
- dot11_phy_type_irbaseband
-
Specifies an infrared (IR) baseband PHY type.
- dot11_phy_type_ofdm
-
Specifies an orthogonal frequency division multiplexing (OFDM) PHY type. 802.11a devices can use OFDM.
- dot11_phy_type_hrdsss
-
Specifies a high-rate DSSS (HRDSSS) PHY type.
- dot11_phy_type_erp
-
Specifies an extended rate PHY type (ERP). 802.11g devices can use ERP.
- dot11_phy_type_ht
-
Specifies the 802.11n PHY type.
- dot11_phy_type_IHV_start
-
Specifies the start of the range that is used to define PHY types that are developed by an independent hardware vendor (IHV).
- dot11_phy_type_IHV_end
-
Specifies the start of the range that is used to define PHY types that are developed by an independent hardware vendor (IHV).
Remarks
An IHV can assign a value for its proprietary PHY types from dot11_phy_type_IHV_start through dot11_phy_type_IHV_end. The IHV must assign a unique number from this range for each of its proprietary PHY types.
Requirements
|
Minimum supported client | Windows Vista, Windows XP with SP3 |
|---|---|
|
Minimum supported server | Windows Server 2008 |
|
Redistributable | Wireless LAN API for Windows XP with SP2 |
|
Header |
|
See also
Send comments about this topic to Microsoft
Build date: 2/3/2012
