What's new

CakeQOS CakeQOS-Merlin

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

It's not up to me. OP has to place the request and then I'll look into it if a script is compatible and meets the requirements for amtm.
To me it looks the project has stalled for some reason.
I'm not having any issues/problems with it, so to me it's working, and there's no need for further development (until that isn't the case). This may not be the case for others...especially those with speeds from their ISP > 100Mbps
 
I'm not having any issues/problems with it, so to me it's working, and there's no need for further development (until that isn't the case). This may not be the case for others...especially those with speeds from their ISP > 100Mbps
There are some defined goals open on the roadmap here: https://www.snbforums.com/threads/cakeqos-merlin.64800/post-595131

As @Wade Coxon points out, this script is of limited use due to the supported models limitation. It would have to run on more routers for me to even consider supporting it in amtm.
 
To me it looks the project has stalled for some reason.

It hasn't stalled per say, there just weren't any more features worth adding after my last rewrite.

As @Wade Coxon points out, this script is of limited use due to the supported models limitation. It would have to run on more routers for me to even consider supporting it in amtm.

Only HND routers are supported (AC86U and newer) as it requires the newer 4.x kernel.
 
It hasn't stalled per say, there just weren't any more features worth adding after my last rewrite.



Only HND routers are supported (AC86U and newer) as it requires the newer 4.x kernel.
We'll see if any newer models get added to the Asuswrt-Merlin supported list.
 
and more importantly, which ones are dropped. I think that day might be coming for the ac68 sooner than most might think, and that would take tha ac66_b1 with it
Highly doubt the ac68u. I believe most of rmerlin firmware downloads are for the 68u. I can be wrong though!
 
No, I mean the ac68, predecessor to the current AC86 (which is already "obsolete" because of AX86), and the ac66_b1, which was a "prerelease" of the ac68...they're old and have been supported for a long time; asus might think it's time to move them to the "legacy" list so they can focus on the newer stuff...and AX88 has supplanted ac88, another one that might be deemed legacy.
...from what I know of the product line historically and currently, I'd not be surprised if asus just stops supporting earlier ac-wireless models (except for maintenance releases) that are non-HND in the near future. it just makes business sense - they can move forward faster/easier when the entire code team is focused on the now and future...think along the lines of Apple: sure the old stuff works, and works well, but look at this new feature, this better functionality...and it's faster and in terms of speed for your money, it's a helluva deal! Also remember wifi6e is coming...that "pinnacle AC-wireless" stuff is ancient in comparison. (hey, I still have apple G5s and a late g4 powerbook that still work and I use on the regular - from my cold dead hands...)
 
I note that a Trendmicro signature update attempt still kills Cake.

Is there any outlook for one of our resident gurus to have a look at this?
 
I note that a Trendmicro signature update attempt still kills Cake.

Is there any outlook for one of our resident gurus to have a look at this?
If you setup /jffs/scripts/service-event-end to listen for "restart_wrs" or "start_sigcheck" events and then reapply your tc commands for cake, that should be an improvement.

Similar concept here in FlexQoS:
 
If you setup /jffs/scripts/service-event-end to listen for "restart_wrs" or "start_sigcheck" events and then reapply your tc commands for cake, that should be an improvement.

Similar concept here in FlexQoS:

Many thanks, a little above my pay grade though......:oops:
 
A test of what’s happening would be to run tc monitor in an SSH window and trigger a signature update. See if the qdisc gets deleted in the SSH session output.

Result..........

deleted qdisc cake 8003: dev eth0 root bandwidth 40Mbit besteffort triple-isolate nat nowash no-ack-filter split-gso rtt 60.0ms raw overhead 0 no-sce

(40mbps is my upload setting.)
 
If you setup /jffs/scripts/service-event-end to listen for "restart_wrs" or "start_sigcheck" events and then reapply your tc commands for cake, that should be an improvement.

Similar concept here in FlexQoS:
@dave14305 can we simply do a copy and paste of your commands to the service-event-end file?
 
@dave14305 can we simply do a copy and paste of your commands to the service-event-end file?
As long as you know what needs to be run to "start cake" again, you can manually add lines similar to these as a test:
Bash:
#!/bin/sh

if [ "$1" = "restart" ] && [ "$2" = "wrs" ]; then { sh /jffs/addons/cake-qos/cake-qos.sh checkrun & } ; fi
if [ "$1" = "start" ] && [ "$2" = "sig_check" ]; then { sh /jffs/addons/cake-qos/cake-qos.sh checkrun & } ; fi
Test at your own risk since I can't test this myself. But this is the same checkrun command that runs at the top of every hour in the cake-qos script.

I also wouldn't encourage everyone to do this yet, because if it ever gets added to the main script, it will be a pain to deal with these manual entries and any entries the script may want to add in the future, and avoid duplication.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top