Content deleted Content added
Link |
Alexceltare2 (talk | contribs) →Specification: added NetAdapterCx |
||
Line 42:
Another driver type is NDIS Intermediate Driver. Intermediate drivers sit in-between the MAC and IP layers and can control all traffic being accepted by the NIC. In practice, intermediate drivers implement both miniport and protocol interfaces. The miniport driver and protocol driver actually communicate with the corresponding miniport and protocol interfaces that reside in the intermediate driver. This design enables adding several chained intermediate drivers between the miniport and protocol drivers. Therefore, driver vendors cannot assume that the interface that they send traffic to is implemented by the last driver in the chain. In order to write applications using NDIS, one can use samples that accompany Microsoft's [[Windows Driver Kit]] (WDK). The "PassThru" sample is a good starting point for intermediate drivers as it implements all the necessary details required in this driver type, but just passes the traffic through to the next driver in the chain.
Since Windows 10 version 2004, a new driver framework for network adapters was created called Network Adapter WDF Class Extension (''NetAdapterCx'') which is meant to simply the driver development process.<ref>{{Cite web|date=22 May 2024|title=Network Adapter WDF Class Extension (NetAdapterCx)|url=https://learn.microsoft.com/en-us/windows-hardware/drivers/netcx/}}</ref>
== See also ==
| |||