anchor.diff:  2. To run the real product, check link:trex_manual.html#_download_and_installation[here] for hardware recommendation and
   installation instructions.
   
  -==== During OS installation, screen is skewed / error "out of range" / resolution not supported etc
  -
  -        * Fedora - during installation, choose "Troubleshooting" -> Install in basic graphic mode
  -        * Ubuntu - try Ubuntu server, which has textual installation
  -
  -==== How to determine relation between TRex ports and device under test ports
  -
  -Run the TRex with following command and check incoming packet on router interfaces:
  +==== During OS installation, screen is skewed / error "out of range" / resolution not supported etc.
  +
  +        * Fedora - during installation, choose "Troubleshooting" -> Install in basic graphic mode.
  +        * Ubuntu - try Ubuntu server, which has textual installation.
  +
  +==== How to determine relation between TRex ports and device under test ports?
  +
  +Run TRex with the below command and check incoming packet count on DUT interfaces.
   
   [source,bash]
   ----
           sudo ./t-rex-64 -f cap2/dns.yaml --lm 1 --lo -l 1000 -d 100
   ----
   
  -==== How to determine relation between Virtual OS ports and Hypervisor ports
  +Alternatively, you can run TRex in stateless mode, send traffic from each port, and look at the counters on the DUT interfaces.
  +
  +==== How to determine relation between Virtual OS ports and Hypervisor ports?
   
   Compare the MACs address + name of interface, for example:
   
   [source,bash]
   ----
  -* > ifconfig +
  -*eth0*    Link encap:Ethernet  *HWaddr 00:0c:29:2a:99:b2* +
  +> ifconfig
  +eth0    Link encap:Ethernet  HWaddr 00:0c:29:2a:99:b2
             ...
   
  -* > sudo ./dpdk_setup_ports.py -s +
  -*03:00.0* 'VMXNET3 Ethernet Controller' *if=eth0* drv=vmxnet3 unused=igb_uio
  +> sudo ./dpdk_setup_ports.py -s
  +03:00.0 'VMXNET3 Ethernet Controller' if=eth0 drv=vmxnet3 unused=igb_uio
   ----
   
   [NOTE]
  
positive.code: However, there is no way to create corrupted L1 fields (Like Ethernet FCS), since these are usually handled by the NIC hardware.
  
  ==== Why the performance is low?
  What would reduce the performance: 
  
  1. Many concurent streams.
  2. Complex field engine program.
  
negative.code: You can use the simulator. see link:trex_manual.html#_simulator[simulator]
  The output of the simulator can be loaded to Excel. The CPS can be tuned.
  
  ==== I want to have more acrive flows in TRex, how can I do this?
  Default maximum supported flows is 1M (From TRex prespective. DUT might have much more due to slower aging). When active flows reach higher number, you will get ``out of memory'' error message
  
  To increase the number of supported active flows, you should add ``dp_flows'' arg in config file ``memory'' section.
  Look link:trex_manual.html#_memory_section_configuration[here] for more info.
  
  ==== I want to have more active flows on the DUT, how can I do this?
  After stretching TRex to its maximum CPS capacity, consider the following: DUT will have much more active flows in case of a UDP flow due to the nature of aging (DUT does not know when the flow ends while TRex knows).
  In order to artificialy increse the length of the active flows in TRex, you can config larger IPG in the YAML file. This will cause each flow to last longer. Alternatively, you can increase IPG in your PCAP file as well.
  
  ==== I am getting an error: The number of ips should be at least number of threads.
  The range of clients and servers should be at least the number of threads. 
  The number of threads is equal to (number of port pairs) * (-c value)
  
  ==== Some of the incoming frames are of type SCTP. Why?
  Default latency packets are SCTP, you can omit the `-l <num>` from command line, or change it to ICMP. See the manual for more info.
   
  ===  Stateless 
  
  ==== How do I get started with stateless mode?
  