Differences

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

--- qos_project [2017/11/30 18:48] – [Extracts] samer
+++ qos_project [2017/11/30 19:39] – [6. [CO2] Implementing the Applications and Tools] samer
@@ Line 158: / Line 158: @@
 </file>
-===== -. [CO2] Implementing the Applications and Tools =====
-In order to describe and analyze the basic steps for installing and using the tools and client/server applications, we need to look carefully to these 4 applications: iperf, flent, VLC, HTTP.
-Let's start with the application iperf:
+The two routers allocate IP addresses using DHCP. In order to facilitate the usage of the platform, fixed allocations are configured for the end hosts. This is configured in ''/etc/config/dhcp'' on each router as in the following.
+<file /etc/config/dhcp>
+config dhcp 'lan'
+        option interface 'lan'
+        option start '100'
+        option limit '150'
+        option leasetime '12h'
+        option dhcpv6 'server'
+        option ra 'server'
+config host
+        option name 'pi2'
+        option mac 'b8:27:eb:0f:f8:95'
+        option ip '192.168.200.192'
+config host
+        option name 'pi3'
+        option mac 'b8:27:eb:20:aa:54'
+        option ip '192.168.200.193'
+</file>
+Finally, we verify the routing and addressing on the Raspberry Pi devices using ''ifconfig'' (or ''ip addr show'') and ''ip route'' commands.
+<code bash>
+pi@raspberrypi:~ $ ifconfig
+eth0      Link encap:Ethernet  HWaddr b8:27:eb:0f:f8:95
+          inet addr:192.168.200.192  Bcast:192.168.200.255  Mask:255.255.255.0
+          inet6 addr: fdd5:bc83:a776:0:2377:1496:eb81:1433/64 Scope:Global
+          inet6 addr: fe80::20ae:134e:ae88:4bc5/64 Scope:Link
+          inet6 addr: fdd5:bc83:a776::192/128 Scope:Global
+          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
+          RX packets:1216 errors:0 dropped:3 overruns:0 frame:0
+          TX packets:983 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:229130 (223.7 KiB)  TX bytes:121127 (118.2 KiB)
+</code>
+<code bash>
+pi@raspberrypi:~ $ ip route
+default via 192.168.200.1 dev eth0  metric 202
+.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.192  metric                                                                                                                                                              202
+</code>
+===== -. [CO2] Implementing the Applications and Tools =====
+In order to describe and analyze the basic steps for installing and using the tools and client/server applications, we need to look carefully to these four applications: iperf, flent, VLC, HTTP.
-- To activate iperf3:
+==== -. iperf tool ====
-	    * On the server side: iperf3 -s
-	    * On the client side: iperf3 -c 192.168.200.192
-- To visualize UDP trafic with a specific bandwidth:
+Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool.
-	    * 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
-- To extend the transmission time(second) as well as the number packets sent:
+  * To launch iperf3:
-	    * On the Client side: iperf3 -c 192.168.200.192 -t 15
+    * On the server side: ''iperf3 -s''
-Note that  by default, iperf3 sets the time to 10 seconds
+    * On the client side: ''iperf3 -c 192.168.200.192'', where 192.168.200.192is the IP address of the server.
-- To reverse mode(server sends, client receives):
+  * By default, the trafic sent by iperf uses TCP. In order to send UDP trafic with a specific bandwidth:
-	    * On the Client side: iper3 -c 192.168.200.192 -R
+    * On the client side: iperf3 -c 192.168.200.192 -u -b 2M
-- To end multiple flows:
+Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, UDP sets the bandwidth to 1Mbit/s.
-	    * 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)
+  * To extend the transmission time(second) as well as the number packets sent:
-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.
+     * On the Client side: ''iperf3 -c 192.168.200.192 -t 15''
-Let's analyze flent application:
+Note that by default, iperf3 sets the time to 10 seconds.
-            * On the Server side: netserver &
--To visualize one TCP stream:
-            * On the Client side:  flent tcp_upload -p totals -l 60 -H 192.168.200.192 -t title2 -o test2.png
--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
+  * To use reverse mode (server sends the trafic and client receives):
+    * On the Client side: ''iper3 -c 192.168.200.192 -R''
+  * To send multiple flows:
+    * On the Client side: ''iper3 -c 192.168.200.192 -P 2 -t 60''
+Here we are sending two flows for one minute (60 seconds). We note that the average rate for the two flows can be different. However, this is not a fairness issue: we only need to extend the transmit time in order to have similar throughput for the two flows.
+==== -. Flent Tool ====
+Let us now analyze flent application:
+  * On the Server side: ''netserver &''
+  * To sent one TCP stream from the client to the server:
+    * On the Client side:  ''flent tcp_upload -p totals -l 60 -H 192.168.200.192 -t title2 -o test2.png''
+  * To send 12 TCP streams:
+     * On the Client side:  ''flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png''
@@ Line 204: / Line 247: @@
-===== Extracts =====