MikroTik MTCTCE lab 3 of 8
HTB queue trees: structure, dual limitation, priority and DSCP
Riverside's phones share the uplink with everyone's downloads, and calls break up whenever someone pulls a big file. The voice provider already marks its packets with DSCP 46. Classify by DSCP with mangle, build an HTB queue tree with a guaranteed rate and top priority for voice, and measure how HTB shares the link when both classes are busy.
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 03 - HTB queue trees - structure dual limitation priority and DSCP
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 1,024 MB
- Smallest plan
- Lite
The scenario
Riverside's phone system (VOICE, 192.168.50.11) and the staff PCs share the office's downlink. When someone starts a big download, calls break up. The voice provider already marks its packets DSCP 46 (EF) on the way in. You'll build an HTB queue tree on the LAN interface that guarantees voice a share, gives it priority over everything else, and lets downloads use whatever is left.
Rates are in kbit/s because of the CHR licence's cap (lab 2 explains); the shape of the tree is what matters.
| Device | Address | Role |
|---|---|---|
| NET | 192.0.2.1/30 | the Internet, bandwidth-test server; marks traffic to VOICE as DSCP 46 |
| RIVERSIDE | ether1 192.0.2.2/30 · ether2 192.168.50.1/24 | the office router |
| VOICE | 192.168.50.11 | the phone system's gateway (RouterOS) |
| PC2 | 192.168.50.12 | a staff PC (RouterOS) |
What you’ll practise
- Explain HTB's inner and leaf queues, and how limit-at, max-limit and priority share bandwidth
- Classify traffic by DSCP with mangle packet marks
- Build a queue tree on an interface with a parent and two leaf classes
- Measure dual limitation and priority with two simultaneous downloads
- Map DSCP to RouterOS priority with set-priority
The tasks
- Watch voice suffer
- Classify by DSCP
- Build the HTB tree
- Measure the sharing
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) - VOICE
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 |
| VOICE | 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
03 - HTB queue trees - structure dual limitation priority and DSCPand 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.