Wireless Operational Characteristics
The following chart summarizes the OIDs used to get or set the general operational characteristics of wireless WAN miniport drivers and/or their NICs.
| Q | S | Indication | Name |
|---|---|---|---|
M |
|||
M |
M |
M |
|
M |
|||
M |
M |
M |
|
M |
|||
M |
|||
M |
M |
M |
|
M |
M |
||
M |
M |
M |
|
M |
M |
M |
|
M |
|||
M |
M |
M |
|
M |
M |
M |
|
M |
M |
||
M |
M |
||
M |
|||
M |
M |
M |
|
M |
M |
M |
|
M |
M |
||
M |
M |
||
M |
|||
M |
|||
M |
M |
||
M |
M |
||
O |
O |
||
O |
|||
O |
|||
O |
|||
O |
|||
O |
|||
O |
O |
References for the set of network-type-dependent OID_WW_XXX follow those for the OID_WW_GEN_XXX.
Unless otherwise specified, the requesting protocol must allocate all buffer space and initialize any structures or pointers necessary to complete OID requests. Underlying NDIS drivers need only copy the data into the supplied buffers.
To account for differences in hardware architectures and structure packing, structure members must be aligned on an 8-byte (NDIS-defined type NDIS_PHYSICAL_ADDRESS) boundary and the sizeof operator in "C" (or an analogous function) must be used to calculate the lengths of structure elements.
Some network devices support external interfaces to configure the device. Therefore, it is possible for some objects to change dynamically, which is outside the control of the underlying miniport driver.
Note These OIDS are not available for use beginning with Windows Vista.