Something is wrong, as NON of the custom rules are being applied in your system log. In the system log, if everything was working correctly, you would be also able to see a message stating "Adaptive QOS: Applying Custom Download Rules"
Preparing a debug log is not too difficult. With a debug log we can see what is going under the hood.
(The rule you have created itself is correct and with no syntax errors. If it was applied, it should do what you want it to do)
Please follow the following:
1) Turn OFF qos
2) In putty:
3)Turn ON qos
4)Wait 3 min for it to finish setting itself up
5) In command prompt:
Code:
pscp -scp admin@192.168.1.1:/tmp/qos.log C:\Putty\qos_debug.log
6)In putty:
After that you will have a file named qos_debug.log inside your putty folder. Send me that file using a pastebin link in a private message, and I will try to see what is going on with your particular setup.
I know you are using MacOS, so you do not have command prompt and the pscp executable, but just use the mac equivalent as you did before, or use a windows computer.
---
@daviworld
If you got more messages in addition to these two your have pasted
Code:
Dave: Adaptive QOS: FreshJR fakeTC Running (No Change Required)
Feb 18 08:03:23 Dave: Adaptive QOS: Parsing QOS config -> No Change
then everything is working fine.
The additional messages should be (in no particular order) that indicate everything is working are:
Code:
Applying Custom Download Rules
Applying Custom Upload Rules
Modifying Download Rule 22
Modifying Download Rule 23
Modifying Upload Rule 22
Modifying Upload Rule 23
Changing 1:10 class rate
Changing 1:11 class rate
Changing 1:12 class rate
Changing 1:13 class rate
Changing 1:14 class rate
Changing 1:15 class rate
Changing 1:16 class rate
Changing 1:17 class rate
Besides that, the other error messages are not from this script, but rather present from something in ASUS's own code.
I have seen user get these messages without the QOS script running so fixing it is beyond my control. Everything seems to be working fine QOS side even with these messages present.
---
To clarify, you should be safe to ignore these messages
Code:
Feb 18 19:27:42 kernel: ERR[qos_start:3356] qos_ops is not registered!
Feb 18 19:27:42 kernel: ioctl_iqos_op_switch(1) fail!
Feb 18 19:27:45 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Feb 18 19:27:45 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!