anchor.diff:  blogs can be found  TRex link:https://communities.cisco.com/community/developer/trex/blog[blog]
   
   
  -=== Stateless Client GUI 
  +=== Stateless Client GUI
   
   * Cross-Platform - runs on Windows, Linux, Mac OS X
  -* Written in JavaFx use TRex RPC API 
  -* Scapy base packet builder to build any type of packet using GUI 
  +* Written in JavaFx use TRex RPC API
  +* Scapy base packet builder to build any type of packet using GUI
   **  very easy to add new protocols builders (using scapy)
   * Open and edit PCAP files, replay and save back
  -* visual latency/jitter/per stream statistic 
  +* visual latency/jitter/per stream statistic
   * Free
   
   Github is here link:https://github.com/cisco-system-traffic-generator/trex-stateless-gui[trex-stateless-gui]
  
positive.code: *** Packets per second (example: 14MPPS)
  *** L1/L2 bandwidth (example: 500Mb/sec)
  *** Interface link percentage (example: 10%)
  ** Support for basic HLTAPI-like profile definition 
  ** Action - stream can trigger a stream 
  * Interactive support - Fast Console,  GUI 
  * Statistics per interface
  * Statistics per stream done in hardware/software
  * Latency and Jitter per stream
  * Blazingly fast automation SDK support using Python 2.7/3.4
  * L2 Emulation Python event driven framework with examples of ARP/ICMP/ICMPv6/IPv6ND/DHCP and more. The framework can be extendable with new protocols
  * Capture/Monitor traffic with BPF filters - no need for Wireshark 
  * Capture network traffic by redirect the traffic to Wireshark
  * Functional tests 
  * PCAP file import/export 
  * Huge pcap file transmission  (e.g. 1TB pcap file) for DPI
  * Multi-user support 
  
  
  The following example shows three streams configured for Continuous, Burst, and Multi-burst traffic.
  
negative.code: more info can be found here link:https://trex-tgn.cisco.com/trex/doc/index.html[Documentation]
  
  
  === *Upcoming* TRex scalable TCP support
  
  With the new advanced scalable TCP support, TRex will use TCP layer for generating the L7 data. This will open the following new capabilities:
  
  * Ability to work when the DUT terminates the TCP stack (e.g. compress/uncompress). In this case there is a different TCP session on each side, but L7 data are *almost* the same.
  * Ability to work in either client mode or server mode. This way TRex client side could be installed in one physical location on the network and TRex server in another.
  * Performance and scale
  ** High bandwidth - 200gb/sec with many realistic flows (not one elephant flow )
  ** High connection rate - order of MCPS
  