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 09:36] – [5. [CO1] Connecting the Platform] samer | qos_project [2017/11/29 10:57] – [6. [CO2] Implementing the Applications and Tools] enwan | ||
---|---|---|---|
Line 158: | Line 158: | ||
</ | </ | ||
+ | ===== -. [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: | ||
+ | |||
+ | * To activate iperf3: | ||
+ | * On the server side: <code bash> iperf3 -s </ | ||
+ | * On the client side: <code bash> iperf3 -c 192.168.200.192 </ | ||
+ | |||
+ | * To visualize UDP trafic with a specific bandwidth: | ||
+ | * On the client side: <code bash> 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 the transmission time(second) as well as the number packets sent: | ||
+ | * On the Client side: <code bash> iperf3 -c 192.168.200.192 -t 15 </ | ||
+ | Note that by default, iperf3 sets the time to 10 seconds | ||
+ | |||
+ | * To reverse mode(server sends, client receives): | ||
+ | * On the Client side: <code bash> iper3 -c 192.168.200.192 -R </ | ||
+ | * To send multiple flows: | ||
+ | * On the client side: <code bash> iper3 -c 192.168.200.192 -P 2 -t 60 </ | ||
+ | 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. | ||
+ | |||
+ | |||
===== Extracts ===== | ===== Extracts ===== | ||
#On TPlink router | #On TPlink router |
qos_project.txt · Last modified: 2021/08/28 09:58 by samer