Network Driver Interface Specification: Difference between revisions

Revision as of 07:48, 2 October 2015

Revision as of 20:02, 18 May 2016

Line 24:

* NDIS 6.30: [[Windows 8]], [[Windows Server 2012]]

* NDIS 6.40: [[Windows 8.1]], [[Windows Server 2012 R2]]

* NDIS 106.50: [[Windows 10]], [[Windows Server 2016]]{{citation needed|reason=Unknown documentation|date=August 2015}}

* NDIS 6.60: [[Windows Server 2016]]

The traffic accepted by the NIC is controlled by an NDIS [[miniport]] Driver while various protocols, such as [[Internet Protocol Suite|TCP/IP]], are implemented by NDIS Protocol Drivers. A single miniport may be associated with one or more protocols. This means that traffic coming into the miniport may be received in parallel by several protocol drivers. For example, [[pcap|Winpcap]] adds a second protocol driver on the selected miniport in order to capture incoming packets. Furthermore, it is possible to simulate several virtual NICs by implementing virtual miniport drivers that send and receive traffic from a single physical NIC. One example of virtual miniport driver usage is to add virtual NICs, each with a different [[Virtual LAN]]. Because implementations cannot assume that other drivers received the same buffers, one must treat the incoming buffers as read only and a driver that changes the packet content must allocate its own buffers.