From Nsnam
Revision as of 15:04, 9 August 2016 by Wasiq (Talk | contribs) (Progress)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

TCP Evaluation Suite - Summer Project 2016

  • Abstract: The TCP evaluation Suite aims to provide a research friendly interface to compare various TCP extensions under different environment conditions and different scenarios.This project aims to tackle various issues in the TCP Evaluation Suite in ns-3 and to add more functionalities.
  • About Me: I'm a 3rd year B.E undergraduate (Computer Science) studying in Sir M. Visvesvaraya Institute of Technology-Bangalore, India.


  • WIRELESS LAN I intend to BUILD a WIRELESS LAN scenario helper according to the standards presented by the /RFC

Time line

June 14 - June 21 = Outline the wireless lan module to be implemented.

June 21 - July 07 = Read up on required papers and RFC's

July 07 - July 14 = Week required to outline the TCP eval module as a whole.

July 14 -July 21= Begin coding the Wireless Access Helper.

July 21 = Submit a prototype for feedback and review.

July 21 - August 1 = Continue working on the wireless access helper. Study how to integrate the Evaluation works with my helper.
August 1 - August 7 = Buffer week for documentations and delays.

August 7 = Submit Wireless helper for review.

August 7 - August 21 = Write the scenario dependent on the wireless helper.
August 21 - August 28 = Cleanup code and submit.


Week 0:Introductions and formalities.

Week 1: This week was spend reading through the different material required to begin this project. Going through the RFC and understanding how the model should be implemented.

Week 2: The wireless lan module is to be developed as a helper class. With an initial assessment i see that the does implement a similar scenario but all the nodes there are wired. The base files and wireless-lan-helper.h have been created and push to github.

Week 3: This week was mostly spend deciding on how the TCP Eval suite would be structured as a whole. Different module designs were discussed, One important design being the placement of the different scenarios that would be created . Each topology type has different examples or scenarios that can be created or used to test the stability and flexibility of TCP variants. This can account to a lot of individual files that would make it harder to discern the structure of the module. It was finally decided to put the topology creators in the model directory and all the scenarios in the example directory. only the tmix traces will be put in a separate file within the example directory.

Week 4:The wireless access topology creator has a create wireless access topology function that takes in the number of wired and wireless leaf nodes.A Point to point helper is used to create the central link as well as connect the wired leaf nodes. After which we use a yans wifi helper to connect and establish the wifi leaf nodes. Further development is in progress.

Week 5:The headers were created for both the wireless dumbbell helper as well as the wireless access scenario. The number of leaf nodes is taken by adding the ftp flows given as input during the run. A get left function is also addded in the wireless dumbbell scenario to give us the left bottleneck node. The wireless access topology sets the traffic parameters and then calls for the wireless dumbbell creator.


  • Mid Term Due to the proposal on the restructuring of the architecture of the tcp eval suite the milestone has been altered and pushed to the start of august.This milestone is the creation of a wireless topology helper which will be used to develop the wireless lan scenario later on.

Code Repository

The Code is currently hosted on github. Link: