qos_project
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
qos_project [2017/11/30 19:01] – [6. [CO2] Implementing the Applications and Tools] samer | qos_project [2017/12/06 11:01] – [6. [CO2] Implementing the Applications and Tools] enwan | ||
---|---|---|---|
Line 12: | Line 12: | ||
- | [{{ :tp-link.jpg? | + | [{{ :glinet.jpg? |
- | [{{ : | ||
===== -. Software ===== | ===== -. Software ===== | ||
The following tools can help in assessing the QoS on the platform: | The following tools can help in assessing the QoS on the platform: | ||
- | Install and compile netperf: | + | * Install and compile netperf: |
<code bash> | <code bash> | ||
wget https:// | wget https:// | ||
Line 29: | Line 28: | ||
</ | </ | ||
- | Install matplotlib and fping | + | * Install matplotlib and fping |
<code bash> | <code bash> | ||
Line 42: | Line 41: | ||
</ | </ | ||
- | Install VLC as in this | + | * Install VLC as in this [[https:// |
- | [[https:// | + | |
===== -. Addressing ===== | ===== -. 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. |
- | [{{ : | + | [{{ : |
===== -. Access and Configuration ===== | ===== -. Access and Configuration ===== | ||
Line 202: | Line 200: | ||
192.168.200.0/ | 192.168.200.0/ | ||
</ | </ | ||
- | ===== -. [CO2] Implementing | + | # Shaping |
- | In order to describe | + | # We first tried to limit the bandwidth using the following command " |
+ | <code bash> tc qdisc add dev eth1 root handle 1: cbq avpkt 1000 bandwidth 8mbit < | ||
+ | # On the Wan interface " | ||
+ | <code bash> tc qdisc add dev eth0 root tbf rate 8000kbit burst 10kb latency 50ms < | ||
+ | # To verify the result of the configuration we used : | ||
+ | <code bash> tc qdisc ls < | ||
+ | #After streaming VLC traffic | ||
+ | <code bash> tc qdisc add dev eth1 root tbf rate 8000kbit burst 10kb latency 50ms < | ||
+ | # Now the link between the two routers has a bandwidth of 8 Mbps for both the incoming | ||
+ | # 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 < | ||
+ | |||
+ | |||
+ | |||
+ | ==== -. 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. | Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool. | ||
Line 211: | Line 224: | ||
* On the client side: '' | * On the client side: '' | ||
- | * by default, the trafic sent by iperf uses TCP. In order to send UDP trafic with a specific bandwidth: | + | * 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 | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M | ||
Line 227: | Line 240: | ||
* On the Client side: '' | * On the Client side: '' | ||
- | Here we are sending | + | Here we are sending |
- | + | ||
- | 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 | + | |
+ | ==== -. Flent Tool ==== | ||
+ | Let us now analyze [[ https:// | ||
+ | * On the Server side: '' | ||
+ | * To sent one TCP stream from the client to the server: | ||
+ | * On the Client side: '' | ||
+ | * To send 12 TCP streams: | ||
+ | * On the Client side: '' | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer