MikroTik MTCNA lab 12 of 19
QoS: simple queues, burst and PCQ
Measure real throughput with iperf, cap one user with a simple queue, find out why FastTrack makes the queue do nothing, add burst, and then share the line fairly between every user with one PCQ queue.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,792 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 12 - QoS - simple queues burst and PCQ
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 4 vCPU, 1,792 MB
- Smallest plan
- Lite
The scenario
A co-working space shares one Internet line. One member's cloud backups run all day and everyone else's video calls stutter. The manager wants a hard cap on that member and, for everyone else, a fair share that adjusts itself as people come and go.
In this lab the "Internet line" is the router itself: a CHR on the free licence can send at most 1 Mbit/s out of each interface. That is your line speed, so every limit below is in kilobits.
| Device | Interface | Address | Role |
|---|---|---|---|
| GW | ether1 · ether2 | 198.51.100.1/24 · 192.168.88.1/24 | Co-working router |
| Server | eth0 | 198.51.100.10/24 | iperf server "on the Internet" |
| Client1 | eth0 | 192.168.88.21/24 | The member with the backups |
| Client2 | eth0 | 192.168.88.22/24 | Everyone else |
What you’ll practise
- Measure throughput through the router with iperf
- Create a simple queue with target, max-limit and limit-at, and read its statistics
- Explain why FastTracked traffic bypasses simple queues
- Configure burst-limit, burst-threshold and burst-time and predict the result
- Share bandwidth equally between users with PCQ queue types
- Explain how the CHR free licence limits a virtual router
The tasks
- Prepare the hosts and start the iperf server
- Measure the line
- Cap Client1 with a simple queue, and meet FastTrack
- Make the queue count
- Allow short bursts
- Share the line fairly with PCQ
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
- GW
ether1to Servereth0 - GW
ether2to Office-LAN (network) - Client1
eth0to Office-LAN (network) - Client2
eth0to Office-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| GW | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| Server | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| Client1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| Client2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCNA RouterOS v7 guided labs.Open
12 - QoS - simple queues burst and PCQand 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 MTCNA 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.