Filtering accounting messages

liran kessel lirankessel at
Mon Jul 15 10:43:16 CEST 2019


I am working with Postgres so will use it in the if statement to query for my users before executing the sql as you suggested, though this still means I am quering sql for every event.
Would using the rlm_cache to store the users be useful in this instance in terms of reducing the sql queries and improving performance?


> On 15 Jul 2019, at 10:11, Alan DeKok <aland at> wrote:
> On Jul 14, 2019, at 10:07 PM, liran kessel <lirankessel at> wrote:
>> I understand what you proposed but this (my users) is a dynamic list that will grow constantly so the question is what would be the best way to keep it updated within the configuration?
> This is what databases are for.
> FreeRADIUS is a RADIUS server.  We don't implement internal databases.  We just use normal databases.
>> As I said in the original mail , we are growing to over 150k unique calling-station-ids that around 80% should be recorded to the DB while 20% shouldn’t. 
>> Maybe storing the list in a file that I can reference in the suggested “if” statement?  
>> Or maybe there is way to cache the list in memory to speed it up even more? 
> Use Redis.  We've tested it at 10K+ complex queries per second with FreeRADIUS.  That should be more than sufficient for your needs.
> Alan DeKok.
> -
> List info/subscribe/unsubscribe? See

More information about the Freeradius-Users mailing list