Content deleted Content added
Citation bot (talk | contribs) Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 158/2141 |
m →Specification: add hyphen to read-only |
||
Line 32:
* NDIS 6.83: Windows 10, version 1903<ref name=MS/>
The traffic accepted by the NIC is controlled by an NDIS Miniport Driver<ref>{{Cite web|url=https://docs.microsoft.com/en-us/windows-hardware/drivers/network/deserialized-ndis-miniport-drivers|title = Deserialized NDIS Miniport Drivers - Windows drivers}}</ref> while various protocols, such as [[Internet Protocol Suite|TCP/IP]], are implemented by NDIS Protocol Drivers.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/windows-hardware/drivers/network/introduction-to-ndis-protocol-drivers|title = Introduction to NDIS Protocol Drivers - Windows drivers}}</ref> 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
NDIS Miniport drivers can also use [[Windows Driver Model]] interfaces to control network hardware.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/windows-hardware/drivers/network/ndis-miniport-drivers-with-a-wdm-lower-edge|title = NDIS Miniport Drivers with a WDM Lower Edge - Windows drivers}}</ref>
| |||