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/03 13:06] – [2. Software] samer | ||
---|---|---|---|
Line 12: | Line 12: | ||
- | [{{ :tp-link.jpg? | + | [{{ :glinet.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 27: | ||
</ | </ | ||
- | Install matplotlib and fping | + | * Install matplotlib and fping |
<code bash> | <code bash> | ||
Line 42: | Line 40: | ||
</ | </ | ||
- | Install VLC as in this | + | * Install VLC as in this [[https:// |
- | [[https:// | + | |
===== -. Addressing ===== | ===== -. Addressing ===== | ||
Line 158: | Line 155: | ||
</ | </ | ||
- | ===== -. [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' | ||
+ | option ra ' | ||
+ | |||
+ | config host | ||
+ | option name ' | ||
+ | option mac 'b8:27: | ||
+ | | ||
+ | |||
+ | 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/ | ||
+ | </ | ||
+ | ===== -. [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 | ||
+ | </ | ||
- | - To visualize UDP trafic with a specific bandwidth: | + | In order to describe and analyze the basic steps for installing and using the tools and client/server applications, |
- | * On the client | + | ==== -. iperf tool ==== |
- | Here we set the bandwidth with UDP to 2Mbit/s. | + | |
- | Note that by default ,UDP sets the bandwidth to 1Mbit/s | + | |
- | - 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 251: | ||
- | ===== Extracts ===== | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer