http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspxParts 1 and 2 of this series discussed how to determine whether an 802.1p tag was added to traffic, and how to modify the NDIS light-weight-filter (LWF) sample driver source code to accomplish this task. We do know that you're all very busy and not everyoneen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#10014512Tue, 25 May 2010 09:25:58 GMT91d46819-8472-40ad-a661-2c78acb4018c:10014512RaFi<p>Could you add the x64 binaries for Windows Serwer 2008 R2?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10014512" width="1" height="1">http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#6328584Sat, 17 Nov 2007 08:26:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:6328584wndpteam<p>Hi Tom,</p> <p>The sample driver is an NDIS6 Light Weight Filter (LWF) driver. NDIS-6 (and LWF) is new to Vista/Server 2008, and replaces NDIS-5 Intermediate (IM) drivers on XP. Therefore, you would have to port the LWF to an IM driver to build on XP. </p> <p>-- Gabe</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=6328584" width="1" height="1">http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#5680851Fri, 26 Oct 2007 01:59:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:5680851Tom<p>I notice this doesn't seem to build under Windows XP... any suggestions for that platform ?</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=5680851" width="1" height="1">http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#5384372Tue, 09 Oct 2007 21:20:20 GMT91d46819-8472-40ad-a661-2c78acb4018c:5384372Gabe Frost<P>Hi vpalkar,</P> <P>While VLAN ID is something the NIC is responsible for, the OS is responsible for setting the 802.1p priority; this is not something which should be set in the NIC. There is no way to set the 802.1p tag other than programmatically, i.e. the application must call either the administrative traffic control (TC) API (traffic.h), or the Qos2 API (qos2.h). Stay tuned for a post on how to do this using the TC API.</P> <P>You *should not* set the 802.1p tag in the miniport driver, as this is the responsibility of the OS. Doing so could cause loss of end-to-end connectivity and potential instability in the network stack if a user-mode application were to call a native QoS API such as described above.</P><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=5384372" width="1" height="1">http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#5224422Mon, 01 Oct 2007 18:15:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:5224422Rich Reynolds<p>Gabe, </p> <p>working source code examples are always helpful, please keep them coming.</p> <p>Thanks, Rich</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=5224422" width="1" height="1">http://blogs.msdn.com/b/wndp/archive/2007/09/14/detecting-802-1p-priority-tags-part-3.aspx#5124865Tue, 25 Sep 2007 20:04:29 GMT91d46819-8472-40ad-a661-2c78acb4018c:5124865vpalkar<p>I have a question about 802.1p.</p> <p>If I configure the vlan id for the miniport , the user prioirty is always 0 when I check the value NdisPacket8021qInfo.</p> <p>If I want to set the user priority , shall I configure it using group policy (gpedit.exe) ?</p> <p>How will it affect the overall system if I set the priority using proprty pages for miniport driver and modify the user priority for every packet , in the miniport driver ?</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=5124865" width="1" height="1">