@Kingp1n
-----
UPDATE:
The reports stating that QOS (fast_version) doesn't work when performing a install on a fresh firmware until after a reboot were bothering me.
I reinitialized my router TWICE, and could not reproduce the issue.
Code:
May 10 04:54:59 adaptive QOS: FreshJR FakeTC Installed
May 10 04:54:59 adaptive QOS: Parsing User QOS Rates -> (Updating)
May 10 04:55:06 kernel: Init chrdev /dev/detector with major 190
May 10 04:55:06 kernel: tdts: tcp_conn_max = 8000
May 10 04:55:06 kernel: tdts: tcp_conn_timeout = 300 sec
May 10 04:55:21 kernel: SHN Release Version: 2.0.1 3529123_patch
May 10 04:55:21 kernel: UDB Core Version: 0.2.14 r3529123
May 10 04:55:21 kernel: Init chrdev /dev/idpfw with major 191
May 10 04:55:21 kernel: IDPfw: IDPfw is ready
May 10 04:55:21 kernel: sizeof forward pkt param = 192
May 10 09:55:22 adaptive QOS: Clearing qos environment
May 10 09:55:34 adaptive QOS: Clearing qos environment
May 10 04:55:36 kernel: IDPfw: Exit IDPfw
May 10 04:55:36 kernel: mod epilog takes 0 jiffies
May 10 04:55:36 kernel: IDPfw: Exit IDPfw
May 10 04:55:36 kernel: Exit chrdev /dev/idpfw with major 191
May 10 04:55:36 kernel: Exit chrdev /dev/detector with major 190
May 10 09:55:37 rc_service: bwdpi_check 319:notify_rc start_firewall
May 10 04:55:37 miniupnpd[2808]: shutting down MiniUPnPd
May 10 04:55:37 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
May 10 04:55:38 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
May 10 04:55:38 miniupnpd[3214]: HTTP listening on port 34094
May 10 04:55:38 miniupnpd[3214]: Listening for NAT-PMP/PCP traffic on port 5351
May 10 04:55:49 rc_service: httpd 1090:notify_rc restart_qos;restart_firewall
May 10 04:55:49 adaptive QOS: Clearing qos environment
May 10 04:55:49 adaptive QOS: Parsing User QOS Rates -> (Updating)
May 10 04:55:51 kernel: Init chrdev /dev/detector with major 190
May 10 04:55:51 kernel: tdts: tcp_conn_max = 8000
May 10 04:55:51 kernel: tdts: tcp_conn_timeout = 300 sec
May 10 04:56:07 kernel: SHN Release Version: 2.0.1 3529123_patch
May 10 04:56:07 kernel: UDB Core Version: 0.2.14 r3529123
May 10 04:56:07 kernel: Init chrdev /dev/idpfw with major 191
May 10 04:56:07 kernel: IDPfw: IDPfw is ready
May 10 04:56:07 kernel: sizeof forward pkt param = 192
May 10 04:56:07 kernel: ERR[qos_start:3356] qos_ops is not registered!
May 10 04:56:07 kernel: ioctl_iqos_op_switch(1) fail!
May 10 04:56:08 kernel: ERR[qos_start:3356] qos_ops is not registered!
May 10 04:56:08 kernel: ioctl_iqos_op_switch(1) fail!
May 10 04:56:09 adaptive QOS: Clearing qos environment
May 10 04:56:09 adaptive QOS: Clearing qos environment
May 10 04:56:10 adaptive QOS: Parsing User QOS Rates -> (Updating)
May 10 04:56:12 adaptive QOS: Changing 1:10 class rate
May 10 04:56:14 adaptive QOS: Changing 1:11 class rate
May 10 04:56:16 adaptive QOS: Changing 1:12 class rate
May 10 04:56:17 adaptive QOS: Changing 1:13 class rate
May 10 04:56:21 adaptive QOS: Changing 1:14 class rate
May 10 04:56:25 adaptive QOS: Changing 1:15 class rate
May 10 04:56:26 adaptive QOS: Changing 1:16 class rate
May 10 04:56:28 adaptive QOS: Applying ------ Up Rules
May 10 04:56:28 adaptive QOS: Changing 1:17 class rate
May 10 04:56:28 adaptive QOS: Applying ---- Down Rules
May 10 04:56:40 adaptive QOS: *- Clearing Iptables -*
May 10 04:56:43 miniupnpd[3214]: shutting down MiniUPnPd
May 10 04:56:43 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
May 10 04:56:43 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
May 10 04:56:43 miniupnpd[10845]: HTTP listening on port 50422
May 10 04:56:43 miniupnpd[10845]: Listening for NAT-PMP/PCP traffic on port 5351
May 10 04:56:44 adaptive QOS: Applying Iptables Rules
------- Manually check for updated Signatures --------
May 10 04:59:20 rc_service: httpd 1090:notify_rc start_sig_check
May 10 04:59:27 adaptive QOS: Clearing qos environment
May 10 04:59:28 adaptive QOS: Clearing qos environment
May 10 04:59:46 adaptive QOS: Clearing qos environment
May 10 04:59:46 adaptive QOS: Clearing qos environment
May 10 04:59:49 adaptive QOS: Changing 1:10 class rate
May 10 04:59:51 adaptive QOS: Changing 1:11 class rate
May 10 04:59:52 adaptive QOS: Changing 1:12 class rate
May 10 04:59:54 adaptive QOS: Changing 1:13 class rate
May 10 04:59:58 adaptive QOS: Changing 1:14 class rate
May 10 05:00:02 adaptive QOS: Changing 1:15 class rate
May 10 05:00:03 adaptive QOS: Changing 1:16 class rate
May 10 05:00:04 adaptive QOS: Applying ------ Up Rules
May 10 05:00:05 adaptive QOS: Changing 1:17 class rate
May 10 05:00:05 adaptive QOS: Applying ---- Down Rules
May 10 05:00:17 adaptive QOS: *- Clearing Iptables -*
On both router re-initializations the script modifications worked right away without a reboot. This was both before and after QOS definition updates.
Anyway, the fast version is experimental for a reason! If you cannot monitor system log or check the qos statistics page, then it is not for you. Instead you should definitely be using the compatible version!!
If it **does** have a serious bug like the reports and I happen to experience it, then fast will be discontinued instead of fixed. It is already hacky, and stacking more hacky patches on top of it is not an option. (Personally I like the instant results and verbose logging of the fast version)
Mine has been stable for the longest time, so idk what is going on.