1) Network latency could be reserved
2) No need to bind multiple IP addresses and the number of client IP addresses 
   is unlimited
3) The maximum number of concurrent users is restricted to bandwidth, memory
   and CPU processing power
4) Only TCP-based applications that could be replayed are supported

1) Stress testing 
2) Comet
3) Performance testing

--with-debug      compile tcpburn with debug support (saved in a log file)
--pcap-send       send packets at the data link layer instead of the IP layer
--single          if intercept is configured with "--single" option, so does tcpburn
--comet           replay for comet applications

a) Install intercept on the assistant server
  git clone git://github.com/session-replay-tools/intercept.git
  cd intercept
  ./configure --single  
  make
  make install

b) Running intercept on the assistant server(root privilege or the CAP_NET_RAW capability is required):

  ./intercept -F <filter> -i <device,> 

  Note that the filter format is the same as the pcap filter.

  For example:

    ./intercept -i eth0 -F 'tcp and src port 80' -d

    Intercept will capture response packets of the TCP-based application which 
  listens on port 80 from device eth0 

  Set route commands appropriately to route response packets to the assistant server

  For example:

  Assume 65.135.233.161 is the IP address of the assistant server. We set the following
  route commands to route all responses to the 62.135.200.x's clients to the assistant
  server.

  route add -net 62.135.200.0 netmask 255.255.255.0 gw 65.135.233.161

a) Install tcpburn on the test server
  git clone git://github.com/session-replay-tools/tcpburn.git
  cd tcpburn

  if not comet scenarios
    ./configure --single 
  else
    ./configure --single --comet  
  endif

  make
  make install

b) Running tcpburn on the test server(root privilege or the CAP_NET_RAW capability is required):
  ./tcpburn -x historyServerPort-targetServerIP:targetServerPort -f <pcapfile,> 
            -s <intercept address> -u <user num> -c <ip range,>

  For example:

  Assume 65.135.233.160 is the IP address of the target server and 10.110.10.161 is the
  internal IP address of the assistant server and 65.135.233.161 is the external IP 
  address of the assistant server.
    ./tcpburn -x 80-65.135.233.160:80 -f /path/to/80.pcap -s 10.110.10.161 
              -u 10000 -c 62.135.200.x

  tcpburn extracts packets from 80.pcap file on dst port 80 and replays these to the
  target server 65.135.233.160 which runs the application listening on port 80. Total 
  sessions replayed are 10000 and client IP addresses used are belonging to 62.135.200.x
  series. tcpburn connects to the assistant server(10.110.10.161) for asking response 
  information.

1) All sessions are retrieved from pcap files and make sure the sessions in pcap files 
   are complete.
2) tcpburn uses raw socket to send packets by default, and if you want to avoid 
   ip_conntrack problems or get better performance, configure tcpburn with "--pcap-send"
   and refer to "./tcpburn -h" for how to set appropriate parameters for running.
3) The test server and the assistant server could share the same machine.
4) For comet applications, exclude publish sessions if they exist in pcap files.
5) tcpburn could not replay TCP-based sessions that could not be replayed, 
   such as SSL/TLS sessions
6) ip_forward should not be set on the assistant server.
7) Root privilege or the CAP_NET_RAW capability is required
8) Please execute "./tcpburn -h" or "./intercept -h" for more details.