Search results

Thx rich for weighing in. I agree with your suggestion, in that it seems likely your router is struggling to keep up. (I gave up and switched to x86 openwrt boxes). BUT: If there was some way to address the folk saying "You don´t have bufferbloat with normal use" definitively once and for all...

@360NoScoper I'm one of cake's authors. I'm aware of how bad the variable "sag" can be on crowded cable, lte, and wifi networks, and over here is an effort to dynamically adjust it. https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/108848/ It needs testers, and a port of the core algorithms...

occasionally I feel the need to raise the amount of clue with laughter: https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-but-its-not-over-yet/

My take is that fq + aqm is useful on any link making a fast to slow transition. As we scale into the 100s of mbits problems get harder to hit in simple scenarios, but still exist in more complex ones. Certainly given the thousands of devices that run fq_codel and cake now I wouldn't give this...

The only two things I can add to this conversation are that getting the frame right right for your technology (DSL/cable) is important, and the spikes I see in these reports look partially like that. I'm not sure if freshjr's scripts do that? There is enormous technical detail as to why and how...

Thank you for trying to make the Net better on this side! For the record the entertaining videos using water bottles as the core analogy were mine at the university of modena and Stephen Hemmingers at some linux con or another. Stephen's is both shorter and funnier...

@RMerlin, lordy... this is 2.6 based still? I feel your pain. I guess my question then becomes what are the underlying qdiscs adaptive qos, traditional qos, and freshJR's stuff uses?

@FreshJR - have you taken a look at sch_cake yet? One feature I'm proud of is the docsis and adsl modes where (at least in the lab!) we can hit 100% of the set rate on the uplink. We still recommend 85-90% on shaping the downlink, though. See: https://arxiv.org/pdf/1804.07617 for some details...

what lies underneath traditional and adaptive qos? fq_codel? sfq?

I am curious as to what exactly is "in" adaptive QOS these days?

sigh That's too bad. It otherwise looks like good hardware. I sure hope that they've, or you've handled the hundreds of CVEs against older kernels and software. https://www.schneier.com/blog/archives/2014/01/security_risks_9.html

it's not clear what kernel are they using? All the innovations over the last couple years on the qos/aqm/packet scheduling front are part of the bog standard linux kernel now. Rather than imq, openwrt and cerowrt's qos mechanisms are built around the linux standard ifb module (not imq) for...

I guess we're not doing a good job of SEO!? The core bufferbloat-fighting innovations (notably "fq_codel") in cerowrt landed in openwrt last year, and have since landed in the linux mainline kernel and nearly every up to date distribution (such as RHEL 7, fedora 18 and later, and ubuntu 13.x)...

open source firmwares with better qos/aqm OpenWrt is marching down towards a stable release. Can contact the devs for a steer towards stable... dd-wrt added fq_codel to it's qos system over a year ago, I don't know when it went into a stable release, but it's out there...

fq_codel, bufferbloat, and streamboost One of the core technologies in streamboost is fq_codel, which is a standard part (now) of openwrt "barrier breaker", dd-wrt, cerowrt, and other shaping systems for hundreds of platforms. Additionally the gargoyle-router project has a system built around...

codel and fq_codel are part of linux 3.5, not 3.4 Sorry, if you want to muck with fq_codel, it entered the linux kernel as of version 3.5, and was improved several times between 3.6 and present. Backporting fq_codel to Linux 3.4 is straightforward, however your QoS system would need to be...