wikiroute

networking recipes

User Tools

Site Tools


qos_project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
qos_project [2017/11/29 09:12] – [5. [CO1] Connecting the Platform] samerqos_project [2017/11/30 18:48] – [Extracts] samer
Line 128: Line 128:
 </file> </file>
  
-Similarly, the configuration of the GL-iNET router +Similarly, the configuration of the GL-iNET router below shows the following: 
 + 
 +  * The WiFi interface is configured with a static IP address 192.168.8.1/24 
 +  * The WAN interface is configured with a static IP address 10.0.0.1/24 
 +  * A static route enables GL-iNET to reach the network 192.168.200.0/24 via 10.0.0.2 of the other router.
  
 <file bash /etc/config/network> <file bash /etc/config/network>
Line 139: Line 143:
         option _orig_ifname 'eth1'         option _orig_ifname 'eth1'
         option _orig_bridge 'false'         option _orig_bridge 'false'
-This interface (wifi) is configured with a static IP address 192.168.8.1/24 
  
 config interface 'wan' config interface 'wan'
Line 147: Line 150:
         option ipaddr '10.0.0.1'         option ipaddr '10.0.0.1'
         option netmask '255.255.255.0'         option netmask '255.255.255.0'
-This interface (connected to the other router) is configured with a static IP address 10.0.0.1/24 
  
 config route config route
Line 154: Line 156:
         option netmask '255.255.255.0'         option netmask '255.255.255.0'
         option gateway '10.0.0.2'         option gateway '10.0.0.2'
-This route enables GL-iNET to reach the network 192.168.200.0/24 via 10.0.0.2 of the other router+  
 +</file> 
 +===== -. [CO2] Implementing the Applications and Tools ===== 
 +In order to describe and analyze the basic steps for installing and using the tools and client/server applications, we need to look carefully to these 4 applications: iperf, flent, VLC, HTTP.
  
 +Let's start with the application iperf:
  
-</file> +- To activate iperf3: 
-===== Extracts ===== +     * On the server side: iperf3 -s 
-#On TPlink router +     * On the client side: iperf3 -c 192.168.200.192
-<file /etc/config/dhcp> +
-config dnsmasq +
-        option domainneeded '1' +
-        option boguspriv '1' +
-        option filterwin2k '0' +
-        option localise_queries '1' +
-        option rebind_protection '1' +
-        option rebind_localhost '1' +
-        option local '/lan/' +
-        option domain 'lan' +
-        option expandhosts '1' +
-        option nonegcache '0' +
-        option authoritative '1' +
-        option readethers '1' +
-        option leasefile '/tmp/dhcp.leases' +
-        option resolvfile '/tmp/resolv.conf.auto' +
-        option localservice '1'+
  
-config dhcp 'lan' +- To visualize UDP trafic with a specific bandwidth: 
-        option interface 'lan' +     * On the client side: iperf3 -c 192.168.200.192 -u -b 2M 
-        option start '100' +Here we set the bandwidth with UDP to 2Mbit/s. 
-        option limit '150' +Note that by default ,UDP sets the bandwidth to 1Mbit/s
-        option leasetime '12h' +
-        option dhcpv6 'server' +
-        option ra 'server'+
  
-config dhcp 'wan' +- To extend the transmission time(second) as well as the number packets sent: 
-        option interface 'wan' +     * On the Client side: iperf3 -c 192.168.200.192 -t 15 
-        option ignore '1'+Note that  by default, iperf3 sets the time to 10 seconds
  
-config odhcpd 'odhcpd' +- To reverse mode(server sends, client receives): 
-        option maindhcp '0' +     * On the Client side: iper3 -c 192.168.200.192 -R  
-        option leasefile '/tmp/hosts/odhcpd+ 
-        option leasetrigger '/usr/sbin/odhcpd-update'+- 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 =====
  
-config host 
-        option name 'pi2' 
-        option mac 'b8:27:eb:0f:f8:95' 
-        option ip '192.168.200.192' 
  
-config host 
-        option name 'pi3' 
-        option mac 'b8:27:eb:20:aa:54' 
-        option ip '192.168.200.193' 
-</file> 
  
  
qos_project.txt · Last modified: 2021/08/28 09:58 by samer