NDIS Mux sample
in [Device Drivers]
|
From: uri habusha on 25 Dec 2007 11:39 I worked with NDIS 5.2 and try to create a VLAN. If I understand correctly I should use an intermediate driver for this propose, searching the WDK documentation points me to mux sample. I installed it on XP 64 bits, and after installation it appears multiple times one for each physical NIC I have on the machine. In addition I didn't succeeded to create multiple VLAN My questions are: - Do I really need an intermediate driver for creating a VLAN. My miniport driver know how to add the VLAN tag on sending and strip it on receive - Why when I install the MUX sample on specific LAN, it installed on all the LAN in my machine. - How can I create multiple VLANs on specific NIC Thanks in advance for your help Uri
From: Angie on 27 Dec 2007 15:35 The sample MUX driver, by default, will bind to all NIC installed in your system. if you want to bind to a particular NIC, you must modify the sample NIC to do so. After the MUX driver binding to a particular NIC, all traffics the MUX modified and send will flow to that particular NIC only. "uri habusha" <urih(a)mellanox.com> wrote in message news:uERixSxRIHA.1164(a)TK2MSFTNGP02.phx.gbl... >I worked with NDIS 5.2 and try to create a VLAN. If I understand correctly >I should use an intermediate driver for this propose, searching the WDK >documentation points me to mux sample. I installed it on XP 64 bits, and >after installation it appears multiple times one for each physical NIC I >have on the machine. In addition I didn't succeeded to create multiple VLAN > > My questions are: > > - Do I really need an intermediate driver for creating a VLAN. My miniport > driver know how to add the VLAN tag on sending and strip it on receive > > - Why when I install the MUX sample on specific LAN, it installed on all > the LAN in my machine. > > - How can I create multiple VLANs on specific NIC > > > > Thanks in advance for your help > > Uri > >
From: Stephan Wolf [MVP] on 1 Jan 2008 11:28 NDIS does have support for VLAN tags. Some network adapter (NDIS miniport) drivers actually do support VLAN tagging. They add VLAN information to send frames based on the out-of-band information (OOB) found in an NDIS_PACKET. Search for 'Ieee8021QInfo' and NDIS_MAC_OPTION_8021Q_VLAN as well as NDIS_MAC_OPTION_8021P_PRIORITY in the DDK/WDK docs. Note that IEEE 802.1Q and IEEE 802.1p information are both found in the VLAN tag. But most protocols like TCP/IP do not care about the VLAN tag (i.e., VLAN id and/or frame priority). That is, these protocols do not provide any VLAN information in any NDIS_PACKET that they send. So if either or both the protocol(s) and/or NIC miniport do not support VLAN tagging but you actually want to send VLAN tagged frames, you need to add the VLAN information yourself. This is exactly what the MUX sample does. It implements an NDIS "MUX" intermediate driver that can add a VLAN tag to send frames (if you define IEEE_VLAN_SUPPORT at compile time). See the .HTM files in the MUX sample for details. MUX creates a virtual adapter for each VLAN id. So if for instance TCP/ IP binds to a MUX virtual adapter with VLAN support, all frames sent by this adapter will have a VLAN tag with the respective VLAN id that you configure for it. Note again that the TCP/IP stack is completely unaware of any VLAN tags. If you need to control the bindings between physical NIC miniports and the protocol part of the MUX intermediate driver, then you need to modify the Notify Object that comes with the MUX sample. A NO has full control over all network bindings. It can prevent bindings from becoming both enabled and/or disabled. Stephan --- On Dec 25 2007, 5:39 pm, "uri habusha" <u...(a)mellanox.com> wrote: > I worked with NDIS 5.2 and try to create a VLAN. If I understand correctly I > should use an intermediate driver for this propose, searching the WDK > documentation points me to mux sample. I installed it on XP 64 bits, and > after installation it appears multiple times one for each physical NIC I > have on the machine. In addition I didn't succeeded to create multiple VLAN > > My questions are: > > - Do I really need an intermediate driver for creating a VLAN. My miniport > driver know how to add the VLAN tag on sending and strip it on receive > > - Why when I install the MUX sample on specific LAN, it installed on all the > LAN in my machine. > > - How can I create multiple VLANs on specific NIC > > Thanks in advance for your help > > Uri
|
Pages: 1 Prev: Device Status Code 37 (DriverEntry failure) spiteful problem. Next: MSVAD buffer size problem. |