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] – [5. [CO1] Connecting the Platform] samer | qos_project [2017/12/07 14:07] – enwan | ||
---|---|---|---|
Line 12: | Line 12: | ||
- | [{{ :tp-link.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 28: | ||
</ | </ | ||
- | Install matplotlib and fping | + | * Install matplotlib and fping |
<code bash> | <code bash> | ||
Line 42: | Line 41: | ||
</ | </ | ||
- | Install VLC as in this | + | * Install VLC as in this [[https:// |
- | [[https:// | + | |
===== -. Addressing ===== | ===== -. 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. | + | The addressing plan of the platform is shown in Fig. 3. 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 202: | Line 200: | ||
192.168.200.0/ | 192.168.200.0/ | ||
</ | </ | ||
- | ===== -. [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: iperf3 -s | ||
- | * On the client side: iperf3 -c 192.168.200.192 | ||
- | |||
- | - To visualize 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 the transmission time(second) as well as the number packets sent: | ||
- | * 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 sends, client receives): | ||
- | * On the Client side: iper3 -c 192.168.200.192 -R | ||
- | |||
- | - To end multiple flows: | ||
- | * 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) | + | ==== -. iperf tool ==== |
- | 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: | + | Let us start with the 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 | + | |
+ | * To launch iperf3: | ||
+ | * On the server side: '' | ||
+ | * On the client side: '' | ||
+ | * 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 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: '' | ||
+ | ==== -.VLC Tool ==== | ||
- | ===== Extracts ===== | + | Let us now analyze the VLC application. VLC media player is a a highly portable multimedia player for various audio, video, streaming protocol. |
+ | * On the Server side: we open VLC media player : Go to media --> stream --> we add the desired video --> Stream --> Next --> for the new destination we choose UDP legacy then we click on add --> we add the destination IP address 192.168.100.111 (client) and the port number 1234 --> next --> we uncheck the active transcoding --> next --> stream. | ||
+ | * On the client side: we open VLC and then we click on play--> go to network and specify the network URL : udp:// | ||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer