Load Balance FreeRadius
Hi, Actually I have a free radius on a centos connected to a mariadb database to give Access to hotspot users. I'm planning to move the freeradius to AWS and I would like to build 2 freeradius instances and 1 database instance. The idea is that when a paket is sent the balancer sends to one freeradius and the freeradius query or update the database and send response. The when a next packet is sent the balancer sends to the second freeradius and that query or update the database and send response.. So both freeradius instances uses the same database .. Maybe it does not have sense because probably the freeradius is not the slow part so build 2 instances to handle the traffic won't work . the database should be the slower part here. Is it possible Theatrically ? Does it has sense to do this schema ? What about freeradius on AWS ? Thanks a lot.
On Nov 21, 2018, at 9:49 AM, <oscar@jofre.com> <oscar@jofre.com> wrote:
I'm planning to move the freeradius to AWS and I would like to build 2 freeradius instances and 1 database instance.
The idea is that when a paket is sent the balancer sends to one freeradius and the freeradius query or update the database and send response.
Which load balancer are you using? If it's AWS, it doesn't support UDP. And even if it did, the load balancer isn't RADIUS aware. So it won't do the RADIUS protocol translations necessary for RADIUS load balancing.
So both freeradius instances uses the same database ..
Then that's the single point of failure. And to be honest, FreeRADIUS can handle many tens of thousands of packets per second. An SQL database is much more limited.
Maybe it does not have sense because probably the freeradius is not the slow part so build 2 instances to handle the traffic won't work . the database should be the slower part here.
Exactly. So you don't need 2 RADIUS servers. One will do fine. Alan DeKok.
Hi, I'm using keepalived in direct routing mode and works perfectly. --Marius Matei
On 21 Nov 2018, at 17:05, Alan DeKok <aland@deployingradius.com> wrote:
On Nov 21, 2018, at 9:49 AM, <oscar@jofre.com> <oscar@jofre.com> wrote: I'm planning to move the freeradius to AWS and I would like to build 2 freeradius instances and 1 database instance.
The idea is that when a paket is sent the balancer sends to one freeradius and the freeradius query or update the database and send response.
Which load balancer are you using? If it's AWS, it doesn't support UDP. And even if it did, the load balancer isn't RADIUS aware. So it won't do the RADIUS protocol translations necessary for RADIUS load balancing.
So both freeradius instances uses the same database ..
Then that's the single point of failure.
And to be honest, FreeRADIUS can handle many tens of thousands of packets per second. An SQL database is much more limited.
Maybe it does not have sense because probably the freeradius is not the slow part so build 2 instances to handle the traffic won't work . the database should be the slower part here.
Exactly. So you don't need 2 RADIUS servers. One will do fine.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
matei marius -
oscar＠jofre.com