Page 1 of 1

Can't set limit-at to zero in simple queue?

Posted: Sat Jan 27, 2007 10:02 pm
by firebat
I have a simple queues setup to bandwidth limit customers and am using bursting. I would like to set CIR to 0 for most of the customers (limit-at). However, it won't let me set it to zero in winbox. It defaults back to unlimited. How do I set limit-at (CIR) to zero and still support bursting, etc?

Posted: Sun Jan 28, 2007 2:11 am
by 111111
block user by MAC address (if is user) static ARP is needed
just change first symbol of his MAC address

Posted: Sun Jan 28, 2007 2:21 am
by firebat
I don't want to block a user. What I am trying to do is set a customers CIR to zero so that at times of congestion, those customers at the same level that have a non zero CIR will get their bandwidth before the rest of the bandwidth is divided amongst all other users with a zero CIR.

Posted: Sun Jan 28, 2007 7:59 am
by abab_rafiq
You may set those IP's CIR to 1 bps/s. This type of queuing will keep some bandwidth free


Posted: Sun Jan 28, 2007 8:37 am
by firebat
Why can't you set it to zero? Is there a reason? Mikrotik folks?

Posted: Sun Jan 28, 2007 9:31 am
by mneumark
Another thing you might want to consider is a firewall rule to block all traffic from that customer.

Posted: Sun Jan 28, 2007 9:39 am
by firebat
I don't want to block traffic. What I am trying to achieve is the following:

I have some customers that must have guaranteed BW of 100K. The rest of the customers do not have guaranteed BW. Thus, I want to set the rest of the customers to 0 CIR and leave the queue priority amongst all customers the same. Thus, at congestion time, the customers with 100K CIR will get their BW first and the remainder will be distributed amongst all customers.

Posted: Sun Jan 28, 2007 10:00 am
by mneumark
Well CIR is the commited rate. If you have it set to 0 then you are commiting to no bandwidth at all. I do agree with you it should all the input of zero, but to my knowledge most providers has a CIR of at least 1.

Posted: Sun Jan 28, 2007 11:14 am
by firebat
Yes, there should not be a need for a comitted rate for normal internet customers. If they need it, it costs extra :).

Posted: Sun Jan 28, 2007 1:15 pm
by valens
I don't know why you can not do it,
but I think 1 will be the same with 0.
No one can feel any different.

Posted: Mon Jan 29, 2007 10:15 am
by sergejs
As far as I know 0 is equal to unlimited.
You can set 1,2,3; anyway unless you will set at least ~>10k, user will not be able to get any suitable communications.

Posted: Tue Jan 30, 2007 5:49 am
by firebat

It is not uncommon to have 0 CIR SLAs. Is there something specific to the mikrotik implementation that requires a specific minimum BW or did you mean that 10K is needed for connections in general? What is the suggested minimum value for provisioned users? CIR should only be used if there is severe congestion. Can you explain the algorithm used when a link becomes suggested? Do all connections fall back to CIR or balanced based on CIR?

Posted: Tue Jan 30, 2007 10:04 am
by normis
if you set it to one (or any small number close to zero), no traffic will be able to pass from-to this customer. essentially this means killing the customer. that is not what you want, so maybe you need to reformulate your question :)

Posted: Tue Jan 30, 2007 10:36 am
by firebat
Thanks Normis for the reply. Questions and comments:

CIR is committed information rate. We also have Max Limit and burst limit. At times of no congestion, we should be running at the Burst limit or Max limit. CIR is the comitted/guaranteed rate but you should be able to run at Max limit in times of no congestion. Are you indicating that if the CIR < Max limit, that Mikrotik OS only provides the CIR? That makes no sense. How can a CIR of 0 yeild no traffic in times of no congestion. If all customer are set to 0 CIR, no customer will get bandwidth? The correct implementation at times of congestion is to provide CIR to all customers and then split the Bandwidth amongst all users above the total combined CIRs. At time of no congestion, you provide Max limit. (These statements assume all queues are at the same level)

So, what exactly is the implementation that MT uses?

As far as what I am trying to accomplish, I had this other thread that disusses it. I need to provide quaranteed bandwith to some premium customers and thus the CIR for all other customers must be low:

Posted: Tue Jan 30, 2007 1:30 pm
by macgaiver
OMG :)

limit-at=0 equals limit-at=unlimited equals limit-at=unspecified

thats all!

Just specify necessary limit-at rules with higher priority than all other non limit-at rules

Posted: Wed Jan 31, 2007 4:47 am
by firebat
If I set the the limit-at rule priority higher than other customers, the customer at the higher level will get more bandwidth due to MAX-limit.

I wanted to understand what Normis's comment.