If you configure each of these routers 10.1.1.254, 10.2.1.254 etc with some “helper” address (on the customer-facing side) to relay the broadcast-request they see coming in the client-side and deliver it in unicast to your DHCP you’ll have no issue to map it to a correct pool I guess.
So you are handing out 10.x.y.z IP’s right ?? Then you have some centralized NAT taking place to public IP ?
The radius server simply authenticates it doesn’t know or care if the IPs being used are public or private.
If you are going to dish out private IP’s then you will have a source nat or masquerade from that range to the WAN IP.
The ip pool for the hand out can be in a mikrotik pool or in the radius server there are two ways to do it.
You can also optionally have the mikrotik pool do the common ones and some fixed static ones be done by the radius.
If the radius is setting the IP it will send a FRAMED-IP field in the radius response.
So there is flexibility in the ip handout scheme.
The radius can also optionally set client queues for speed limit per user it does that via some special response fields.
Alternatively you can control customer speeds by other mechanism like tree queues etc.
Your start point is setup a radius server and connect it to mikrotik. You can generally organize a vlan on the system to play
without affecting the current running system.
Would something like this work, such that the client routers could obtain an IP address from the Radius server?
radius (nas server) only handles AAA (users and password, mac addresses etc - as defined in attributes) requested by routers (nas clients) . it needs to work with dhcp server for ip address allocation.
mikrotik wiki has a detailed guide for radius. you might want to read.