Differences

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

--- qos_project [2017/11/29 11:02] – [6. [CO2] Implementing the Applications and Tools] enwan
+++ qos_project [2017/12/06 11:03] – [5.2. Flent Tool] enwan
@@ Line 12: / Line 12: @@
-[{{ :tp-link.jpg?nolink&150 | Figure 1. GL-iNet 6461 wireless router}}]
+[{{ :glinet.jpg?nolink&150 | Figure 1. GL-iNet 6461 wireless router}}][{{ :tp-link.jpg?nolink&150 | Figure 2. TP-Link WR741nd wireless router}}]
-[{{ :glinet.jpg?nolink&150 | Figure 2. TP-Link WR741nd wireless router}}]
 ===== -. Software =====
 The following tools can help in assessing the QoS on the platform:
-Install and compile netperf:
+  * Install and compile netperf:
 <code bash>
 wget https://github.com/HewlettPackard/netperf/archive/master.zip
@@ Line 29: / Line 28: @@
 </code>
-Install matplotlib and fping
+  * Install matplotlib and fping
 <code bash>
@@ Line 42: / Line 41: @@
 </code>
-Install VLC as in this
+  * Install VLC as in this [[https://thepi.io/how-to-compile-vlc-media-player-with-hardware-acceleration-for-the-raspberry-pi/|tutorial]].
-[[https://thepi.io/how-to-compile-vlc-media-player-with-hardware-acceleration-for-the-raspberry-pi/|tutorial]].
 ===== -. Addressing =====
-the addressing plan of the platform is shown in Fig. 2. Both routers have static addresses on their wan and lan interfaces. DHCP is activated on the LAN interfaces and static leases are configured so as to obtain the addresses on the terminals according to the figure.
+The addressing plan of the platform is shown in Fig. 3. Both routers have static addresses on their wan and lan interfaces. DHCP is activated on the LAN interfaces and static leases are configured so as to obtain the addresses on the terminals according to the figure.
-[{{ :qos-project.png?nolink&600 | Figure 2. Addressing plan for QoS platform}}]
+[{{ :qos-project.png?nolink&600 | Figure 3. Addressing plan for QoS platform}}]
 ===== -. Access and Configuration =====
@@ Line 158: / Line 156: @@
 </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.
-- To activate iperf3:
-	    * On the server side: iperf3 -s
-	    * On the client side: iperf3 -c 192.168.200.192
-- To visualize UDP trafic with a specific bandwidth:
-	    * 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:
-	    * 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):
-	    * On the Client side: iper3 -c 192.168.200.192 -R
-- To end multiple flows:
-	    * 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)
-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.
-===== Extracts =====
-#On TPlink router
 <file /etc/config/dhcp>
-config dnsmasq
-        option domainneeded '1'
-        option boguspriv '1'
-        option filterwin2k '0'
-        option localise_queries '1'
-        option rebind_protection '1'
-        option rebind_localhost '1'
-        option local '/lan/'
-        option domain 'lan'
-        option expandhosts '1'
-        option nonegcache '0'
-        option authoritative '1'
-        option readethers '1'
-        option leasefile '/tmp/dhcp.leases'
-        option resolvfile '/tmp/resolv.conf.auto'
-        option localservice '1'
 config dhcp 'lan'
         option interface 'lan'
@@ Line 213: / Line 167: @@
         option dhcpv6 'server'
         option ra 'server'
-config dhcp 'wan'
-        option interface 'wan'
-        option ignore '1'
-config odhcpd 'odhcpd'
-        option maindhcp '0'
-        option leasefile '/tmp/hosts/odhcpd'
-        option leasetrigger '/usr/sbin/odhcpd-update'
 config host
@@ Line 232: / Line 177: @@
         option mac 'b8:27:eb:20:aa:54'
         option ip '192.168.200.193'
-</file>
-# DHCP configuration on router GL-iNet:
-<file /etc/config/dhcp>
-config dnsmasq
-	option domainneeded '1'
-	option boguspriv '1'
-	option localise_queries '1'
-	option rebind_protection '1'
-	option rebind_localhost '1'
-	option local '/lan/'
-	option domain 'lan'
-	option expandhosts '1'
-	option authoritative '1'
-	option readethers '1'
-	option leasefile '/tmp/dhcp.leases'
-	option resolvfile '/tmp/resolv.conf.auto'
-config dhcp 'lan'
-	option interface 'lan'
-	option start '100'
-	option limit '150'
-	option leasetime '12h'
-	option dhcpv6 'server'
-	option ra 'server'
-	option ra_management '1'
-config dhcp 'wan'
-	option interface 'wan'
-	option ignore '1'
-config odhcpd 'odhcpd'
-	option maindhcp '0'
-	option leasefile '/tmp/hosts/odhcpd'
-	option leasetrigger '/usr/sbin/odhcpd-update'
-config dhcp
-	option start '100'
-	option leasetime '12h'
-	option limit '150'
-	option interface 'eth1'
-config domain 'localhost'
-	option name 'console.gl-inet.com'
-	option ip '192.168.8.1'
 </file>
-#ifconfig on raspberry pi2
+Finally, we verify the routing and addressing on the Raspberry Pi devices using ''ifconfig'' (or ''ip addr show'') and ''ip route'' commands.
 <code bash>
@@ Line 292: / Line 193: @@
           collisions:0 txqueuelen:1000
           RX bytes:229130 (223.7 KiB)  TX bytes:121127 (118.2 KiB)
-lo        Link encap:Local Loopback
-          inet addr:127.0.0.1  Mask:255.0.0.0
-          inet6 addr: ::1/128 Scope:Host
-          UP LOOPBACK RUNNING  MTU:65536  Metric:1
-          RX packets:221 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:221 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1
-          RX bytes:20606 (20.1 KiB)  TX bytes:20606 (20.1 KiB)
 </code>
-#ifconfig on raspberry pi3
-<code bash>
-pi@raspberrypi:~ $ ifconfig
-eth0      Link encap:Ethernet  HWaddr b8:27:eb:20:aa:54
-          inet addr:192.168.200.193  Bcast:192.168.200.255  Mask:255.255.255.0
-          inet6 addr: fe80::c7d8:36cf:a404:2c5/64 Scope:Link
-          inet6 addr: fdd5:bc83:a776:0:7379:7bf5:f8c5:b6ff/64 Scope:Global
-          inet6 addr: fdd5:bc83:a776::193/128 Scope:Global
-          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-          RX packets:745 errors:0 dropped:3 overruns:0 frame:0
-          TX packets:394 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000
-          RX bytes:66979 (65.4 KiB)  TX bytes:48816 (47.6 KiB)
-lo        Link encap:Local Loopback
-          inet addr:127.0.0.1  Mask:255.0.0.0
-          inet6 addr: ::1/128 Scope:Host
-          UP LOOPBACK RUNNING  MTU:65536  Metric:1
-          RX packets:256 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1
-          RX bytes:20736 (20.2 KiB)  TX bytes:20736 (20.2 KiB)
-</code>
-#ip route on raspberry pi2
 <code bash>
@@ Line 335: / Line 200: @@
 .168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.192  metric                                                                                                                                                              202
 </code>
-#ip route on raspberry pi3
-<code bash>
+==== -. iperf tool ====
-pi@raspberrypi:~ $ ip route
-default via 192.168.200.1 dev eth0  metric 202
+Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool.
-.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.193  metric 202
-</code>
+  * 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.
+  * 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
+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:
+     * On the Client side: ''iperf3 -c 192.168.200.192 -t 15''
+Note that by default, iperf3 sets the time to 10 seconds.
+  * 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 [[ https://flent.org/index.html | Flent]] application. Flent is a network benchmarking tools which allows to easily run network tests.
+  * 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''
+===== -. [CO3] Shaping the Traffic  =====
+# We first tried to limit the bandwidth using the following command "cbq" but it didn't work since cbq is not installed on the HP-PC:
+<code bash> tc qdisc add dev eth1 root handle 1: cbq avpkt 1000 bandwidth 8mbit <code>
+# On the Wan interface "eth0" of the router GL-iNet, the following command is used in order to limit the bandwidth of the outgoing traffic :
+<code bash> tc qdisc add dev eth0 root tbf rate 8000kbit burst 10kb latency 50ms <code>
+# To verify the result of the configuration we used :
+<code bash> tc qdisc ls <code>
+#After streaming VLC traffic and iperf UDP traffic with 6mbps to visualize the impact of the used command we noticed that the offered bandwidth is still the same 100 Mbps, therefore the same configuration should be done on the router TP-Link :
+<code bash> tc qdisc add dev eth1 root tbf rate 8000kbit burst 10kb latency 50ms <code>
+# Now the link between the two routers has a bandwidth of 8 Mbps for both the incoming and outgoing traffic on them.
+# In order to visualize the impact on the VLC video streamed from pi3 we generated UDP traffic from pi2 with 6mbps. The VLC video is affected giving that images of the video are pixelized
+# If we want to apply this feature in one direction we have to remove the limitation of the bandwidth on one of the routers(in our case we applied it on GL-iNet router):
+<code bash> tc qdisc del dev eth0 root <code>