No one uses this much, but it could be better documented and used. I had a thought which might help... Right now there's a "dynamic_clients" module. It reads the dynamic clients from a file. The "lifetime" parameter determines when the client should be reloaded. It would be useful to automatically extend the lifetime if the origin file still existed, and was unchanged. i.e. 1) create dynamic client with lifetime = 300 (so you can change it periodically) 2) 300s later, the server notices that the file exists, and hasn't changed 3) the server extends the client for another lifetime. Thoughts?
That sounds very logical to me and should avoid a lot of unnecessary reloads. Are you thinking a simple modification time check or some sort of file hash? — Aaron
On May 11, 2015, at 10:34 AM, Alan DeKok <aland@deployingradius.com> wrote:
No one uses this much, but it could be better documented and used. I had a thought which might help...
Right now there's a "dynamic_clients" module. It reads the dynamic clients from a file. The "lifetime" parameter determines when the client should be reloaded.
It would be useful to automatically extend the lifetime if the origin file still existed, and was unchanged.
i.e.
1) create dynamic client with lifetime = 300 (so you can change it periodically)
2) 300s later, the server notices that the file exists, and hasn't changed
3) the server extends the client for another lifetime.
Thoughts? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
On May 11, 2015, at 2:26 PM, Aaron Hurt via Freeradius-Devel <freeradius-devel@lists.freeradius.org> wrote:
That sounds very logical to me and should avoid a lot of unnecessary reloads. Are you thinking a simple modification time check or some sort of file hash?
A modification time check should be sufficient. I've pushed a fix which does that. Alan DeKok.
On May 11, 2015, at 11:34 AM, Alan DeKok <aland@deployingradius.com> wrote:
No one uses this much, but it could be better documented and used. I had a thought which might help...
Right now there's a "dynamic_clients" module. It reads the dynamic clients from a file. The "lifetime" parameter determines when the client should be reloaded.
It would be useful to automatically extend the lifetime if the origin file still existed, and was unchanged.
i.e.
1) create dynamic client with lifetime = 300 (so you can change it periodically)
2) 300s later, the server notices that the file exists, and hasn't changed
3) the server extends the client for another lifetime.
Thoughts?
Use sqlite or rlm_csv. The dynamic clients module should be removed. -Arran
We use it in a large corporate environment for a long time and look the clients up in a sql database. It just works for us. Norbert -----Original Message----- From: Freeradius-Devel [mailto:freeradius-devel-bounces+norbert.wegener=atos.net@lists.freeradius.org] On Behalf Of A.L.M.Buxey@lboro.ac.uk Sent: Tuesday, May 12, 2015 12:06 AM To: FreeRadius developers mailing list Subject: Re: Dynamic clients Hi,
No one uses this much, but it could be better documented and used. I had a thought which might help...
how do you know that noone uses it much? if it doesnt have bugs then noone reports...and the server does talk back to networkradius to report the modules in use.. ;-) alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Aaron Hurt -
Alan DeKok -
Arran Cudbard-Bell -
Wegener, Norbert