Differences

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

Link to this comparison view

Both sides previous revision Previous revision
technical:ppsk-sqm [2024/08/08 08:59] – [Troubleshooting] systemtechnical:ppsk-sqm [2024/08/08 10:11] (current) – system
Line 24: Line 24:
  
 ====== SQM on OpenWrt ====== ====== SQM on OpenWrt ======
-The following sections are a short summary of information from this Wiki page (https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm) as well as our own experimenting.+The following sections are a brief summary of information from this wiki page (https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm) and from our own experiments.
 ===== Required Packages ===== ===== Required Packages =====
-  * For SQM to be available in OpenWrt, you need the **sqm-scripts** package. +  * To make SQM available in OpenWrt, you need the package **sqm-scripts**. 
-  * If you also have Luci on the OpenWrt device, it is recommended to install the additional **luci-app-sqm** package. +  * If you also have Luci on the OpenWrt device, it is recommended to install the additional package **luci-app-sqm**. 
-  * This will install the Luci SQM package which is well developed and offer you an intuitive way to apply SQM on selected interfaces using the Luci web interface.+  * This will install the Luci SQM package which is well developed and provides you with an intuitive way to apply SQM to selected interfaces via the Luci web interface.
 ===== Config File ===== ===== Config File =====
-  * Essentially the SQM application in Luci manipulates the **/etc/config/sqm** UCI based config file and start and stop the SQM service to apply those settings. +  * Essentially, the SQM application in Luci manipulates the UCI-based configuration file **/etc/config/sqm** and starts and stops the SQM service to apply these settings. 
-  * Lets look at a snippet of the sqm config file:+  * Let's take a look at an excerpt from the sqm configuration file:
  
 <code bash> <code bash>
Line 46: Line 46:
 </code> </code>
  
-  * Some items of note on this snippet: +  * Some notes on this snippet: 
-        * The Queue discipline is CAKE. There is also other options like **fq_codel** which you can use should performance be an issue. +        * The queue discipline is CAKE. There are also other options like fq_codel that you can use if performance is an issue. 
-        * The upload and download values are in kbps so this snippet limits it to 4Mbps (4*1024) +        * The upload and download values are in kbps, so this snippet limits the value to 4Mbps (4*1024) 
-        * The script used to set up the SQM (based on the settings in the /etc/config/sqm file) is *piece_of_cake.qos*. +        * The script to set up the SQM (based on the settings in the /etc/config/sqm file) is called **piece_of_cake.qos**. 
-        * The SQM section is applied to the **br-ex_v104** interface which is actually a bridge. +        * The SQM section is applied to the **br-ex_v104** interface, which is actually a bridge. 
-    * Lets look at the /etc/config/network file to find out more about the **br-ex_v104** interface.+    * Let us take a look at the /etc/config/network file to learn more about the br-ex_v104 interface.
  
 <code> <code>
Line 66: Line 66:
     option netmask '255.255.255.0'     option netmask '255.255.255.0'
 </code> </code>
-  * Although the word //interface// in the /etc/config/sqm section is used intuitive, it can also be applied to a //device// like a bridge. +  * Although the word //interface// is used intuitively in the /etc/config/sqm section, it can also be applied to a //device// such as a bridge. 
-  * In our case the br-ex_104 bridge has one port, eth1.104. This port will receive traffic from VLAN 104 on eth1. (e.g. when a user connects with a Private PSK and the Dynamic VLAN associated with him is 104.) +  * In our case, the br-ex_104 bridge has one port, eth1.104. This port receives traffic from VLAN 104 on eth1 (e.g. when a user connects to a private PSK and the dynamic VLAN assigned to it is 104) 
-  * Traffic going through this bridge will thus be throttled and managed with SQM.+  * The data traffic that runs via this bridge is therefore throttled and managed with SQM.
  
-Now that we covered the configuration of SQM, we can look at some handy commands under the Troubleshooting heading.+Now that we have covered the configuration of SQM, we can take a look at some practical commands under the heading 
 ===== Troubleshooting ===== ===== Troubleshooting =====
   * To start and stop SQM:   * To start and stop SQM:
Line 84: Line 84:
 </code> </code>
  
-  * SQM creates a matching IFB Interface with the convention //ifb4-<interface>//. So it is an easy way to tell if the start-up was successful.+  * SQM creates a matching IFB interface with the convention //ifb4-<interface>//. In this way, you can easily determine whether the start was successful.
  
 <code bash> <code bash>
Line 112: Line 112:
 </code> </code>
  
-  * This brings us to the end of the section of SQM on OpenWrt.  +  * This brings us to the end of SQM's section in OpenWrt. 
-  * In RADIUSdesk we took this knowledge and created the SQM Profiles applet which makes management of SQM in MESHdesk and APdesk a breeze. +  * In RADIUSdesk we have taken this knowledge and created the SQM Profiles applet, which makes managing SQM in MESHdesk and APdesk a breeze. 
-  * There is a dedicated page for SQM Profiles which should get you applying limits in no time.+  * There is a special page for SQM Profiles that allows you to apply limits in no time at all.
  
  
  • technical/ppsk-sqm.1723100361.txt.gz
  • Last modified: 2024/08/08 08:59
  • by system