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/11/30 19:01] – [6. [CO2] Implementing the Applications and Tools] samer | ||
---|---|---|---|
Line 158: | Line 158: | ||
</ | </ | ||
+ | |||
+ | 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 ''/ | ||
+ | |||
+ | <file / | ||
+ | config dhcp ' | ||
+ | option interface ' | ||
+ | option start ' | ||
+ | option limit ' | ||
+ | option leasetime ' | ||
+ | option dhcpv6 ' | ||
+ | option ra ' | ||
+ | |||
+ | config host | ||
+ | option name ' | ||
+ | option mac ' | ||
+ | option ip ' | ||
+ | |||
+ | config host | ||
+ | option name ' | ||
+ | option mac ' | ||
+ | option ip ' | ||
+ | </ | ||
+ | |||
+ | Finally, we verify the routing and addressing on the Raspberry Pi devices using '' | ||
+ | |||
+ | <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 ===== | ===== -. [CO2] Implementing the Applications and Tools ===== | ||
- | In order to describe and analyze the basic steps for installing and using the tools and client/ | + | In order to describe and analyze the basic steps for installing and using the tools and client/ |
- | Let' | + | Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool. |
- | - To activate | + | * To launch |
- | | + | * On the server side: '' |
- | | + | * On the client side: '' |
- | - To visualize | + | * 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 |
- | Here we set the bandwidth with UDP to 2Mbit/s. | + | |
- | Note that by default ,UDP sets the bandwidth to 1Mbit/s | + | |
- | - To extend | + | Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, |
- | * On the Client side: iperf3 -c 192.168.200.192 -t 15 | + | |
- | Note that by default, | + | |
- | - To reverse mode(server sends, client receives): | + | * To extend the transmission time(second) as well as the number packets sent: |
- | * On the Client side: iper3 -c 192.168.200.192 -R | + | * On the Client side: '' |
- | - To end multiple flows: | + | Note that by default, iperf3 sets the time to 10 seconds. |
- | * On the Client side: iper3 -c 192.168.200.192 -P 2 -t 60 | + | |
- | Here we are sending 2 flows in 1 min(60 seconds) | + | * To use reverse mode (server sends the trafic and client receives): |
- | 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: '' |
+ | |||
+ | * To send multiple flows: | ||
+ | * On the Client side: '' | ||
+ | |||
+ | Here we are sending 2 flows in for one minute | ||
Let's analyze flent application: | Let's analyze flent application: | ||
Line 201: | Line 245: | ||
- | |||
- | |||
- | |||
- | ===== Extracts ===== | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer