XPost: comp.dcom.lans.ethernet   
   From: grahn+nntp@snipabacken.se   
      
   ["Followup-To:" header set to comp.protocols.tcp-ip.]   
   On Wed, 2011-09-07, Mark wrote:   
   > Thanks everyone for input. I was rather looking for the principles of   
   > testing of specific QoS features, for example, I can assign a 802.1q   
   > priority value to a specific output queue (with low, mid or high priority).   
   > So, for this particular test case the question is: how, having just a couple   
   > of PCs and a L2 development design in between, to verify that the L2   
   > hardware really does what I ask it to, i.e. placing a frame with COS   
   > priority value 2 to TX queue 0 (as example), and a frame with COS value 7 to   
   > TX queue 3.   
   >   
   > (I'm trying to implement such functionality on the hardware and want to make   
   > sure that it does what it claims in datasheet).   
      
   That's not functionality; that's stuff that is internal to the chip,   
   and can only be verified by looking at its counters if it has any.   
      
   The /functionality/ would be how traffic with different COS values   
   affect the dropping of each other during heavy load.   
      
   I suppose you could set up something like this:   
      
     host A: addr A ----- SUT ------ addr B0 : host B   
                                     addr B1   
                                     addr B2   
      
   And add iptables rules to rewrite COS on traffic   
   to B0, B1 and B2.   
      
   /Jorgen   
      
   --   
     // Jorgen Grahn    O  o   .   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)