Best OpenWrt routers for SQM (2026)
SQM with CAKE is the only real fix for bufferbloat — but it costs CPU. A router that shapers your line at full speed must have the compute to pace every packet. This guide matches CPU classes to bandwidth tiers, lists the boards the community actually uses (plus our own benchmark device), and what to avoid. As of 2026-11.
The one rule: match CPU to your line speed
CAKE inspects, classifies and paces every packet. Rough community-consensus throughput by SoC class (piece_of_cake, bidirectional worst case):
| SoC class | Examples | CAKE at (approx.) |
|---|---|---|
| Dual-core MIPS ~880 MHz | MT7621 (many budget boards) | 150–250 Mbps |
| Quad Cortex-A53 2 GHz | MT7986 (BPI-R3, Flint 2), RK3568 (R5C/R5S) | 500 Mbps – 1 Gbps |
| Quad Cortex-A55/A76+ | RK3588 (R6S/R6C), IPQ807x | 1–2.5 Gbps |
| x86 dual/quad core | N100/N305 boxes (CWWK, Topton etc.) | 1 Gbps+ with headroom |
Numbers are community lore plus vendor datasheets, rounded down; NAT, VPN or traffic accounting on the same box eats into them. Check the OpenWrt Table of Hardware and forum threads for the exact board.
Picks by tier
Some links below are Amazon affiliate links (tagged) — they cost you nothing extra and help keep this site free. Products not sold on Amazon link to their official stores. As an Amazon Associate we earn from qualifying purchases.
≤ 300 Mbps lines
Any MT7621 board is fine (used market is full of them). 256 MB RAM minimum so SQM + LuCI + stats breathe. This tier is where cheap routers stop being embarrassing.
300 Mbps – 1 Gbps
Quad-core A53/A55 class: GL.iNet Flint 2 (MT7986, Wi-Fi 6, polished OpenWrt build), Banana Pi BPI-R3 (MT7986, tinkerer favourite, official store), FriendlyElec NanoPi R5C/R5S (RK3568 — our own benchmark device; runs CAKE on a 1000/50 line with 7.8 ms loaded latency, FriendlyElec).
Multi-gigabit / power users
NanoPi R6S/R6C (RK3588S, 2.5 GbE ports) or an x86 N100/N305 box with 2.5 GbE Intel NICs (N100 boxes on Amazon). x86 also leaves room for containers, AdGuard, VPN. Add RPS/IRQ spreading so a single core does not become the receive bottleneck.
What to avoid
- ISP combo units — no real queue management, no control. Bridge them and put your own router in front.
- 64/128 MB RAM boards — SQM plus LuCI plus anything else will OOM. 256 MB is the floor, 512 MB+ is comfortable.
- Buying Wi-Fi generation instead of CPU — Wi-Fi 7 does nothing for bufferbloat. A dedicated OpenWrt router + a plain access point often beats an all-in-one.
Setting it up
Hardware is only half of it. On OpenWrt: install sqm-scripts and luci-app-sqm,
pick the cake queue discipline, set upload/download to ~85–95% of your measured speeds,
enable ingress shaping — then re-run the bufferbloat test until loaded latency stays under
~20 ms. Full walkthrough with A/B numbers: OpenWrt SQM guide. With
NetSteer installed, all of it is one toggle and it self-configures from your measured line.
FAQ
What CPU do I need to run CAKE at gigabit speed?
As a practical 2026 rule of thumb: MT7621-class dual-core (~880 MHz) manages CAKE up to roughly 150–250 Mbps; quad-core Cortex-A53 at 2 GHz (MT7986, RK3568) reaches 500 Mbps–1 Gbps; any modern x86 (N100 and up) does gigabit CAKE with headroom. Price your router by your measured line speed, not the marketing number.
Is SQM better on Wi-Fi 6/7 routers?
Wi-Fi generation does not help SQM — queue management runs on the CPU and the WAN link, not the radio standard. An older MT7986 or an N100 box with CAKE beats a shiny Wi-Fi 7 router with no working SQM for latency. Buy Wi-Fi for Wi-Fi; buy CPU for SQM.
Do ISP routers support SQM/CAKE?
Most ISP combo units offer at best a basic QoS that shapes by priority but does not keep queues short. Very few expose CAKE. The usual fix is to put a small OpenWrt device in router mode in front of the modem, or bridge the ISP box entirely.