freeradius 3.0.x HOW TO ULANG read/write all list keys/values

Alan DeKok aland at deployingradius.com
Tue Nov 10 15:42:23 CET 2015


On Nov 9, 2015, at 6:18 PM, Michal Tomaszewski <Michal.Tomaszewski at cca.pl> wrote:
> I've already made all radius accounting using redis as well as connection between different sessions' records belonging to the same user roaming between different devices in the same pool of devices.

  That's different.  Writing arbitrary attributes *to* a database is easier than reading them from a database.

> The default cache mechanism is not suitable for me as I need to set different expirations on some records depending on session time parameter and other properties of the user

  So set the expiration time per cache entry.  The module supports that.

> as well as  I need to have full control of data stored in redis. What is more - cache module working with redis has been introduced only in FR 3.1.x

  You don't need redis to cache data.

> Thus I'd like to develop own-controlled redis storage.
> The only I need is the ulang syntax to extract reply parameters stored in string back to the reply list.

  Except that's not possible in 3.0.  That's why I suggested the cache module.

> Could you be so kind to explain how in ulang can I achieve reading data directly to the reply list from string created e.g. using  "%{pairs:reply:[*]}" syntax?

  You can't.

a) use the cache module in 3.0

b) use 3.1

c) write a custom Perl script which uses redis as a back-end to cache attributes

  Pick one.

  Alan DeKok.




More information about the Freeradius-Users mailing list