Hi Alan, Yes indeed. RADIUS Authentication and Accounting servers are two different physical machines, which are connected to each other. Then, I have 2 instances of the SQL configuration, one that writes to a local database and another that writes to a remote database. The reason for this setup is that the remote database is handled by a different team and this cannot be eliminated. Now the issue is that when the remote database is for any reason unreachable (could be firewall, maintenance, etc..) RADIUS will no longer authenticate users. So what I'd like to establish is if there's a way for RADIUS to continue with the authentication process of users without having them accounted for, when the remote database is unavailable. Hope this helps, if a diagram will be more helpful please let me know and I will provide you with one. Thanks again, SG On Mon, Dec 19, 2022 at 2:44 PM Alan DeKok <aland@deployingradius.com> wrote:
On Dec 19, 2022, at 6:48 AM, Sea Gull <seagull0044@gmail.com> wrote:
Thanks again for your time. I understand your comments, and you are right. However, in my setup the RADIUS Authentication server, and the RADIUS Accounting server are two different physical servers, and as you might well know network disruptions can happen. Also, it is impossible for us to have users unable to authenticate, because the accounting server is down as this will stop thousands of users from working.
Is there a way we can have RADIUS Authentication working when the accounting servers are down or unreachable, please?
So... the servers are physically different, but if one stops working, the other one stops working, too?
Either the servers are magic, or you're not describing what's actually going on.
If you can't describe what the current system is doing or how it works, then you can't configure it to do what you want.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html