OID_GEN_MEDIA_SUPPORTED
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
OID_GEN_MEDIA_SUPPORTED specifies the media types that the NIC can support, but not necessarily the media types that the NIC currently uses.
The following table shows the media types that are listed as a proper subset of the indicated system-defined values.
| Media type | Description |
|---|---|
NdisMedium802_3 |
Ethernet (802.3) |
NdisMedium802_5 |
Token Ring (802.5) |
NdisMediumWan |
WAN |
NdisMediumWirelessWan |
Various types of NdisWirelessXXX media |
NdisMediumIrda |
Infrared (IrDA) |
NdisMedium1394 |
IEEE 1394 bus |
Remarks
A wireless-WAN NIC driver must report its medium type as NdisMediumWirelessWan. However, such a miniport also must provide NdisWWDIXEthernetFrames header format to any bound protocol that selects this format. The miniport can provide its NIC's native header format as well. To support existing LAN-based protocols, the driver writer can provide an NDIS intermediate driver to "translate" a wireless NIC's native header formats and medium-specific information into a form that is understood by existing protocols.
Note that wireless-WAN and wireless-LAN media are different. A wireless-LAN network transfers packets that appear to the operating system and to NDIS as Ethernet packets. Currently, NDIS drivers should provide support for wireless-LAN networks as Ethernet networks. Such drivers declare their medium as NdisMedium802_3 and emulate Ethernet to higher-level NDIS drivers. For more information, see OID_GEN_PHYSICAL_MEDIUM.
If the underlying miniport returns NULL for this query or if an experimental media type is used, the driver must indicate receive operations using the NdisMIndicateReceivePacket function. Any protocol that is bound to such an underlying NIC driver receives all such indications, that is, the protocol cannot filter receive operations with OID_GEN_CURRENT_PACKET_FILTER.
Requirements
| Header | ntddndis.h |
| Windows Embedded CE | Windows CE .NET 4.0 and later |