Hi
Would it work?
To only set the priority under queue - tree whitout any limits. ?
How would it know where the limit is to know when to prioritize traffic?
Thats why I´m asking =)
If their is no limit set, would it priority that data who has the lowest priority set under that parent.
edit. because you can add a child queue whitout any limit, why is that possible if it doesent work?
You want Low Latency Queueing, RouterOS currently doesn’t support it.
You can add your sig to a feature request wiki page, so developers will see it.
Thanks, did a quick research on google and found out that it was developed by cisco.
How do I vote for this feature?
Just post a feature request here.
But i also found the request here:
http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/Feature_Requests
Implement LLQ (Low Latency Queuing). Important for giving priority to one type of traffic over another, not just reserving bandwidth for each type. Especially important for growing number of VoIP implementations around the world.
This would be a GREAT feature !
Don’t sit and wait, until developers find time to understand that this is an useful feature. Just write one feature request on forum and wiki.
I Found this, http://wiki.mikrotik.com/wiki/DSCP_based_QoS_with_HTB
Seems that you can prioritize traffic without any limit.
DSCP is for marking packets only.
did you even read the attached link?
The stuff posted on that page works great as-is, but the OP was asking about being able to do it without first defining the amount of bandwidth available on the link. In other words, he doesn’t care how much bandwidth is being used, but he wants to give different priorities to different types of traffic. Personally, I have a queue on my home router, and it works wonders for giving games priority over my daughter’s youtube or torrents.
I wonder though… is there a way to use statistical data to determine the maximum data rate over the last XX minutes, and use that to dynamically update the queue to show 105% of the max used, then give different types of data different amounts of bandwidth.. VOIP 20%, SSH/telnet 10% to absolutely cover the +5%, http/s up to 60%, pop3/smtp 25%, etc…
This would also eliminate sudden bursts that could potentially cause disruption to the network. It would really smooth out the flow rates. It would also be a great way to keep torrent traffic from interfering with more interactive/important communications.
This might make for an interesting experiment if I remember to work on it when I free up some time.
-Troy
DSCP is for packets marking, it allows other routers to not mangle different types of traffic. Just catch packets with DSCP value in mangle and prioritize them in HTB.
would setting limit-at to a very small value (ex. 1500 bytes) simulate low latency queue behaviour?