anchor.diff:  <4> Jitter of latency measurements.
   <5> Indication of number of errors (it is the sum of seq_too_high and seq_too_low. You can see description in Python API doc below). In the future it will be possible to 'zoom in', to see specific counters.
       For now, if you need to see specific counters, you can use the Python API.
  -    
  +
  +
  +[NOTE] 
  +=====================================================================
  +The global multiplier does not apply to this type of stream because those streams are process by software. so the rate would be constat
  +=====================================================================
  +   
   
   An example of API usage is as follows
   
  
positive.code: 
  
  ----
  <1> Assigned to PG ID 7
  <2> Assigned to PG ID 12
  
  The following command injects this to the console and uses the textual user interface (TUI) to display the TRex activity:
  
  
negative.code: * Packets must contain at least 16 bytes payload.
  * Each stream must have unique pg_id number. This also means that a given "latency collecting" stream can't be transmitted from two interfaces in parallel (internally it means that there are two streams). 
  * Maximum number of concurrent streams (with different pg_id) on which latency info may be collected: 128 (This is in addition to the streams which collect per stream statistics).
  * Global multiplier does not apply to this type of stream because those streams are process by software.   
  
  
  [NOTE] 
  =====================================================================
  IPv6 support is WIP, IPv6.flow_id would be the ID of the rule 
  =====================================================================
  
  
  Two examples follow, one using the console and the other using the Python API.
  
  *Console*::
  