Wireless Data Networks, TLEN 5520/ECEN 5032Lab. #3Varun Vora, Martin HeusseDue in class: Apr. 22nd1 IntroductionIn this lab we will analyse the behavior of different types of traffic in different types of environmenton 802.11n. We will be using RUDE/CRUDE (respectively, Real time UDP Data Emitter and Collectorfor RUDE) for generating and analysing UDP traffic, while we will be using tcpmt/tcptarget forgenerating and analysing TCP traffic. Divide yourselves in three groups. The three environments inwhich testing shall be done are1. RF isolated room (opposite to Pecolab)2. Pecolab3. A Student’s residenceMultiple unicast streams will be generated on the same WiFi channel, which will enable us to analyse thethroughput and other performance measurement in a dense Wi-Fi network.2 Set up• The lab equipment will consist of one Desktop (server), 4 laptops (Clients), 4 Linksys WPC600Ncards, 1 WRT610N Linksys router and 1 Cat 5 (1000BASE-T) Ethernet cable. Make sure youtake all the equipment to the respective environment.• Connect the router to the Desktop using the Ethernet cable. You can use any ethernet slotexcept the one marked internet. Open a web browser on server and type 10.1.1.1 (IP address ofthe router). The router page opens. Make sure the frequency is set to 2.4GHz, mode is set to ”nonly” and channel bandwidth is set to 20MHz.1• Set the server’s IP address to 10.1.1.0 using ifconfig command• Plug in the Wifi cards on the 4 laptops, and place the laptops at roughly equal distance (5-7 feet)from the AP as shown in the figure belowFigure 1: 802.11n video testing in a RF isolated room at Univ. of Colorado.• Give the four clients IP addresses from 10.1.1.2 to 10.1.1.5.3 UDP experiments1. Use only 1 laptop, set its IP address to 10.1.1.2. This will be called client1. Make sure you canping the server (10.1.1.0). On client1, open a terminal. Open the scripts folder within the rudefolder on the client using cd /Desktop/rude/scripts. This is the folder in which all yourfiles must be saved. Now run the command crude -p 10001 -l temp. This command willmake client 1 listen on port 10001 and any packets it recieves, its statistics will be saved in the filetemp. Note that the file temp will be a binary file and is not readable.2. On the server, open the lab3 folder and open client1.cfg. This is the script on the server sidethat generates the UDP packets. The first group of number 0000 indicates the begin time in ms,in this case it means immediately, the next group of numbers 1001 indicate a flow id. This willbe useful to save files collected at the reciever. The convention used is 1001 means 1st type ofexperiment - UDP with 1 client. For UDP with 2 clients it will be called 1002 and so on. For the2nd type of experiment thats is UDP plus TCP with 1 TCP and x UDP clients, the flow id will be200x. The next group of numbers 3002 indicate the source port that is used to emit data. Then2the IP address and port number of client1 is specified. Constant indicates the type of flow, whichis CBR here with 1500 bytes per packet and 4167 packets per sec which gives 4167*1500*8 = 50Mbps. Finally, on the last line, 212400 indicates the end time in millisec.3. On the server, open a terminal and type rude -s /Desktop/lab3/client1.cfg ;[email protected] ”killall crude”. This command begins the packet transmission fromserver to client (remember client is already listening). The latter part of command kills crude onthe client1 as it does not stop listening automatically.4. Now, we have undecoded packet statistics on client1 saved in temp. Run crude -d temp>& 50_1UDP_client1. This will convert the binary file temp to file 50_1UDP_client1.Note, here there was only 1 client and hence 1 UDP stream, hence 1UDP in the name of file. Run./crude_jitter.pl 50_1UDP_client1 >& 50_1UDP_client1_jitter. This will savethe jitter observed in the _jitter file. Finally run ./crude_parse.pl 50_1UDP_client1.This will generate and save throughput statistics in a file data.flowid. Remember our flow id inthis case was 1001. Hence the throughput file generated will be data.10015. The files of interest are 50_1UDP_client1_jitter and data.1001.6. Now, turn on the 2nd laptop viz client2. Give it an ipaddress 10.1.1.3 using ifconfig.Again make sure you can ping the server, the AP and client1. Again open a terminal and go tothe scripts folder and run the crude command as mentioned in step 1.7. On the server, check client2.cfg. Note, the source port is different from the one used tosend packets to client1. We cannot use the same source port to send packets to different clients.In both client1.cfg and client2.cfg, change the flow id to 1002 from 1001, otherwise thefiles collected will overwrite the throughput you measured using 1 client only.8. Open another terminal window and type the command mentioned in step 3 except that insteadof client1 type client2 and instead of [email protected], type 10.1.1.3. Dont hit enter yet! Typethe command for the 1st client on the 1st terminal as mentioned in step 3, again do not hit enter.9. Hit enter at the same time on both the terminal windows on server (for client1 and for client2respectively). Thus, here the server is generating and sending packets simultaneously on twodifferent streams to two different client using two different source ports.10. After packets have been sent and recieved at the clients, process them and follow the naming con-ventions according to step 4 and 5. The files of interest would be 50_2UDP_client1_jitterand data.1002 on client1 and 50_2UDP_client2_jitter and data.1002 on client2.11. Continue in this manner for 3 and 4 Clients.34 TCP plus UDP experiments1. Do not change the physical setup of the network. In this set of experiments, we will have 1 client(TCPclient) continously doing TCP packet exchanges with the server, while we add 0, 1, 2 and 3UDP clients to the network. So the 1st experiment in this set would be only 1 TCP throughputmeasurement using ipmt. Save the throughput file as 50_0UDP1TCP_TCPclient.2. Perform the test again, but with a UDP stream going simultaneously with TCP stream. Save theTCP throughput on TCPclient as 50_1UDP1TCP_TCPclient and UDP throughput on client1as 50_1UDP1TCP_client1.3. Add 2 and 3 UDP streams to the 1 TCP stream and save the files according to the above nomen-clature.5 AnalysisBy now, you must have collected lot of data from 8 experiments (4 for UDP only and 4 for UDP+TCP).Import all these