Accessing OOB Information From a Connection-Oriented Protocol (NDIS 5.1)

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

A connection-oriented protocol driver can copy the information from the associated OOB block of an indicated receive packet using NDIS-supplied macros as follows:

  • Copy media-specific information using NDIS_GET_MEDIA_SPECIFIC_INFO.

  • Copy TimeSent using NDIS_GET_TIME_SENT.

  • Copy TimeReceived using NDIS_GET_TIME_RECEIVED.

Note   Most miniport drivers do not support TimeSent and TimeReceived.

 

TimeSentis the time a packet was sent by the miniport driver on the remote node, and is retrieved and stored by the underlying miniport driver on the local node, if available. TimeReceivedis the time that the incoming packet was received on the underlying NIC on the local node.

The current system time can be determined using NdisGetCurrentSystemTimeif the protocol converts these time stamps into another format.

A connection-oriented miniport driver might indicate the TimeReceivedfor a packet in the NIC's local time. To query a connection-oriented miniport driver's or MCM's local timing capabilities, a protocol driver calls NdisCoRequestwith OID_GEN_CO_GET_TIME_CAPS. To obtain the NIC's local time, a protocol driver calls NdisCoRequestwith OID_GEN_CO_GET_NETCARD_TIME.

 

 

Send comments about this topic to Microsoft