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:04] – [5. [CO1] Connecting the Platform] samer | qos_project [2017/11/30 18:48] – [Extracts] samer | ||
---|---|---|---|
Line 81: | Line 81: | ||
<code bash> | <code bash> | ||
- | 10.0.0.0/24 dev eth0 proto kernel | + | 10.0.0.0/24 dev eth0 proto kernel |
- | 192.168.8.0/ | + | 192.168.8.0/ |
- | 192.168.100.0/ | + | 192.168.100.0/ |
- | 192.168.200.0/ | + | 192.168.200.0/ |
10.0.0.2 of the TP-LINK router | 10.0.0.2 of the TP-LINK router | ||
</ | </ | ||
Line 126: | Line 126: | ||
option netmask ' | option netmask ' | ||
option gateway ' | option gateway ' | ||
- | |||
</ | </ | ||
- | <file bash / | + | Similarly, the configuration |
- | # | + | |
- | All the network configuration on both routers (routing & addressing) are taken from / | + | |
- | On router | + | * The WiFi interface is configured with a static IP address 192.168.8.1/ |
+ | * The WAN interface is configured with a static IP address 10.0.0.1/ | ||
+ | * A static route enables | ||
+ | <file bash / | ||
config interface ' | config interface ' | ||
option force_link ' | option force_link ' | ||
Line 143: | Line 143: | ||
option _orig_ifname ' | option _orig_ifname ' | ||
option _orig_bridge ' | option _orig_bridge ' | ||
- | This interface (wifi) is configured with a static IP address 192.168.8.1/ | ||
config interface ' | config interface ' | ||
Line 151: | Line 150: | ||
option ipaddr ' | option ipaddr ' | ||
option netmask ' | option netmask ' | ||
- | This interface (connected to the other router) is configured with a static IP address 10.0.0.1/24 | ||
config route | config route | ||
Line 158: | Line 156: | ||
option netmask ' | option netmask ' | ||
option gateway ' | option gateway ' | ||
- | This route enables GL-iNET to reach the network | + | |
+ | </ | ||
+ | ===== -. [CO2] Implementing the Applications and Tools ===== | ||
+ | In order to describe and analyze | ||
+ | |||
+ | 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) | ||
+ | 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 | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
- | </ | ||
===== Extracts ===== | ===== Extracts ===== | ||
+ | |||
+ | |||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer