I am part of the world then. In screenshot above for CAKE I had:
nat dual-src/dst internet (or I sometimes try regional)
Based on this thread, and being in Australia, it sounds like I should use:
nat triple-isolate oceanic
Good to know! Thanks for checking in here every now and then, your tips are always very useful.
And btw dtaht I’ve been using CAKE since soon after it came to the edgerouter-x. Back then Dropbox uploads (which were constant due to my work at the time) would basically stall my entire WAN connection on Australia’s standard 15/1 ADSL2+ home plans. CAKE made the connection feel no different to how it does now, it was black magic. Thanks!
I misspoke above. I meant triple-isolate when using nat.
I don´t know what the right answer is for australia, my hope is that you have plenty of CDNs now and you do not need to set oceanic.
I am delighted by how useful many people have found it, saddened by how few that could use it know about it. Most of my work these days is with LibreQos, so that ISPs can do the right things. I look forward to the day most CPE just does the right things.
Is anyone using cake-overhead-scheme with PPPoE and VLAN to the WAN or Bridge interface in Queue-Tree?
I just started really using cake last year to great results… someone please tell me this is a sick April Fools joke 
It’s not https://github.com/LibreQoE/LibreQoS/pull/684#issuecomment-2770436543
RIP Dave .
Unfortunately, it’s not a joke. Frank with LibreQoS here. Besides sharing this sad, sad news in our production, this is our official statement:
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
I came here to find a right contact at MikroTik that would be able to discuss how Dave’s positive impact on MikroTik can be commemorated.
So sad, I’m shocked honestly
Dave was an active contributor also directly with MikroTik and shared his recommendations and bug reports with our support team
Yessir, we know this. I was hoping to get in touch with someone from the MikroTik management to discuss how MikroTik can actually commemorate Dave and his work. Cloudflare did it already, other companies are working on it as far as I know…
That's a really great post there, and I agree with the Round-Trip Time section. CAKE uses sane defaults. The 100ms RTT works for the majority of people, but that doesn't mean it will always work, especially for the minority.
Western people are probably blessed with tons of good ISPs with good peering and very affordable pricing. That's not always the case for Eastern countries, especially Asian countries.
An easy example to reproduce this is the case with users in China, where using Google/Cloudflare DNS often gives them IPs to overseas servers, which will be slower. They mitigate this issue by using smartdns and splitting the DNS between domestic and foreign websites. Domestic websites use domestic DNS (like Alidns, Tencent DNS, and so on), while foreign websites use Google/Cloudflare DNS.
My point is that if we don't understand their problems, we will just accept that 100ms RTT works for everyone, when that's clearly not the case for users in mainland China and nearby countries.
I made a tool to automatically change CAKE's RTT in real-time based on your real network conditions, but this might not be a straightforward solution for MikroTik users. It's written in Golang for better accuracy and performance, but I also made a shell script version, which might not be as accurate or performant as the Golang version. Both were tested and worked with OpenWrt, so if you ever have the chance to try OpenWrt later, this project might be useful for you.
I also have an RB5009, and I know we can run Docker containers with it, but there's really no easy way to change CAKE RTT in real-time on MikroTik. So, anyone who knows a solid way to achieve a similar result in MikroTik, please feel free to use my project as a reference and go crazy with it.
Also, RIP dtaht. I read lots of articles, forum threads, GitHub issues, and probably more that I've forgotten where he commented. His discussions were really helpful to me, so I feel kind of sad that whenever there's a post about CAKE or SQM in the future, he won't be there to join the discussion.