I was experimenting with tree queues and i found out this feature is “broken” in real world
i was triing to priorize internet trafic
give one device (pc 192.168.77.254 (static)) priority (and garanted trafic)
over other device (mobil 192.168.77.253 (static)
everything worked when i set everything to aproximate speed of my conection down 80M/up 20m (not guaranted) so to 79/19
but when i set it to 85/25 to mock times when it drops to guaranteed trafic ( that is 55% of 80/20)
nothing worked
- limit at was violated even at that moment it could be satisfied
- priorities was violated ( device with lover priority was able to get more bandwith)
There was at that time enought bandwith to satisfy both and i gived 30 seconds for shaper and nothing
just to be shure there are my mangle rules
/ip firewall mangle
0 chain=forward action=mark-packet new-packet-mark=pc-Up passthrough=no src-address=192.168.77.254 src-address-list="" log=no log-prefix=""
1 chain=forward action=mark-packet new-packet-mark=pc-down passthrough=no dst-address=192.168.77.254 log=no log-prefix=""
2 chain=forward action=mark-packet new-packet-mark=mobil down passthrough=no dst-address=192.168.77.253 log=no log-prefix=""
3 chain=forward action=mark-packet new-packet-mark=mobil up passthrough=no src-address=192.168.77.253 log=no log-prefix=""
Wokring ques setup
0 name="mobil download" parent=global down packet-mark=mobil down limit-at=0 queue=qos priority=5 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
1 name="pc download" parent=global down packet-mark=pc-down limit-at=0 queue=qos priority=2 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
2 name="pc upload" parent=global up packet-mark=pc-Up limit-at=11M queue=qos priority=2 max-limit=19M burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
3 name="mobil up" parent=global up packet-mark=mobil up limit-at=0 queue=qos priority=5 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
4 name="global up" parent=ether1 packet-mark="" limit-at=0 queue=default priority=8 max-limit=19M burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
5 name="global down" parent=bridge1 packet-mark="" limit-at=0 queue=default priority=8 max-limit=79M burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
and non working setup (only changes)
4 name="global up" parent=ether1 packet-mark="" limit-at=0 queue=default priority=8 max-limit=25M burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
5 name="global down" parent=bridge1 packet-mark="" limit-at=0 queue=default priority=8 max-limit=85M burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
custom queue is
name="qos" kind=sfq sfq-perturb=2 sfq-allot=1514
other details
routerOs version is 6.48
model: hap ac lite
fw: latets
speedtester: https://speedtest.cesnet.cz (lenght can be set in “Pokročilé nastavení”)
Just to point out this is not nentioned in documentation and kinda throws monkeywrech for soho users into qos-ing their trafic on network with big diferences between guaranteed and usualy available bandwith.
Feel free to correct me.
I would like to hear if this will/can be fixed. eather by mikrotik or by me by doing this in other way