Hello Keenetic team and community,
I understand that KeeneticOS uses CAKE-based AQM/SQM, and that NFQ is used for shaping at higher speeds while CAKE is used at lower rates. What I would like to understand better is which CAKE/SQM-related mechanisms are actually active internally, and how they are implemented.
Could someone from the Keenetic team or experienced users confirm whether the following mechanisms are active in the current IntelliQoS/SQM/NFQ implementation? A simple yes/no or short explanation for each item would be very helpful.
NAT-aware host fairness
Can SQM fairly separate LAN devices behind NAT?
ACK filtering
Is TCP ACK filtering, or any similar ACK optimization, used?
WAN overhead compensation
Does SQM account for PPPoE, VLAN, DSL, cable or Ethernet overhead while shaping?
Download-side SQM / IFB
Is download shaping done with an ingress / IFB-like mechanism, or with another Keenetic-specific method?
Packet marking / priority mapping
After IntelliQoS classifies traffic, are packets marked with DSCP/802.1p, or are they only mapped internally to priority queues?
How are CAKE features limited or simplified in NFQ to ensure fast loading speeds?
Does IntelliQoS / NFQ protect small latency-sensitive UDP flows under heavy load independently of application recognition, at the SQM/queueing level or through Keenetic’s own scheduler?
My goal is not to criticize IntelliQoS. I am trying to understand how close the current implementation is to typical OpenWrt SQM-CAKE behavior in areas such as host fairness, overhead compensation, ACK filtering and download-side shaping.
Any explanation from moderators, developers or experienced users would be appreciated.
Thank you.
Hello Keenetic team and community, I understand that KeeneticOS uses CAKE-based AQM/SQM, and that NFQ is used for shaping at higher speeds while CAKE is used at lower rates. What I would like to understand better is which CAKE/SQM-related mechanisms are actually active internally, and how they are implemented. Could someone from the Keenetic team or experienced users confirm whether the following mechanisms are active in the current IntelliQoS/SQM/NFQ implementation? A simple yes/no or short explanation for each item would be very helpful. NAT-aware host fairness Can SQM fairly separate LAN devices behind NAT? ACK filtering Is TCP ACK filtering, or any similar ACK optimization, used? WAN overhead compensation Does SQM account for PPPoE, VLAN, DSL, cable or Ethernet overhead while shaping? Download-side SQM / IFB Is download shaping done with an ingress / IFB-like mechanism, or with another Keenetic-specific method? Packet marking / priority mapping After IntelliQoS classifies traffic, are packets marked with DSCP/802.1p, or are they only mapped internally to priority queues? How are CAKE features limited or simplified in NFQ to ensure fast loading speeds? Does IntelliQoS / NFQ protect small latency-sensitive UDP flows under heavy load independently of application recognition, at the SQM/queueing level or through Keenetic’s own scheduler? My goal is not to criticize IntelliQoS. I am trying to understand how close the current implementation is to typical OpenWrt SQM-CAKE behavior in areas such as host fairness, overhead compensation, ACK filtering and download-side shaping. Any explanation from moderators, developers or experienced users would be appreciated. Thank you.