Simple Queue - what traffic is limited?

RouterOS General
1

Hi, sorry for my basic question but I am thinking what does simple queue limit?

like this:

/queue simple
add burst-limit=0/30M burst-threshold=0/5M burst-time=0s/10s max-limit=8M/16M \
    name="TEST" queue=wireless-default/wireless-default \
    target=192.168.1.3/32

Does this limit all the communication of client on 192.168.1.3 to anywhere (to internet interface of the router?, to every other lan interfaces on the router?, to MikroTik router itself?)? If all is truth, am I able to limit only the direction to/from WAN interfaces with such simple queues?

Thanks for the clean answeer :slight_smile:

2

It will limit the traffic to/from that host from/to all the other Networks…

3

OK that is what I expected. So now, if the queue will be full, it will also affect communication to DNS server directly on MikroTik router and other DNS server on LAN and or communication to local server on LAN which I do not want to limit. So what is the solution? I am thinking about one of these:

  • fastrack mentioned communication from LAN to LAN and LAN to MIKROTIK (incl. DNS?) and it will bypas this queue?
  • specify destination on queue (but there is an option for one interface only, not group of intefaces - I have 2 WAN)?
  • use packet marks in the queue?
4

and or communication to local server on LAN which I do not want to limit

To all the other networks, as indicated in my previous post. Since your Server and that host are on the Same Lan ( same Network ) there will be no traffic limit between them …
( It can be limited, but that’s not the case here )

5

OK so

  • communication to router itself - the same LAN - not limited, so the DNS aswers will not be affected? :slight_smile:
  • communitation to other LAN interface - different network - limited (so need to set LAN to LAN fasttrack rule?)
6

You can as well exclude that destination address/subnet from your Queue rule…

7

The RouterOS DNS service is running inside the router, you can see that as “a different LAN” in this context.
The only thing excluded from the Simple Queue (without further config) is the traffic being switched or bridged between ports that are configured in the same LAN.

However, it should not really matter. Under normal circumstances the queue will not drop much traffic, it will mostly just delay it a bit.
And when a user has saturated his queue with a lot of download traffic, he is probably not that interested in DNS traffic at that time.

8

so you mean another target simple queue with “!”?

9

DNS as different network… hmm , so to avoid delays in DNS communication I should set rule to fasttrack DNS?

10

No not “DNS as different network” but “inside router and outside on LAN as different network”.
EVERYTHING that passes through the router (and not only through the switch) is passed through the queue.

There is no need to do such settings (you cannot do that anyway), everything will work fine.

11

what would happen if the target is changed to an interface?

Would burst applied to each client going through this interface or is the traffic through this interface accumulated, means user 1 could consume all burst bandwidth if user 2 connects later.

/queue simple
add burst-limit=0/30M burst-threshold=0/5M burst-time=0s/10s max-limit=8M/16M \
    name="TEST" queue=wireless-default/wireless-default  target=VLAN_GUEST