Config Pro · Independent certification preparation

Simple queues for bandwidth limiting

Configure, verify and troubleshoot simple queues for bandwidth limiting on MikroTik RouterOS v7.

32 min read9 chapters2 labs15 quiz7 scenarios15 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

What you will learn: bandwidth control with simple queues

What you will learn in this module. By the end you will be able to explain why networks need bandwidth management, describe how RouterOS queues work (HTB, CIR and MIR, queue types), build simple queues that limit one host or a whole subnet, read upload and download correctly, configure burst so short downloads feel fast, build parent and child queues that guarantee bandwidth with limit-at, verify queues with statistics and torch, and troubleshoot queues that "do nothing". This is the first module of the MikroTik QoS track, aligned with the traffic-control (MTCTCE) level. The next module adds priorities, mangle marking, queue trees and PCQ.

Prerequisites. MTCNA basics: RouterOS CLI, IP addresses, the default route and masquerade NAT. You should know the difference between bits and bytes (8 bits = 1 byte; ISPs sell megabits per second, while downloads usually show megabytes per second).

Start with an analogy: water tanks and taps

Imagine a housing society that receives water through one main pipe. If one flat opens every tap to fill a swimming pool, every other flat gets a trickle. The society secretary fits a tap limiter on each flat: no flat can draw more than a set amount per minute, and every flat is promised a minimum flow even when the pipe is busy. The pipe is your internet link; the flats are users; the limiters are queues.

A queue on a router is two things at once: a speed limit (packets above the allowed rate wait or are dropped) and a waiting line (packets that cannot go yet wait in a buffer). Controlling both lets you share a link fairly, sell different speed plans, and protect important traffic.

PC110.0.0.10/24 R1queue pc1-limit5M/5M Internet ether1 Everything PC1 sends or receives through R1 is held to 5 Mbps

The first lab: one host behind R1, limited to 5 Mbps each way.

Why bandwidth control matters

  • Fairness. Without limits, one user's large download or cloud backup fills the link and everyone else suffers.
  • Service plans. ISPs and hotels sell 10 Mbps, 50 Mbps and 100 Mbps plans from one big uplink. Queues enforce each plan.
  • Latency. When a link is full, packets wait in buffers and every application, including voice calls and games, gets laggy. Shaping traffic just below the real link speed keeps the waiting line in your router, under your control.
  • Guarantees. A finance team or a point-of-sale system can be promised a minimum rate even during peak hours.

Upload and download, from whose point of view?

This trips up almost every beginner. In a RouterOS simple queue, max-limit=2M/10M means upload 2M / download 10M from the point of view of the target (the user). Upload is traffic the target sends; download is traffic the target receives. The lab uses 5M/5M, so direction does not matter there, but in real plans it almost always does.

How this module is organised

ChapterTopic
2How RouterOS queues work: HTB, CIR, MIR, queue types
3Anatomy of a simple queue
4Lab walkthrough: limit one host (pc1-limit)
5Lab walkthrough: limit a subnet (lan-limit)
6Burst: fast starts, fair averages
7Parent and child queues, guarantees with limit-at
8Troubleshooting workflow
9Summary and exam checklist

Worked example. A small office has a 50 Mbps link and 20 staff. Without queues, a single cloud backup reaches 48 Mbps and video calls freeze. With a simple queue giving each PC max-limit 10M/20M, the backup is held to 10 Mbps upload, leaving room for everyone else. Nobody notices a difference in browsing, and the calls stay clear.

Common beginner mistake. Confusing bits and bytes. A queue of 8M allows about 1 megabyte per second, which a download manager shows as "1 MB/s". The queue is working correctly.

The cyber cafe that lost customers

A cyber cafe with a 30 Mbps line had complaints every evening that "the internet is slow". Torch showed one machine running a game update at 28 Mbps. The owner added a simple queue per machine with max-limit 5M/5M. The next evening the update took longer, but every other customer browsed smoothly and the complaints stopped.

Lesson: bandwidth problems are usually sharing problems, and queues are the sharing tool.

"What is QoS and why would you rate-limit users?"

Say QoS means controlling how a limited link is shared: limiting rates, guaranteeing minimums, prioritising sensitive traffic and keeping latency low. Rate-limiting stops one user or application from starving others, enforces sold service plans and keeps queuing delay inside your router where you can manage it. Mention RouterOS simple queues and the upload/download order.

Key takeaways

  • A queue is both a speed limit and a waiting line.
  • Bandwidth control gives fairness, service plans, low latency and guarantees.
  • max-limit=upload/download is from the target's point of view.
  • 8 Mbps is about 1 MB/s: watch bits versus bytes.
  • Lab: pc1-limit 5M/5M for 10.0.0.10, then lan-limit 10M/10M for 10.0.0.0/24.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. How RouterOS queues work: HTB, CIR, MIR and queue types
  2. Anatomy of a simple queue
  3. Lab walkthrough: limit one host to 5 Mbps (pc1-limit)
  4. Lab walkthrough: limit a whole subnet (lan-limit)
  5. Burst: fast starts with fair averages
  6. Parent and child queues: guarantees with limit-at
  7. Troubleshooting simple queues
  8. Summary and exam checklist

Join the community