If any
386.1 alpha 2 users with an
AX router are also running FlexQoS (or even if you're using stock Adaptive QoS), please run this test for me to see if the above-mentioned tc filter issue is resolved on the 386 branch.
Bash:
tc filter show dev br0 | grep -c flowid
service restart_qos
sleep 60
tc filter show dev br0 | grep -c flowid
The counts from the first command to the last command should not be doubling each time you do this. That is the test. Doubling = bad.
If you're actually running FlexQoS, reinstate the custom rules afterward by running
flexqos check
Thanking you in advance.
Hi Dave:
Currently still on V384.19 as per my signature, but having an RT-AX88U and FlexQOS V1.05 at the time (Was at 47 Days, 10 hours uptime), when running your command
Code:
tc filter show dev br0 | grep -c flowid
It showed "688", and with FlexQOS on my Ookla Speedtests were getting really slow, so hard rebooted the router (uptime contest gone

), and it went to "58", but now after 18 Days, 16 hours of uptime, with V384.19 and V1.06 Hotfix, when running the command
Code:
tc filter show dev br0 | grep -c flowid
it showed "188", and now after turning FlexQOS off, and then back on, after waiting the appropriate time frame, that command now shows "222", and the Ookla Speedtest has gotten even slower.
Is this an affect from FlexQOS over time, or the V384.19 firmware for an RT-AX88U HND Router?