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 18:48] – [5. [CO1] Connecting the Platform] samer | qos_project [2017/12/14 09:09] – [6. [CO3] Shaping the Traffic] carine | ||
---|---|---|---|
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 the Applications and Tools ===== | ||
- | In order to describe and analyze the basic steps for installing and using the tools and client/ | ||
- | Let's start with the application | + | ==== -. iperf tool ==== |
- | - To activate iperf3: | + | Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool. |
- | * On the server side: iperf3 -s | + | |
- | * On the client side: iperf3 -c 192.168.200.192 | + | |
- | - To visualize UDP trafic with a specific bandwidth: | + | * To launch iperf3: |
- | | + | * On the server side: '' |
- | Here we set the bandwidth with UDP to 2Mbit/s. | + | |
- | Note that by default | + | |
- | - To extend | + | * By default, |
- | | + | * On the client |
- | Note that by default, iperf3 sets the time to 10 seconds | + | |
- | - To reverse mode(server sends, client receives): | + | Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, UDP sets the bandwidth to 1Mbit/s. |
- | * On the Client side: iper3 -c 192.168.200.192 -R | + | |
- | - To end multiple flows: | + | * To extend the transmission time(second) as well as the number packets sent: |
- | * On the Client side: iper3 -c 192.168.200.192 | + | * On the Client side: '' |
- | Here we are sending 2 flows in 1 min(60 seconds) | + | Note that by default, iperf3 sets the time to 10 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 Client side: '' |
- | -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 | + | |
+ | * To send multiple flows: | ||
+ | * On the Client side: '' | ||
+ | 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:// | ||
+ | * 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: '' | ||
+ | ==== -.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: '' | ||
+ | ===== -. [CO3] Shaping the Traffic | ||
+ | |||
+ | 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 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 </ | ||
+ | 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. | ||
- | ===== Extracts ===== | + | 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 </ | ||
+ | Exceeded : | ||
+ | We run flent with VLC and we noticed that the video wasn't affected because flent uses TCP. | ||
+ | ===== -. [PO2] Implementing QoS ===== | ||
+ | The QoS will be implemented on the outgoing interface (Wan) of the router TP-Link. | ||
+ | First, we have to check the existing configuration, | ||
+ | <code bash> tc qdisc ls </ | ||
+ | |||
+ | To delete the previous configurations we can use : | ||
+ | |||
+ | <code bash> tc qdisc del dev eth1 root </ | ||
+ | |||
+ |
qos_project.txt · Last modified: 2021/08/28 09:58 by samer