wikiroute

networking recipes

User Tools

Site Tools


qos_project

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
qos_project [2017/12/03 13:07] – [2. Addressing] samerqos_project [2017/12/07 14:07] enwan
Line 13: Line 13:
  
 [{{ :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 1. GL-iNet 6461 wireless router}}][{{ :tp-link.jpg?nolink&150 | Figure 2. TP-Link WR741nd wireless router}}]
- 
- 
-===== -. Addressing ===== 
- 
-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 3. Addressing plan for QoS platform}}] 
  
 ===== -. Software ===== ===== -. Software =====
Line 48: Line 42:
  
   * Install VLC as in this [[https://thepi.io/how-to-compile-vlc-media-player-with-hardware-acceleration-for-the-raspberry-pi/|tutorial]].   * Install VLC as in this [[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. 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 3. Addressing plan for QoS platform}}]
 +
 +
 ===== -. Access and Configuration ===== ===== -. Access and Configuration =====
  
Line 200: Line 200:
 192.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.192  metric                                                                                                                                                              202 192.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.192  metric                                                                                                                                                              202
 </code> </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 ==== ==== -. iperf tool ====
  
Line 247: Line 237:
      * On the Client side:  ''flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png''      * On the Client side:  ''flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png''
  
 +==== -.VLC Tool ====
  
 +Let us now analyze the VLC application. VLC media player is a a highly portable multimedia player for various audio, video, streaming protocol. 
  
- +  * On the Server side: we open VLC media player : Go to media --> stream --> we add the desired video --> Stream --> Next --> for the new destination we choose UDP legacy then we click on add --> we add the destination IP address 192.168.100.111 (client) and the port number 1234 --> next --> we uncheck the active transcoding --> next --> stream. 
- +  * On the client side: we open VLC and then we click on play--> go to network and specify the network URL : udp://@:1234 and finally we click on play. 
- +
  
  
  
qos_project.txt · Last modified: 2021/08/28 09:58 by samer