Differences

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

--- qos_project [2017/11/23 14:27] – [5. [CO1] Connecting the Platform] samer
+++ qos_project [2017/11/30 18:48] – [Extracts] samer
@@ Line 65: / Line 65: @@
 ===== -. [CO1] Connecting the Platform =====
-<WRAP center round tip 100%>
 Describe and analyze the basic steps for ensuring the platform connectivity: addressing and routing
+<WRAP center round info 100%>
   * Accomplished
       * Enable end-to-end communication
       * Analyse the addressing and routing (routing tables, DHCP, etc.)
   * Exceeded
-      * Identify the necessary commands and configurations for enabling end-to-end communications
+      * Identify the necessary commands and configurations for enabling end-to-end communication
 </WRAP>
+In order to analyse the addressing and routing on the platform, we need to look carefully on the interface configuration and routing tables of the different devices.
+Let us start with the routing devices. The routing table of the GL-iNet is shown using the command ''ip route'' and gives the following:
+<code bash>
+.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.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
+.0.0.2 of the TP-LINK router
+</code>
+Similarly, the routing table of the TP-LINK router shows the following:
+<code bash>
+.0.0.0/24 dev eth1  src 10.0.0.2 # connection to directly connected network 10.0.0.0/24
+.168.100.0/24 via 10.0.0.1 dev eth1 # static route to the network 192.168.100.0/24 via the interface
+.0.0.1 of the GL-iNet router
+.168.200.0/24 dev br-lan  src 192.168.200.1 # connection to our LAN 192.168.200.0/24
+</code>
+We note on the two routers that static routes are used in order to give access to the two LANs. Particularly, the configuration of the routers is given in the ''/etc/config/network'' files as on a typical OpenWrt system.
+As given below, the configuration of the TP-Link router shows the static addressing of the interface ''eth0'' (LAN interface) and the interface ''eth1'' (WAN interface). We also note the section ''route'' that configures a static routers towards the LAN connected to the TP-LINK router.
+<file bash /etc/config/network>
+#Configuration of LAN interface:
+config interface 'lan'
+        option type 'bridge'
+        option ifname 'eth0'
+        option proto 'static'
+        option ipaddr '192.168.200.1'
+        option netmask '255.255.255.0'
+        option ip6assign '60'
+#Configuration of WAN interface:
+config interface 'wan'
+        option ifname 'eth1'
+#       option proto 'dhcp'
+        option proto 'static'
+        option ipaddr '10.0.0.2'
+        option netmask '255.255.255.0'
+#Configuration of the static route :
+config route
+        option interface 'wan'
+        option target '192.168.100.0'
+        option netmask '255.255.255.0'
+        option gateway '10.0.0.1'
+</file>
+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>
+config interface 'lan'
+        option force_link '1'
+        option proto 'static'
+        option ipaddr '192.168.8.1'
+        option netmask '255.255.255.0'
+        option ip6assign '60'
+        option _orig_ifname 'eth1'
+        option _orig_bridge 'false'
+config interface 'wan'
+        option ifname 'eth0'
+        option hostname 'GL-iNet-b2d'
+        option proto 'static'
+        option ipaddr '10.0.0.1'
+        option netmask '255.255.255.0'
+config route
+        option interface 'wan'
+        option target '192.168.200.0'
+        option netmask '255.255.255.0'
+        option gateway '10.0.0.2'
+</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:
+- 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.
+Let's analyze flent application:
+            * 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
+===== Extracts =====