It appears that the 2.4ghz band is not adhering to using sqm egress settings for limits. My android phone has no cap when connected to wifi only.
NAME="LEDE"
VERSION="17.01.2, Reboot"
ID="lede"
ID_LIKE="lede openwrt"
PRETTY_NAME="LEDE Reboot 17.01.2"
VERSION_ID="17.01.2"
HOME_URL="http://lede-project.org/"
BUG_URL="http://bugs.lede-project.org/"
SUPPORT_URL="http://forum.openwrt.org/"
BUILD_ID="r3435-65eec8bd5f"
LEDE_BOARD="ar71xx/generic"
LEDE_ARCH="mips_24kc"
LEDE_TAINTS="no-all"
LEDE_DEVICE_MANUFACTURER="LEDE"
LEDE_DEVICE_MANUFACTURER_URL="http://lede-project.org/"
LEDE_DEVICE_PRODUCT="Generic"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="LEDE Reboot 17.01.2 r3435-65eec8bd5f"
But your wired connections are being limited properly?
Yes. Its strange. I noticed this when my phone would get an update or a notification my latency would spike. Then I confirmed it using the Speedtest App for Android. I can confirm it works for my laptop on the 5ghz band. I will have to test the 2.4ghz band when streaming movies stops tonight.
So I think the problem is fixed. I was used to fq_codel automatically working for wifi. Now I have setup cake for wlan0 & wlan1 with ingress and egress limits reversed. Appears to be working now. Will be testing the nat dual-* options over wifi 
You probably now that already and took it into consideration, but to make this helpful to others less experinced stumbling over this thread:
If you instantiate SQM on internal interfaces, like LAN or WLAN (so anything but WAN) the directionality of ingress and egress changes its relation towards the internet. Specifically the internal interface's egress direction corresponds to the internet download direction and the internal interface's ingress direction corresponds to internet uploads. So in essence for SQM instances running on an interface other than WAN, one needs to switch the bandwidth of the Download and upload fields in the GUI; that is if you would use ingress 10, egress 1 on WAN you need to specify ingress 1, egress 10 on say an LAN interface to get the same effective shaping in relation to the internet.
1 Like
What would be the purpose of putting SQM on LAN instead of (or in addition to) WAN? Bandwidth usage limiting?
To control the queues which by default at this stage of the buffer bloat effort, requires bandwidth limiting along with the many other parameters inside the network stack to effectively control latency. You could police the bandwidth usage inside the lan without SQM using other bits of software, but since in my case wifi has access to the WAN which needs AQM. One could instantiate SQM on the inter-lan switch for bandwidth limiting without side effects as long as your device has the cpu to accommodate all the SQM instances. I'm using a Netgear WNDR3800-Charter router effectively with SQM on WAN, WLAN 2.4ghz WLAN 5ghz.