I’m using Radiator for my hotspot, but I would like to store information on Mikrotik local when my radius server having server down time. For example when server down the radius information will store at Mikrotik local, once radius server service restored, it will send the information back to my Radiator/server.
Are you talking about the accounting information? You want RouterOS to keep trying to send the accounting messages to the RADIUS server until it succeeds? I don’t think RouterOS supports that, to my knowledge (though that would be a nice feature; if RouterOS does not get Accounting-Response back from any RADIUS servers, queue up retransmission of the same Accounting-Request at intervals for a configurable amount of time before giving up).
If you mean that you want people to still be able to authenticate to some degree despite your Radiator server being down, depending on what hardware you are running RouterOS on, you may be able to run a local Linux VM (using either KVM on x86 or MetaROUTER on select RouterBoards) with a second copy of Radiator that proxies requests to the main Radiator server using the RADIUS AuthBy mechanism. Then enable the CachePasswords feature within that AuthBy clause. This will cause Radiator to cache some of the responses it proxies in memory, which will allow it to continue to re-authenticate users who were already authenticated before the main Radiator server went down.
(Come to think of it, if you did this, you could also have this local Radiator VM server store accounting information, which solves that problem as well.)
By far the easiest, most straightforward, and most reliable answer to your question, though, is for you to run 2 RADIUS servers, and then add both of them to RouterOS’s RADIUS configuration. Is there a reason why you can’t do that?
– Nathan