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:07] – [2. Addressing] samer | ||
---|---|---|---|
Line 12: | Line 12: | ||
- | [{{ :tp-link.jpg? | + | [{{ :glinet.jpg? |
+ | |||
+ | |||
+ | ===== -. 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. | ||
+ | [{{ : | ||
- | [{{ : | ||
===== -. 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 34: | ||
</ | </ | ||
- | Install matplotlib and fping | + | * Install matplotlib and fping |
<code bash> | <code bash> | ||
Line 42: | Line 47: | ||
</ | </ | ||
- | Install VLC as in this | + | * Install VLC as in this [[https:// |
- | [[https:// | + | |
- | + | ||
- | ===== -. 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. | + | |
- | [{{ : | + | |
===== -. Access and Configuration ===== | ===== -. Access and Configuration ===== | ||
Line 203: | Line 201: | ||
</ | </ | ||
===== -. [CO2] Implementing the Applications and Tools ===== | ===== -. [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: | + | <WRAP center round info 100%> |
- | + | * Accomplished | |
- | - To activate iperf3: | + | * 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: | + | </WRAP> |
- | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M | + | |
- | Here we set the bandwidth with UDP to 2Mbit/s. | + | |
- | Note that by default ,UDP sets the bandwidth to 1Mbit/s | + | |
- | - To extend | + | In order to describe and analyze |
- | * On the Client side: iperf3 | + | ==== -. iperf tool ==== |
- | Note that by default, iperf3 sets the time to 10 seconds | + | |
- | - To reverse mode(server sends, client receives): | + | 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: iper3 -c 192.168.200.192 -R | + | |
- | - To end multiple flows: | + | * To launch iperf3: |
- | | + | * On the server |
+ | * On the client side: '' | ||
- | Here we are sending 2 flows in 1 min(60 seconds) | + | * By default, |
- | 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. | + | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M |
- | Let's analyze flent application: | + | Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, UDP sets the bandwidth to 1Mbit/s. |
- | * 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 | + | |
+ | * To extend the transmission time(second) as well as the number packets sent: | ||
+ | * On the Client side: '' | ||
+ | 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: '' | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer