http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspxIn a previous post, I discussed traffic coloring. Modifications to a data packet such that the packet itself informs your network equipment that it requires handling different from normal packets such as best effort traffic. In other words, if you lookeden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#511042Tue, 10 Jan 2006 04:42:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:511042ChristianIs there a way to use VLANs with Windows like in Linux? <br> <br>e.g. a virtual adapter for each VLAN?http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#511812Thu, 12 Jan 2006 02:33:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:511812wndpteamThe Windows networking stack fully supports the 802.1Q tag, i.e. both UserPriority (as Mathias discusses in this post) as well as VlanId. However, no stack component (tcpip, etc.) ever acts on the VlanId field. Vendors, such as Intel, Broadcom, etc., implement VLANs in their miniport drivers in combination with NIC hardware. Thus, Windows enables ISVs to implement VLAN if they wish, but does not natively implement them. <br> <br>- Gabehttp://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#514563Thu, 19 Jan 2006 02:12:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:514563Arne Lovius*no stack component (tcpip, etc.) ever acts on the VlanId field* <br> <br>Thats because its an ethernet tag, and not a TCP/IP one. I've been using HPQ servers for some time now that have VLAN tagging support in their NIC drivers. <br> <br>There are ways in BSD (don't know about linux) to add VLAN tagging to *any NIC <br> <br>*most PCI nics that don't support VLAN tagging nativelyhttp://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#559659Fri, 24 Mar 2006 08:22:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:559659Windows Network Developer PlatformSome weeks ago I described 802.1p. It's a way to color traffic on your local network segment. If you...http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#650374Thu, 29 Jun 2006 05:34:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:650374Windows Network DevelopmentIn Windows Vista, a great deal of effort has gone into making it simple for network applications to take...http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#652005Fri, 30 Jun 2006 11:29:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:652005Windows Network DevelopmentMy previous post on WiFi QoS (WMM) discussed the four access classes (BG, BE, VI, and VO) available for...http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#652017Fri, 30 Jun 2006 11:36:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:652017Windows Network DevelopmentMy previous post on WiFi QoS (WMM) discussed the four access classes (BG, BE, VI, and VO) available for...http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#657205Wed, 05 Jul 2006 23:46:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:657205Windows Network DevelopmentA while back I wrote about the fundamentals of networking Quality of Service (QoS) including 802.1p and...http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#1632548Fri, 09 Feb 2007 10:08:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:1632548Windows Core Networking<p>The “Certified for Windows Vista” logo is comprised of requirements for myriad networking features and</p> http://blogs.msdn.com/wndp/archive/2006/01/09/511020.aspx#4812434Fri, 07 Sep 2007 19:51:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:4812434Windows Core Networking<p>Consider a case where a network application calls Windows QoS APIs to add a layer-2 IEEE 802.1Q UserPriority</p>