Project Description 1. Impact of Queue Size on TCP Performance  Simulation 1: the default simulation using "fifth.cc" in /examples/tutorial  Simulation 2: the same setting, but with the queue size (or the size of droptail queue) at node S = 10 o How to change the queue size -- Need to change the value of an attribute called "MaxPackets" of a "DropTailQueue" class  Method 1: Use "Config::SetDefault" to change this value; refer to the following class reference and manual: https://www.nsnam.org/docs/release/3.25/doxygen/group__config.html#ga2e7882df8 49d8ba4aaad31c934c40c06 (Links to an external site.) https://www.nsnam.org/docs/release/3.25/manual/singlehtml/index.html (Links to an external site.)  Method 2: Use "PointToPointHelper::SetQueue" to change this value; refer to the following "PointToPointHelper class" reference https://www.nsnam.org/docs/release/3.25/doxygen/classns3_1_1_point_to_point_hel per.html#a546a5c9ae3c9eab0ea98b25fd41e3c95 (Links to an external site.) o Further Information  To know when the queue is created, check the constructor of the "PointToPointHelper" class: https://www.nsnam.org/docs/release/3.25/doxygen/point-to-pointhelper_8cc_source.html#l00041 (Links to an external site.)  To know the default value of "MaxPackets", check the "DropTailQueue" class reference: https://www.nsnam.org/docs/release/3.25/doxygen/classns3_1_1_drop_ta il_queue.html#details (Links to an external site.)  Simulation 3: the same setting, but with the queue size (or the size of droptail queue) at node S = 10 and application data rate at node S = 5 Mbps  In all simulations: the number of packets to be generated should be 100000 or more. ** Deliverables (simulation graphs along with your explanation):  congestion window vs. time  actual queue size vs. time  packet loss vs. time  throughput (or the rate of data received at node D) vs. time 2. Impact of Different RTT (Round Trip Time) on TCP Fairness  Setup the topology as shown in figure below -- two TCP connections: connection 1 (S1--D) and connection 2 (S2--D) Start each connection at time 1 sec and stop the connection at time 30 sec; application data rate at each source = 2.5 Mbps  Change the propagation delay between S2 and R from 2 ms to 10 ms  In all simulations: the number of packets to be generated should be 100000 or more; run simulation more than 30 sec. ** Deliverables (simulation graphs along with your explanation):  congestion window vs. time for both connections  throughput (or the rate of data received) vs. time for both connections 3. Impact of Cross UDP Traffic on TCP Performance  Setup the topology as shown in figure below -- one TCP connection (S1--D) and one UDP connection (S2--D)  Start TCP connection at time 5 sec and stop the connection at time 20 sec; application data rate at node S1 = 2.5 Mbps  Start UDP connection at time 1 sec and stop the connection at time 30 sec  Change the application data rate at node S2: 0.5 Mbps, 1.5 Mbps, 2.5 Mbps, 3.5 Mbps, 4.5 Mbps  In all simulations: the number of packets to be generated should be 100000 or more; run simulation more than 30 sec. ** Deliverables (simulation graphs along with your explanation):  congestion window vs. time for TCP connection  throughput (or the rate of data received) vs. time for both TCP and UDP connections4. Impact of Wireless Channel on TCP Performance  Setup the topology as shown in figure below.  For the configuration of an access point and two stations, use a sample code, which can be found in (Links to an external site.)https://www.nsnam.org/docs/release/3.25/models/html/wifi-user.html#infrastructureaccess-point-and-clients-wifinetdevice-configuration o Note that "LogDistancePropagationLossModel" is based on the free space loss equation with path loss exponent. See the following class reference for more details: https://www.nsnam.org/docs/release/3.25/doxygen/classns3_1_1_log_distance_ propagation_loss_model.html (Links to an external site.)  Create a single TCP flow from source (north station) to sink (east station) using "BulkSendApplication" for which "MaxBytes" is set to be zero. Refer to the following sample code for the TCP bulk transmission: https://www.nsnam.org/docs/release/3.25/doxygen/tcpbulk-send_8cc_source.html (Links to an external site.)  Start the TCP flow at time 0 sec and stop the flow at time 10 sec; simulation time is also 10 sec.  Change the distance between the access point and each station, and repeat the simulation. ** Deliverables (simulation graphs along with your explanation):  throughput measured by the end of simulation (the amount of data received at sink divided by the simulation time) vs. distance 5. Impact of Wireless Channel and Cross-Traffic on TCP Performance  Setup the topology as shown in figure below.  For the configuration of an access point and "four" stations, extend the above code.  Create one TCP flow from source 1 (north station) to sink 1 (east station) using BulkSendApplication for which MaxBytes is set to be zero.  Create another TCP flow from source 2 (west station) to sink 2 (south station) using BulkSendApplication for which MaxBytes is set to be zero.  Start both TCP flows at time 0 sec and stop them at time 10 sec; simulation time is also 10 sec.  Change the distance between the access point and each of the stations associated with the second flow, i.e., west and south stations, without changing the distances for east and north stations, and repeat the simulation.** Deliverables (simulation graphs along with your explanation):  throughput measured at each sink by the end of simulation (the amount of data received at each sink divided by the simulation time) vs. distance\