Perfect - thank you. Looks like I need to start rebuilding this evening then! David On 28/09/2026, 15:55, "Alan DeKok" <alan.dekok@inkbridge.io> wrote: On Sep 28, 2026, at 10:50 AM, David Lake <d.lake@surrey.ac.uk<mailto:d.lake@surrey.ac.uk>> wrote:
Thanks. We are also stuck with an SQL-based DB at the moment because this links to a CRM system which links to a billing system which links to…. Etc.
Life is complicated. :(
WAN bandwidth between the two sites is not an issue (dark fibre) so the answer for now is probably to have the RADIUS servers as main and backup and then have everything in one place. The highest number will ever get to that need IP allocation all-at-once is about 8,000 clients (that is in the event of site failure all clients rehoming to the second site) so we’re not going to be hitting any limited in terms of system performance.
Having both RADIUS servers talk to one SQL cluster is fine, so long as the connectivity is _very_ reliable.
Looks like I need to build HAProxy or ProxySQL to hide the multi-master and then direct both my NASes through one RADIUS server for now.
(Any preferences for HAProxy vs ProxySQL?)
I've had good luck with HAproxy. I haven't looked at ProxySQL. Alan DeKok.