V7.20beta [testing] is released!

[fischerdouglas]

Well, the “lease script” can do absolutely nothing for “client authorization”, as it is called after a lease has already been acknowledged.
It is intended to provide a hook to handle new systems, e.g. to create a DNS record, to send an alert mail when new systems join the network, etc.
I have proposed before that a “pre-lease script” could be added that is called when the request comes in, and that can examine the request parameters and decide whether a lease should be granted, from what pool, etc. In that functionality, mapping of requests to RADIUS could also be done, e.g. by setting some magic variables (that RouterOS first sets to a default, and that the user can then modify when desired).

Rewrite Radius-Request username with Circuit-ID DHCP-Option82 or PPPoE+

Suggestion: Hooks to Scripts on /routing/filter/rule actions