MikroTik MTCTCE lab 5 of 8
Queue types: FIFO, SFQ, RED, fq-codel and CAKE against bufferbloat
Riverside's staff say the Internet is fine until someone downloads, then calls and games lag by seconds. Reproduce the problem, bufferbloat, with a big FIFO queue, measure the ping times under load, and fix it with the modern queue types in RouterOS 7: fq-codel in a queue tree, then CAKE on the interface, which shapes, separates flows and controls delay on its own. Meet SFQ and RED on the way.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 768 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 05 - Queue types - FIFO SFQ RED fq-codel and CAKE against bufferbloat
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 3 vCPU, 768 MB
- Smallest plan
- Lite
The scenario
Riverside's downlink is shaped to 512k (small numbers because of the CHR licence; lab 2 explains). Staff report that everything is fine until someone starts a download; then calls stutter and remote desktops lag by seconds. That's bufferbloat: a queue so big that packets wait in it for seconds. You'll reproduce it, measure it, and cure it with the right queue type.
| Device | Address | Role |
|---|---|---|
| NET | 192.0.2.1/30 | the Internet, bandwidth-test server |
| RIVERSIDE | ether1 192.0.2.2/30 · ether2 192.168.50.1/24 | the office router |
| PC1 | 192.168.50.11 | a RouterOS router playing a staff PC |
What you’ll practise
- Explain FIFO, SFQ, RED, fq-codel and CAKE and what queue size does to delay
- Create queue types and attach them to a queue tree leaf or an interface
- Measure latency under load with a background download and ping
- Shape and manage a link with CAKE alone
The tasks
- The queue types
- Reproduce bufferbloat
- Cure it with fq-codel
- SFQ and RED
- CAKE on the interface, no tree needed
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- NET
ether1to RIVERSIDEether1 - RIVERSIDE
ether2to PC1ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| NET | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| RIVERSIDE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCTCE RouterOS v7 guided labs.Open
05 - Queue types - FIFO SFQ RED fq-codel and CAKE against bufferbloatand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More MikroTik MTCTCE labs
Related labs in other courses
CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.