Hello,
we use RADIUS features for wireless client authentication: station MACs are checked by RouterOS AP against a (single) configured RADIUS server, and everything works fine.
/radius add address=radius_server_ip1 secret=oursecret service=wireless
However, the RADIUS server is a single point of failure of our system. We have set up a redundant (additional, backup, secondary, … - call it as you like) RADIUS server and need to use it in APs.
When I simply add the server, hoping for some round-robin failover behavior, like:
/radius add address=radius_server_ip1 secret=oursecret service=wireless
/radius add address=radius_server_ip2 secret=oursecret service=wireless
in case, that the first server is unavailable, the clients are not authenticated until the first RADIUS server is disabled, i.e. the operational RADIUS server becomes the first one in the server list.
I have found several discussions about this problem (see http://forum.mikrotik.com/t/secondary-radius-server/30238/1), but I don’t want to use such “ugly” scripts, because of poor maintenance and functionality: pinging the server does not mean that the RADIUS service is operational.
Q: Am the only one who wants to have a redundant RADIUS servers? Does anyone got it working somehow? Or is it just a RouterOS bug?
Thank you for any info.