
Hello everyone:
After the update v6.17, I found that it seems much this option.
See the WIKI, found no explanation of this option.
Can someone tell how this function with the choice?
Grateful ![]()

Hello everyone:
After the update v6.17, I found that it seems much this option.
See the WIKI, found no explanation of this option.
Can someone tell how this function with the choice?
Grateful ![]()
you can add rate limitations to the customer as it gets dhcp-lease. This setting governs where new dynamic queue is added as queue order is important.
Hi Janis.
Is there a RADIUS attribute for this?
Why was this very awesome change not part of the change log?!? ![]()
I think this change was not introduced in 6.17, but much earlier.
janisk, are there any chances for more improvements in dhcp leases in the future versions of RouterOS? I was asking about it in this post http://forum.mikrotik.com/t/feature-request-dhcp-leases-improvements/78960/1 ?
santa is correct. That is an old feature added some time ago, i do not even recall when it was made. Most probably during 6.0rc or 6.0beta phase.
Cool feature!, so is there a radius attribute to control this ?
yes, dhcp can be controlled via radius. Set where queues have to be placed and you can get rate limitation settings from RADIUS.
I just checked and it appears you can only do this on a per-lease basis.
How do we set the queue placement for a lease from RADIUS ?
of course, you do that per lease - every new lease will get its limitation. If you want to do some grouping you could give out address-list name and thus, bunch customers together.
or i not understand you correctly.
Oh… I was under the impression that this is a per-server setting… that I could set every dynamic lease to also create a dynamic queue.
On closer inspection, it appears you’re right… My oldest RouterOS installation is 6.9, and it indeed has this feature for static leases.
Then I have a tiny feature request… make this doable for dynamic leases as well? I mean, sure, one could make a lease script that makes a lease static as soon as it’s created, and adds those settings, but it would be more convenient (and less error prone) if that could be done by a server setting.
If you want to use radius and create SQ for every lease, just add proper reply attribute to the client configuration.
My simple client configuration:
"11:22:33:44:55:66" Cleartext-Password := "", NAS-Identifier == "mt-gdansk", Auth-Type := Accept
Framed-IP-Address = 172.16.100.1,
Framed-IP-Netmask = 255.255.255.0,
Mikrotik-Address-List = "clients_tariff1"
To create SQ you need to add this one:
Rate-Limit
Everything is described here: http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server , take a look at “Access-Request” and “Access-Accept”.
In my opinion you can’t set “insert queue before” using radius.
that is correct, it is part of the configuration of DHCP-server where to place queues.
I understand how to do this. We are already using Mikrotik-Rate-Limit to set up a simple queues for DHCP leases dynamically from RADIUS.
My question was how we can set the “Insert Queue Before” option in a RADIUS response.
This appears to be done on a per-lease basis, not on a per-server basis. So that means that if it is done per-lease that if we are allocating leases from RADIUS we would need to respond per-lease from RADIUS to let RouterOS know where to “Insert Queue Before”…
Or maybe I have completely misunderstood the purpose of the “Insert Queue Before” feature. Janis, I cannot find anything on the Wiki describing this feature in detail, can you perhaps put something up ?