Anyone here with experience using the RADIUS server backend for DHCP server?
I am thinking about adding some functionality to a DHCP server where the supplied lease depends on some parameters in the request.
Of course I can make some feature request to add such functionality to the DHCP server (e.g. in a way similar to the ISC DHCP server, where you can define a number of classes and then have several scopes each with an “allow members of class” statement), but who knows if that is ever going to be implemented…
I see the RouterOS DHCP server is supporting RADIUS as a backend, but unfortunately the documentation is terse. As usual in MikroTik documentation, there is a list of all parameters you can set, but no overview of how it is going to work.
I don’t like the idea of the router becoming completely dependent on a RADIUS server for its DHCP service, so I wonder if there is any fallback to local processing.
Therefore:
- when you do use RADIUS backend, are the issued leases still stored locally on the router as usual?
- when there is no reply from the RADIUS server, can the router still issue leases from a local pool?
When so, I could consider constructing a special RADIUS setup that issues leases with the desired parameters depending on the request, and still have a fallback to the normal method when the RADIUS server is down, being rebooted, etc.