MikroTik MTCTCE lab 2 of 8
Simple queues: limits, parents, order and burst
Share Fernvale's Riverside office uplink between two staff PCs with simple queues: per-PC limits in both directions, a parent queue for the whole office, the first-match order that decides which queue a packet uses, and burst, which makes short downloads feel fast without raising the long-term rate. Every rate is measured with RouterOS's own bandwidth test.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,024 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 02 - Simple queues - limits parents order and burst
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 1,024 MB
- Smallest plan
- Lite
The scenario
Fernvale's Riverside office has two staff PCs behind its router, and a small uplink that one big download can fill. You'll share it with simple queues: a limit per PC, a parent queue for the whole office, and burst so that short downloads finish quickly.
About the rates in this course. Our virtual routers run RouterOS's free licence, which caps each interface at about 1 Mbit/s. So every rate is in kbit/s, well under that cap; the configuration is the same as at 100 Mbit/s. Measured rates come out a few per cent under the configured limit, and vary a little from run to run.
| Device | Address | Role |
|---|---|---|
| NET | 192.0.2.1/30 | the Internet, with a bandwidth-test server (no login needed) |
| RIVERSIDE | ether1 192.0.2.2/30 · ether2 192.168.50.1/24 | the office router, where the queues live |
| PC1 · PC2 | 192.168.50.11 · 192.168.50.12 | RouterOS routers playing staff PCs |
What you’ll practise
- Read a simple queue's target, max-limit and limit-at, and which value is upload and which is download
- Measure a queue's effect with /tool bandwidth-test
- Build a parent queue and child queues, and explain the first-match order of simple queues
- Configure burst-limit, burst-threshold and burst-time, and predict how long a burst lasts
The tasks
- Measure before you shape
- A queue per PC
- A parent queue for the office
- Queue order: the first match wins
- Burst
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 Office (network) - PC1
ether1to Office (network) - PC2
ether1to Office (network)
| 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 |
| PC2 | 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
02 - Simple queues - limits parents order and burstand 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.