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] – [Extracts] 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 158: | Line 156: | ||
</ | </ | ||
- | ===== -. [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: | + | 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 ''/ |
- | - To activate iperf3: | + | <file / |
- | * On the server | + | config dhcp ' |
- | * On the client side: iperf3 -c 192.168.200.192 | + | option interface ' |
+ | option start ' | ||
+ | option limit ' | ||
+ | option leasetime ' | ||
+ | option dhcpv6 'server' | ||
+ | | ||
- | - To visualize UDP trafic with a specific bandwidth: | + | config host |
- | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M | + | option name ' |
- | Here we set the bandwidth | + | option mac 'b8:27: |
- | Note that by default | + | |
+ | |||
+ | config host | ||
+ | option name ' | ||
+ | option mac ' | ||
+ | option ip ' | ||
+ | </ | ||
+ | |||
+ | Finally, we verify | ||
+ | |||
+ | <code bash> | ||
+ | pi@raspberrypi: | ||
+ | eth0 Link encap: | ||
+ | inet addr: | ||
+ | inet6 addr: fdd5: | ||
+ | inet6 addr: fe80:: | ||
+ | inet6 addr: fdd5: | ||
+ | UP BROADCAST RUNNING MULTICAST | ||
+ | RX packets: | ||
+ | TX packets:983 errors:0 dropped:0 overruns:0 carrier:0 | ||
+ | collisions: | ||
+ | RX bytes: | ||
+ | </ | ||
+ | |||
+ | <code bash> | ||
+ | pi@raspberrypi: | ||
+ | default via 192.168.200.1 dev eth0 metric 202 | ||
+ | 192.168.200.0/ | ||
+ | </ | ||
+ | # 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 | ||
+ | <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 | ||
+ | # 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 ==== | ||
- | - To extend | + | 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 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 | + | * To launch iperf3: |
- | | + | * On the server |
+ | * On the client | ||
- | - To end multiple flows: | + | * By default, the trafic sent by iperf uses TCP. In order to send UDP trafic with a specific bandwidth: |
- | | + | * On the client |
- | Here we are sending 2 flows in 1 min(60 seconds) | + | Here we set the bandwidth with UDP to 2Mbit/ |
- | 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: | + | |
- | | + | |
- | -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 | + | |
+ | 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: '' | ||
+ | * 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: '' | ||
Line 204: | Line 257: | ||
- | ===== Extracts ===== | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer