the ‘BQL series’ is a topic branch of cerowrt attempting to prove out
new bufferbloat technologies, notably ‘Byte Queue Limits’ (BQL), and SFQRED.
When this stabilizes we will move back into a real development cycle again.
Virtually all the work being done in the BQL series of builds has been incorporated into the Linux 3.3 kernel. We have dropped further development of the BQL series in favor of pushing on with development on a more mainline core. For more information, see the
-bind 9.9 final
-decently working aqm with adsl support
alternate tcp algorithm support
changes in this release:
ntpd + dnssec removed (too buggy)
snmpd installed by default (for SNMP monitoring)
fprobe installed by default (for NetFlow monitoring)
avahi installed by default (for mdns/Bonjour device naming and discovery across subnets)
sort of better working ‘aqm’ shaper installed
**** when configured uses hfsc + sfqred
**** still has trouble with ipv6, diffserv, and tcp elephants
**** no adsl overhead support
BQL-27 is the third public release of a BQL enabled kernel build for cerowrt.
The primary purpose of the bql series is to evaluate and test the new BQL, improved SFQ, RED, and SFQRED subsystems, while we grope towards a final product definition.
It should be possible now to thoroughly debloat ethernet behavior, as well as vastly improve to-upstream dsl/ethernet behavior.
Wireless-n remains a major problem, and is likely to remain one until a
thorough redesign takes place of the aggregation and AP
layers in Linux. (in other words, we don’t expect to make any real progress on wireless until august at the earliest). That said, the new algorithms do hold wireless latency ‘tighter’, under load.
A great deal of additional stuff is included by default, of varying quality. Due to the size of this build, no jffs2 version will be available, only the squashfs version works for wndr3700v2 and wndr3800.
I note that the wndr3700v3 has hit the stores and IS NOT compatible with the v2. Get a 3800 if you want to be future proofed.
The standard Installation Guide otherwise applies.
bql-27 meets the original base feature set intended for rc7.
Some core features may be added, others dropped, as being discussed on the mailing list.
Several hundred GB have been sent through the router with no crashes. Performance is good. SFQ does wonders under load for things like voip, short connections, and dns.
You’ll note that none of these issues are essential for normal
operation, and several have easy fixes already in the pipeline.
Normal operation is pretty fine, actually.
1) After evaluating the performance of the current openwrt-based AQM
substitute will be implemented. #306 Regrettably the primary prototype of that
was QFQ based. #312 The SFQRED implementation will be used instead, which should
work well, except with bittorrent. Unless I figure out how to do the same
thing with DRR, or get QFQ working.
2) A gui for creating the AQMs and measuring bandwidth will be added
3) Hopefully the wins related bugs with XP vs Vista will be resolved
by somebody. #314 I still lack hardware to test that. I do not intend to
actually ship samba pre-installed at this point, but can be persuaded
otherwise if something can be made to ‘just work’.
4) Working ds-lite support (dibbler? wide? what?) #274
Please give this one a shot. It’s the first build to show significant
differences in performance since
august. Actually, most bottlenecks have moved to my laptop(s) and servers! I suggest running BQL enabled
kernels on your desktops/laptops with the ‘debloat’ script in order to see best results.
the debloat repository is being maintained separately from cerowrt:
A lot of glue is required as yet to make the various pieces function
but I do hope you notice a difference in overall performance in normal use. With a new external AQM we’ll do
better, but I’d like people to be exercising that code, suggesting features, etc, before I commit
to starting up a more formal release cycle, and product definition.
I am still toying with the idea of moving forward directly into Linux
3.3, rather than continuing
to backport to 3.2.
That said, I won’t be hurt if you delay until after I get the newest AQM installed and working by default.
My hope would be mid-feburary for that.