Differences

This shows you the differences between two versions of the page.

--- qos_project [2017/11/30 18:56] – [6. [CO2] Implementing the Applications and Tools] samer
+++ qos_project [2017/11/30 19:01] – [6. [CO2] Implementing the Applications and Tools] samer
@@ Line 207: / Line 207: @@
 Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool.
-  * To activate iperf3:
+  * To launch iperf3:
     * On the server side: ''iperf3 -s''
     * On the client side: ''iperf3 -c 192.168.200.192'', where 192.168.200.192is the IP address of the server.
-- To visualize UDP trafic with a specific bandwidth:
+  * by default, the trafic sent by iperf uses TCP. In order to send UDP trafic with a specific bandwidth:
+    * On the client side: iperf3 -c 192.168.200.192 -u -b 2M
-  * On the client side: iperf3 -c 192.168.200.192 -u -b 2M
+Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, UDP sets the bandwidth to 1Mbit/s.
-Here we set the bandwidth with UDP to 2Mbit/s.
+  * To extend the transmission time(second) as well as the number packets sent:
-Note that by default ,UDP sets the bandwidth to 1Mbit/s
+     * On the Client side: ''iperf3 -c 192.168.200.192 -t 15''
-- To extend the transmission time(second) as well as the number packets sent:
+Note that by default, iperf3 sets the time to 10 seconds.
-	    * On the Client side: iperf3 -c 192.168.200.192 -t 15
-Note that  by default, iperf3 sets the time to 10 seconds
-- To reverse mode(server sends, client receives):
+  * To use reverse mode (server sends the trafic and client receives):
-	    * On the Client side: iper3 -c 192.168.200.192 -R
+    * On the Client side: ''iper3 -c 192.168.200.192 -R''
-- To end multiple flows:
+  * To send multiple flows:
-	    * On the Client side: iper3 -c 192.168.200.192 -P 2 -t 60
+    * On the Client side: ''iper3 -c 192.168.200.192 -P 2 -t 60''
-Here we are sending 2 flows in 1 min(60 seconds)
+Here we are sending 2 flows in for one minute (60 seconds). Note that we need to extend more the tx time in order to have similar throughput for the 2 flows so that we don't consider it as a fairness issue.
-Note that we need to extend more the tx time in order to have similar throughput for the 2 flows so that we don't consider it as a fairness issue.
 Let's analyze flent application:
@@ Line 237: / Line 235: @@
 -To visualize 12 TCP streams:
             * On the Client side:  flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png