multiple-login checking
Alan DeKok
aland at deployingradius.com
Wed Apr 16 15:04:20 UTC 2025
On Apr 16, 2025, at 8:53 AM, Can Paçacı <pacaci at servisnet.com.tr> wrote:
> Which method is better performance to limit for concurrent logins per user, Simultaneous-Use checking or checkrad?
They are related. Sertting the Simultaneous-Use attribute also makes the server run the checkrad program.
> Since simultaneus-use check performs "select count(*) .." for each session in query.conf, it causes performance loss in db.
It shouldn't cause a performance problem. The default schema creates an index on the user name and stop time. Which means that counting sessions for a user shouldn't be expensive.
That being said, if the server is receiving have 10K packets per second, that will cause performance issues by itself.
> Which method is suitable for the least performance loss?
The answer here is "database optimization". If the database is slow, make it faster. You can't control how many packets are received by FreeRADIUS. So the best approach is fixing the database.
> Also, the NAS we use (Huawei-BNG) is not included in the NAS types list on the checkrad man-page.
We're happy to accept patches.
Alan DeKok.
More information about the Freeradius-Users
mailing list