Mikrotik Bandwidth Management Using Simple Queue

Mikrotik Bandwidth Management Using Simple Queue

The most frequently used bandwidth management on Mikrotik is Shared Bandwidth Management Mikrotik and Simple Bandwidth Management Mikrotik. These two techniques have different purposes and functions and are used for different needs. Following are the differences:

  • Shared Bandwidth Management Mikrotik is used to allocate bandwidth for each client at a rate that varies depending on whether other clients are active on the network. By using this method, if one client is not active (offline), the bandwidth allocation will be given to another client.
  • Mikrotik Simple Bandwidth Management is used to allocate Mikrotik bandwidth simply (simple) using the Mikrotik Simple Queue menu. By using static bandwidth control, the Mikrotik bandwidth allocation for each client will remain. For example, client 1 will get a bandwidth allocation of 256kbps/256kbps, as well as client 2.

In this article, we want to provide a complete tutorial on both bandwidth management methods on Mikrotik. Here is the full tutorial:

Mikrotik Simple Bandwidth Management Tutorial Using Simple Queue

For example, client 1 will get a bandwidth allocation of 256kbps/256kbps, as well as client 2:

The commands that can be used are as follows:

queue simple add name=limit-1 target-addresses=10.10.10.10 max-limit=256000/256000

queue simple add name=limit-2 target-addresses=10.10.10.20 max-limit=256000/256000

Or you can also use Winbox, go to the Queues menu –> Simple Queues

Intsall Foam Inside The Keyboards C...
Intsall Foam Inside The Keyboards Case

Testing or monitoring of bandwidth activities that have been limited can be seen using the torch menu, and the monitored interface is the ether2 interface, because this interface is connected to the local network. The command used is as follows:

tool torch ether2 src-address=10.10.10.0/24

Or you can use Winbox, go to the Tools menu -> Torch

Thus the Mikrotik Indonesia Tutorial about Mikrotik Simple Bandwidth Management Using Simple Queue. Please try and adjust yourself to the network conditions used.

Mikrotik Shared Bandwidth Management Tutorial Using Simple Queue

Continuing the previous scenario about Simple Bandwidth Management Mikrotik, let’s say there are 2 clients, namely client 1 and client 2, each of which will get a bandwidth allocation of 256kbps/256kbps. So the total bandwidth for the two clients is 512kbps/512kbps. If client 1 does not use its bandwidth allocation, then the bandwidth allocation will be given to another client, so that client 2 will get the maximum bandwidth allocation.

The first configuration that is done is the configuration to limit bandwidth usage for both clients at once.

This configuration also serves as a parent bandwidth limitation. The commands that can be used are as follows:

queue simple add name=limit-all target=10.10.10.0/24 max-limit=512000/512000

Furthermore, a configuration is made to limit the bandwidth usage of each client by using the previous configuration as the parent. The commands that can be used are as follows:

queue simple add name=limit-1 target=10.10.10.1 max-limit=512000/512000 limit-at=256000/256000 parent=limit-all

queue simple add name=limit-2 target=10.10.10.2 max-limit=512000/512000 limit-at=256000/256000 parent=limit-all

Now we try to check by monitoring the bandwidth allocation of the two clients using the proxy torch tool.

1. When both active clients use the entire allocated bandwidth (512kb)

2. When one client is not active (offline), bandwidth will be given to another client.

Thus the Mikrotik Indonesia Tutorial about Mikrotik Shared Bandwidth Management Using Simple Queue. Please try and adjust yourself to the network conditions used.