• Part 1: Network Analysis Tool [65 points total]: Construct a network analysis tool. You will test your tool by analyzing a few sets of packets captured during a set of test runs. The captured packets are stored as a sequence of records in a file with the format given below.

  
   0                             15                              31
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                        Capture Second                         |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                     Capture Microsecond                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                          IP Header                           ...
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                            Data                              ...
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  ...                                                             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                  Capture Second (Packet 2)                    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                Capture Microsecond (Packet 2)                 |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                      IP Header (Packet 2)                    ...
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  ...
  

  The capture second and capture microsecond is the time that the IP packet was captured from the network. Capture seconds are measured since the epoch on January 1, 1970. Microseconds is the number of microseconds within that second. This is the standard C timeval structure configuration.
  • A [15 points]: Display the number of IP packets arriving per second along with the time. The output should look something like this:

    Capture starts on: Fri Mar 11 05:18:37 EST 2005 and 006113 microseconds

    05:18:37 IP packets: 15

    05:18:38 IP packets: 28

    05:18:39 IP packets: 3

    . . .

    The above is an example that illustrates the time the capture started (the capture seconds and microseconds of the first IP packet). Each second of the capture displays the number of IP packets that were captured within that second. In the example above, 15 were captured within the first second, 28 in the second second, and 3 in the third second.
  • B [10 points]: Display only the number of TCP packets arriving per second along with the time. The output should look the same as Part A, but only TCP packets should be counted. The --TCP command line argument should instruct the analysis tool to perform this analysis.
  • C [10 points]: Display only the number of UDP packets arriving per second along with the time. The output should look the same as Part A, but only UDP packets should be counted. The --UDP command line argument should instruct the analysis tool to perform this analysis.
  • D [10 points]: Display only the number of UDP and TCP packets that match specific port criteria per second along with the time. This criteria should be given as a command line argument to the analysis tool. The port criteria is simply the source OR destination port matches a given number. The -p # command line argument should instruct the analysis tool to perform this analysis.
  • E [10 points]: Display the bytes of data (TCP and UDP) arriving per second along with the time. The -B command line argument should instruct the analysis tool to perform this analysis.
  • F [10 points]: When the end of the file is reached in the analysis tool, display a summary that includes the following:
    • Total length of capture in hours, minutes, seconds and microseconds
    • Total count of IP packets
    • Total count of TCP packets
    • Total count of UDP packets
    • Total count of data bytes
    • Average IP packets/second
    • Average TCP packets/second
    • Average UDP packets/second
    • Average data throughput (in bits/second)
  • Example Input for Testing: Here is an example input file to begin testing with. Additional files will be used for submissions. The contents of the example input file can be found here.
• Part 2: Protocol Design [35 points total]: Design a protocol to handle the transfer and management of song playlists. A user must have some form of authentication (username/password is acceptible). Each user may have numerous playlists and each must have a name. A user can create, delete, add songs to, and remove songs from a particular playlist. Each playlist has an implied order, but an undefined length. Each song on a playlist can be identified by Artist, Album/CD name, and Track Number. In addition, it should be possible to mark a playlist as random, meaning it has no implied order to it. You are responsible for designing a custom protocol to handle manipulating the playlist database given the basic requirements above. You may add additional functionality as you desire.

Notes: Your submissions must at least compile before any credit will be given. Submissions that do not compile will not be graded. Submissions submitted after the due date will not be graded. All work must be your own original work. To get partial credit for parts of the assignment, you must demonstrate that those pieces work by themselves. If you share code with others, you will be given a 0 for the assignment. This assignment set is worth 25% of your total grade.