V
V
Vladimir Kivva2015-09-01 20:24:30
System administration
Vladimir Kivva, 2015-09-01 20:24:30

How to configure traffic prioritization on Mikrotik?

Task: to freely surf the Internet with the torrent turned on to the maximum
Given: Miktorik rb951hnd (RouterOS 6.30.1), the Internet receives via an LTE modem (router mode), about 20 megabits. Wired client.
When I turn on the torrent without restrictions on the client (namely, this is how it needs to be configured, because not everyone knows how to limit) - it is almost impossible to work in the browser.
Tried:

  • wiki.mikrotik.com/wiki/Traffic_Prioritization_Script - nothing has changed
  • habrahabr.ru/post/131295 - the script works only on 5 versions of RouterOS, and 5x does not see my LTE modems.

With the second option plugging in the lines:
/queue tree
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 max-limit=10M name=DOWNLOAD parent=global-out priority=8
add burst-limit=0 burst -threshold=0 burst-time=0s disabled=no limit-at=0 max-limit=10M name=UPLOAD parent=global-total priority=8

because in the 6th version of Mikrotik, global-out and global-total were replaced with one global. I don’t know what to do with it, just renaming it to global didn’t help, traffic doesn’t get into the queue.
Does anyone have experience with this kind of setup?
P.S. If you limit the torrent in this way, then the download speed of the torrent drops, and surfing does not get better

ip firewall filter add chain=forward action=add-dst-to-address-list protocol=udp dstaddress=10.0.0.2-10.0.0.254 address-list=dst_list address-list-timeout=0s
ip firewall filter add chain=forward action =accept dst-address-list=dst_list dst-limit=250,250,dstaddress/1m40s
ip firewall filter add chain=forward action=reject reject-with=icmp-admin-prohibited dst-addresslist=dst_list

Answer the question

In order to leave comments, you need to log in

3 answer(s)
K
Kirill, 2015-09-01
@CMHungry

With a narrow external channel, you won’t be able to make yourself comfortable surfing, since QoS policies normally work only on the outgoing interface. What falls down from the provider - then falls down, and it is impossible to control this flow in any way.
Imagine a pipe through which 60 apples fall per minute. Who throws apples, we do not know. But there are 60 of them per second. Apples go green - torrent and red - surf. We take 10 seconds. In these 10 seconds we will get 600 apples. What - and as it falls, we will get it. And for comfortable surfing, we need, conditionally, 200 red apples. If they fall to us on our Mikrotik, then we are lucky. And if 550 greens and 50 reds arrived, then we can do anything with the greens, but we won’t make 200 out of 50 reds ...

I
Ivan, 2015-09-01
@LiguidCool

I config through the face and a slightly different task, but I think the logic is something like this:
1) Firewall -> Mangle. In General you specify the necessary traffic in Forward , you mark it with Action ( mark packet )
2) Queue - Queue Types - you actually create a speed limit.
3) Queue - Queue Tree - compare the traffic speed with which marking.
You make a rule for the web (80 and 443 ports) and, accordingly, everything else.
PS
I made a restriction for each user of the network, so that one person does not completely clog the channel. I can upload screenshots.
PPS
Well, or if this is your torrent and you know its port, then everything is even easier...

B
bukass, 2015-10-05
@bukass

Discover PCQ and download at least the whole office, everyone will get it equally.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question