Basic bandwidth limiting

Hi,

There are a few bits of information about limiting bandwidth on Mikrotik Routers. They seem either overly simplistic or geared towards bigger per user setups. None really cover what I’m trying to do.

I have a HaP AC acting as my router with an IP of 192.168.8.1 My main WAN is eth1.

I want a simple queue that limits bandwidth to 2Mbps for every device connected to the router.

This was an attempt (attached) from reading some of the resources. (excuse the 512Kbps, that was just me playing around).

Anyway, it doesn’t seem to work, or I can’t test it. If I run a speed test for example on fast.com I see it returns 14Mbps.

Obviously I’ve done something wrong. Can anyone help me get it right?
Screenshot 2020-07-04 at 14.55.38.png

Check whether you have fast path allowed, this setting will bypass queues.

Sent from my SM-G965F using Tapatalk

The following CLI command limits both upload and download to 1Mbps for clients in LAN 192.168.128.0/24 behind ether3:

/queue simple
add name=myRateLimiting target=192.168.128.0/24 max-limit=1M/1M dst=ether3

with “print” you can see it with the other fields it has, for example:

print
Flags: X - disabled, I - invalid; D - dynamic
0 name=“myRateLimiting” target=192.168.128.0/24 dst=ether3 parent=none packet-marks=“” priority=8/8 queue=default-small/default-small limit-at=0/0 max-limit=1M/1M burst-limit=0/0
burst-threshold=0/0 burst-time=0s/0s bucket-size=0.1/0.1

>

Instead of etherX you can also specify a bridge, if one exists in your router setup.

See also https://wiki.mikrotik.com/wiki/Manual:Queue#Configuration_Example

I’m not sure how that works. Changing that to my system e.g. 192.168.0.0/24 and ether1, doesn’t seem to have any affect when running a speed test.

I have already read the wiki, but like I said the examples don’t seem to work for me. I was hoping someone had a proven working example and perhaps a better way to test it.

[admin@MikroTik] > /queue simple print   
Flags: X - disabled, I - invalid, D - dynamic 
 0    name="Limit1" target=192.168.8.0/24 dst=ether1 parent=none packet-marks="" priority=8/8 queue=default-small/default-small limit-at=0/0 max-limit=1M/1M burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s 
      bucket-size=0.1/0.1

If I run a speed test I get over 14Mbps. Since the online speedtests work by downloading/uploading, any limit should be easily be showing and working.

suggest reviewing some basic videos on the subject.
https://www.youtube.com/watch?v=MPxVWlqmWOI
https://www.youtube.com/watch?v=rvWz27zaL_Y&t=23s
https://www.youtube.com/watch?v=DucfnXn_J28

Thanks but they aren’t really getting to the point of what I want to do. It’s more background stuff. Though Video 10 does exactly as I’ve already done.

It might just be that I’m testing wrong or don’t know how to test it.

I was really expecting someone to be able to say, “ah this is where you’ve gone wrong” so I know what to change. Then further reading could be done should I require greater understanding for more complex setups.

I hoping it to be a 30 second job, and other than turning it on an off as desired I’d never look or need to do again.

It’s basically just a limit for when I’m using websites that only have adaptive video. Lowering the bandwidth forces them to provide a lower quality stream and stretches my finite data plan a little further.

Have you checked fast path setting?

Sent from my SM-G965F using Tapatalk

Post your config here, the snippets shown are not the same thing and without the total picture, advice could be spotty.
/export hide-sensitive file=anynameyouwish

Also this may prove to be informative…
http://forum.mikrotik.com/t/using-routeros-to-qos-your-network-2020-edition/66683/1

Do you have fasttrack enabled?

Asked and not answered twice, maybe 3rd time lucky :slight_smile:

Sent from my SM-G965F using Tapatalk

3rd time? I see it was asked yesterday when I was busy. Where is the time before that?

Seems to be enabled in my firewall. Should it not be? There was no mention of that in the wiki nor in the video.

Does it have to be off for simple queues, or when one uses mangling rules for more complex queues??

This has been discussed before.

And a quote from fasttrack manual:

Note that not all packets in a connection can be FastTracked, so it is likely to see some packets going through slow path even though connection is marked for FastTrack. This is the reason why fasttrack-connection is usually followed by identical action=accept rule. > FastTracked packets bypass > firewall, connection tracking, > simple queues> , queue tree with parent=global, > ip traffic-flow> (restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure FastTrack does not interfere with other configuration;

(emphasis is mine).

That was it. Disabling Fasttrack and the issue is solved.

Thanks to all

Posts #2,7 + 9
Glad you found it!

Sent from my SM-G965F using Tapatalk