NDIS MUX Intermediate Drivers (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.
The number of virtual miniports exposed by a MUX intermediate driver can be different than the number of lower physical adapters that are bound to the driver. A MUX intermediate driver exposes virtual miniports in a one-to-n, n-to-one, or even an m-to-n relationship with underlying adapters. This results in complicated internal bindings and data paths.
In a one-to-n configuration, a single MUX intermediate driver can bind to many physical adapters below. Transport drivers bind to the virtual miniport of the MUX intermediate driver in the same way that they bind to nonvirtual miniports. The MUX intermediate driver repackages and passes down all requests and send packets that are submitted to the intermediate driver for a specific connection. A Load Balancing Failover (LBFO) driver is an example of this type of MUX intermediate driver. (For more information about LBFO solutions, see Load Balancing and Failover.)
The following figure illustrates a one-to-n MUX intermediate driver configuration:
.png)
In an n-to-one configuration, a MUX intermediate driver can expose many virtual miniports for a single physical adapter below. Overlying protocols bind to these virtual miniports of the MUX intermediate driver in the same way that they bind to nonvirtual miniports. The MUX intermediate driver handles requests and sends that are submitted to the driver for specific connections at each virtual miniport. The driver repackages and transfers these requests and sends down to the NDIS miniport driver for the bound physical adapter.
The following figure illustrates an n-to-one MUX intermediate driver configuration:
.png)
MUX intermediate drivers require a notify object DLL. When a MUX intermediate driver is initialized, its bindings are determined by the configuration established by its notify object DLL. For more information about installing MUX intermediate drivers, see MUX Intermediate Driver Installation.
The following are examples of n-to-one MUX intermediate drivers:
Windows ATM LAN Emulation is an intermediate driver that emulates Ethernet over an ATM network. This driver is similar in structure to the MUX sample. This driver is included in Windows 2000 and later versions of the operating system.
802 and proprietary virtual LANs are technologies that could be implemented as intermediate drivers similar to the MUX sample.
The MUX Intermediate Driver Sample is an n-to-one MUX intermediate driver. MUX creates multiple virtual miniports layered above a single underlying miniport.