Differences

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

--- technical:ppsk-sqm [2024/08/08 08:36] – [Config File] system
+++ technical:ppsk-sqm [2024/08/08 10:11] (current) – system
@@ Line 24: / Line 24: @@
 ====== 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 =====
-  * 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 =====
-  * 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>
@@ Line 46: / Line 46: @@
 </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>
@@ Line 66: / Line 66: @@
     option netmask '255.255.255.0'
 </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 =====
+  * To start and stop SQM:
+<code>
+#You might first need to stop it before starting it:
+/etc/init.d/sqm stop
+SQM: Stopping SQM on br-ex_v104
+#Start it
+/etc/init.d/sqm start
+SQM: Starting SQM script: piece_of_cake.qos on br-ex_v104, in: 4096 Kbps, out: 4096 Kbps
+SQM: piece_of_cake.qos was started on br-ex_v104 successfully
+</code>
+  * 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>
+#Real interface
+ifconfig br-ex_v104
+br-ex_v104 Link encap:Ethernet  HWaddr 08:00:27:EA:B7:D5
+    inet addr:10.200.105.1  Bcast:10.200.105.255  Mask:255.255.255.0
+    inet6 addr: fe80::a00:27ff:feea:b7d5/64 Scope:Link
+    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
+    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
+    collisions:0 txqueuelen:1000
+    RX bytes:0 (0.0 B)  TX bytes:1088 (1.0 KiB)
+#Matching IFB
+ifconfig ifb4br-ex_v104
+ifb4br-ex_v104 Link encap:Ethernet  HWaddr AA:93:EE:2A:4D:E6
+    inet6 addr: fe80::a893:eeff:fe2a:4de6/64 Scope:Link
+    UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
+    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+    collisions:0 txqueuelen:32
+    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B
+</code>
+  * To get stats on SQM, you can use the tc command:
+<code bash>
+tc  -s qdisc show dev br-ex_v104
+</code>
+  * This brings us to the end of SQM's section in OpenWrt.
+  * 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 special page for SQM Profiles that allows you to apply limits in no time at all.