Differences

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

--- qos_project [2017/11/29 09:08] – [Extracts] enwan
+++ qos_project [2017/12/03 13:05] – [2. Software] samer
@@ 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 27: @@
 </code>
-Install matplotlib and fping
+  * Install matplotlib and fping
 <code bash>
@@ Line 42: / Line 40: @@
 </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]].
@@ Line 81: / Line 79: @@
 <code bash>
-.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.1 # Loopback address
+.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.1 # loopback address
-.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.1 # Connection to the wifi interface
+.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.1 # connection to the wifi interface
-.168.100.0/24 dev eth1  proto kernel  scope link  src 192.168.100.1 # Connection to the LAN 192.168.100.0/24
+.168.100.0/24 dev eth1  proto kernel  scope link  src 192.168.100.1 # connection to the LAN 192.168.100.0/24
-.168.200.0/24 via 10.0.0.2 dev eth0  proto static # Static route to the 192.168.200.0/24 network via the interface
+.168.200.0/24 via 10.0.0.2 dev eth0  proto static # static route to the 192.168.200.0/24 network via the interface
 .0.0.2 of the TP-LINK router
 </code>
@@ Line 128: / Line 126: @@
 </file>
-Similarly, the configuration of the GL-iNET router
+Similarly, the configuration of the GL-iNET router below shows the following:
+  * The WiFi interface is configured with a static IP address 192.168.8.1/24
+  * The WAN interface is configured with a static IP address 10.0.0.1/24
+  * A static route enables GL-iNET to reach the network 192.168.200.0/24 via 10.0.0.2 of the other router.
 <file bash /etc/config/network>
@@ Line 139: / Line 141: @@
         option _orig_ifname 'eth1'
         option _orig_bridge 'false'
-This interface (wifi) is configured with a static IP address 192.168.8.1/24
 config interface 'wan'
@@ Line 147: / Line 148: @@
         option ipaddr '10.0.0.1'
         option netmask '255.255.255.0'
-This interface (connected to the other router) is configured with a static IP address 10.0.0.1/24
 config route
@@ Line 154: / Line 154: @@
         option netmask '255.255.255.0'
         option gateway '10.0.0.2'
-This route enables GL-iNET to reach the network 192.168.200.0/24 via 10.0.0.2 of the other router.
+</file>
+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>
-===== 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 185: / 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 205: / Line 178: @@
         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 =====
+<WRAP center round info 100%>
+  * Accomplished
+      * Using the tools to obtain performance results of basic tests
+      * Wiki tutorial on the tools and applications
+  * Exceeded
+      * Installing tools on a new device
+</WRAP>
+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.
+==== -. iperf tool ====
+Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool.
+  * 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''