have you played with that? on wiki sayang (i picked one of them)
“total-limit-at (NUMBER/NUMBER): corresponds to limit-at”
so try: /queue simple add limit-at=2m/1m total-limit-at=3m/2m or other way around.
Of course, you have to fill the rest of max limit,
burst if you want
thanks, yes I played with it, but its not clear to me.
MT writes (in their wiki) about the total-stuff:
And corresponding options for > global-total HTB queue> :
I know, the global queue stuff is related with Queue Trees - not Simple Queues.
This is stated here too:
and:
You see, the “HTB global (Queue Tree)” is always prior the Simple Queues.
It makes sense that the Total limts have priority of the General/Advaned limits, because they are in the Packet Flow prior the Simple Queues.
But what are the reasons to set the limits in the Total tab insed of the General/Advanced tab? They are processed one step prior the Simple Queues. But are there advantages or disadvantages? We know, Queue Trees use a single CPU-core only. Is this (Total) related to the single-core-limitation of the Queue-Trees?
Or is this for Parent/Child scenarios? The Parent with limits under the Total tab and Child with limits under the General/Advanced tab?