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/29 10:52] – [6. [CO2] Implementing the Applications and Tools] enwan | qos_project [2017/11/29 11:32] – carine | ||
|---|---|---|---|
| Line 163: | Line 163: | ||
| Let's start with the application iperf: | Let's start with the application iperf: | ||
| - | * To activate iperf3: | + | - To activate iperf3: |
| - | - On the server side: <code bash> | + | * On the server side: iperf3 -s |
| - | - On the client side: <code bash> | + | * On the client side: iperf3 -c 192.168.200.192 |
| - | * To visualize UDP trafic with a specific bandwidth: | + | - To visualize UDP trafic with a specific bandwidth: |
| - | - On the client side: <code bash> | + | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M |
| Here we set the bandwidth with UDP to 2Mbit/s. | Here we set the bandwidth with UDP to 2Mbit/s. | ||
| Note that by default ,UDP sets the bandwidth to 1Mbit/s | Note that by default ,UDP sets the bandwidth to 1Mbit/s | ||
| - | * To extend the transmission time(second) as well as the number packets sent: | + | - To extend the transmission time(second) as well as the number packets sent: |
| - | - On the Client side: <code bash> | + | * On the Client side: iperf3 -c 192.168.200.192 -t 15 |
| Note that by default, iperf3 sets the time to 10 seconds | Note that by default, iperf3 sets the time to 10 seconds | ||
| - | * To reverse mode(server sends, client receives): | + | - To reverse mode(server sends, client receives): |
| - | - On the Client side: <code bash> | + | * On the Client side: iper3 -c 192.168.200.192 -R |
| - | | + | |
| - | | + | - To end multiple flows: |
| + | * On the Client | ||
| Here we are sending 2 flows in 1 min(60 seconds) | Here we are sending 2 flows in 1 min(60 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. | 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 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 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer