Woolf

Hello Keenetic team, I would like to request more advanced and transparent controls for the existing SQM / CAKE-based functionality in IntelliQoS. I understand that Keenetic already includes Smart Queue Management as part of IntelliQoS, and that IntelliQoS can classify applications, apply traffic prioritization, and optimize bandwidth by using configured download and upload limits. This is already a very useful feature. However, the current interface hides most of the actual SQM / CAKE behavior from the user. For users who specifically care about bufferbloat, gaming latency, small-packet protection and fair bandwidth sharing between devices, it would be very useful to expose more CAKE/SQM options in the web interface. The main request is not to replace IntelliQoS, but to make the SQM part more configurable and more transparent. Currently, IntelliQoS is mainly presented as application classification and prioritization. This is useful, but it is not the same thing as giving the user direct control over CAKE’s fairness and queue management behavior. Application recognition helps when the router correctly identifies traffic categories such as gaming, conferencing, streaming or file transfers. But real home networks often include encrypted traffic, unknown games, cloud sync, downloads, mobile apps, VPNs and devices that generate mixed traffic. In those cases, application recognition alone may not be enough. CAKE’s strength is that it can control latency and fairness even without needing to perfectly identify every application. It can prevent large bulk transfers from burying small, sparse and latency-sensitive flows, and it can also help prevent one device from monopolising the connection. For this reason, I think KeeneticOS would benefit from an “Advanced SQM / CAKE mode” in IntelliQoS. Suggested features: Separate SQM control from application prioritization It would be helpful if users could clearly enable or disable SQM independently from application classification and application prioritization. For example: Application classification: on/off Application prioritization: on/off Smart Queue Management / CAKE shaping: on/off This would make the interface clearer. Some users may want CAKE/SQM fairness and bufferbloat control without relying heavily on application-based prioritization. Show which queue algorithm is being used The interface could clearly show whether the active SQM backend is CAKE, fq_codel or another algorithm. For example: Current SQM algorithm: CAKE Current mode: besteffort / diffserv3 / diffserv4 Current isolation mode: flow isolation / host isolation Current WAN shaping rate: download / upload This would help advanced users understand what the router is actually doing. Host fairness / device fairness option Please consider adding CAKE host isolation options, especially for home networks with many devices. Useful modes could include: fair sharing between flows; fair sharing between local devices; fair sharing on download and upload separately. The practical benefit is simple: one device downloading or uploading heavily should not destroy latency for another device that is gaming, using voice chat or making a video call. DiffServ mode selection It would be useful to expose simplified DiffServ options. For example: besteffort — simple fairness, no priority tiers; diffserv3 — simple priority separation; diffserv4 — more detailed priority separation. This would give users the choice between simple latency control and more advanced priority handling. Link-layer overhead presets Please add presets for common WAN types, such as: Ethernet; PPPoE; VLAN; VDSL/PTM; ADSL/ATM; DOCSIS; conservative mode. This is important because incorrect overhead compensation can make SQM shape slightly above the real link capacity. When that happens, queues may still build up outside the router, especially on the ISP side, and bufferbloat control becomes less effective. ACK filtering option for asymmetric connections Many users have asymmetric connections, for example 100/20, 50/10 or 50/6. In these cases, upload can become the bottleneck easily. An optional ACK filtering setting could help reduce unnecessary upstream ACK load in suitable asymmetric scenarios. More precise bandwidth input Please allow more precise values for download and upload rates. For example: Mbps with decimals; or direct Kbps input. This is especially important for low-speed connections. On a 6 Mbps upload line, the difference between 4 Mbps, 4.5 Mbps and 5 Mbps can be very noticeable for latency and bufferbloat. Integer-only Mbps values are too coarse for these connections. SQM statistics and diagnostics It would also be useful to show basic SQM statistics, such as: active queue algorithm; packet drops; ECN marks; current shaping rate; CPU load impact; whether hardware offloading is active or bypassed; whether SQM is active on upload, download or both. This would help users diagnose whether SQM is actually working correctly. The benefit for users would be: more stable ping under load; better gaming latency while other devices are active; fewer voice/video call interruptions; fairer sharing between devices; better bufferbloat control; less dependence on perfect application recognition; more predictable behavior on DSL, VDSL, PPPoE, cable, radio-link and asymmetric fiber connections. This feature could be hidden under an “Advanced” section, so normal users can keep the current simple IntelliQoS experience, while advanced users can fine-tune CAKE/SQM when needed. In short, Keenetic already has a strong IntelliQoS system. My request is to expose the SQM / CAKE part more clearly and give users advanced controls similar to what OpenWrt SQM-CAKE users value: fairness, host isolation, overhead compensation, DiffServ modes, ACK filtering and precise bandwidth tuning. Thank you for considering this request.