Changes between Version 23 and Version 24 of GeniTmixSoftware


Ignore:
Timestamp:
03/14/13 20:25:45 (6 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixSoftware

    v23 v24  
    4848
    4949== Run ==
    50 Tmix generates traffic based on traffic measured on a real link.  This measurement is made by recording the headers of packets flowing over a link in either direction.  This protion of the Tmix software converts a network trace into a pair of Tmix input files which are then used to replay the traffic in GENI.    Currently only pcap format files are supported.  Pcap is a standard format, and most network traces should be easily output in or converted to the pcap format.  The Tmix software requires that packets be identified as incoming packets or outgoing packets.  Incoming packets are those entering an institution or machine over a link, and likewise outgoing packets are those leaving an institution or machine.  For an internal host surfing the web, the packets making up an HTTP request are outgoing packets, and   
     50As described above this software converts a network trace into a pair of Tmix input files which are then used to replay the traffic.  Currently only pcap format network trace files are supported for conversion into tmix input files.  Pcap is a standard format, and most network traces should be easily output in or converted to the pcap format.  The Tmix software requires that the direction of each packet be identified.  Packets can be either incoming packets or outgoing packets.  Incoming packets are those entering an institution or machine over a link, and likewise outgoing packets are those leaving an institution or machine.  When monitoring a link in the middle of a network, users may choose to arbitrarily label one direction as incoming and the other as outgoing.  Please note, the incoming and outgoing classification relates only to the direction of travel of the packet, and not to which side initiated the tcp connection (i.e. inbound connection).       
    5151
    5252Follow these steps to obtain a set of Tmix input files. These instructions assume you have installed binaries, and they are in your path, if not, augment the program names below with the paths to those binaries.   
    5353
    5454
     551. Obtain a pcap file or set of pcap files you wish to process into a pair of Tmix input files.   
    5556
    56 1. Identify a pcap file you wish to process into a pair of Tmix input files.   
     572. If not already split into 2 files, one containing incoming packets and one containing outgoing packets, split the pcap file.  This can be accomplished when all the subnets one one side of the connection are known by using the following commands:
     58{{{
     59tcpdump -r <toSplit.pcap> -w <incoming.pcap> dst net 155.90.0.0/16 or dst net 155.91.0.0/16 or ... or dst net 155.92.0.0/16
     60tcpdump -r <toSplit.pcap> -w <outgoing.pcap> src net 155.90.0.0/16 or src net 155.91.0.0/16 or ... or src net 155.92.0.0/16
     61}}}
     62where toSplit.pcap is the filename of the pcap to split, incoming.pcap and outgoing.pcap are the filenames of the resulting files, and all the subnet descriptions (155.90.0.0/16) are replaced with those relevant to the network one one side of the link where the trace was collected.  If the trace is anonymized subnet descriptions will need to work for the anonymized IPs.   
    5763
    58 2. Change to a directory in which your input files will be created (they will be put in a tmix-results sub-directory)
     643. Next, change to a directory in which your input files will be created (they will be put in a tmix-results sub-directory in this directory)
    5965
    60 3. Issue the foll
     663. Issue the following command to create