Jakob Hirsch wrote: > > is there an easy/good way to determine the huntgroup depending on the > the shortname from clients.conf?
They're independent, so the answer is "no, not really". > We have more than 100 clients > configured (with a "ProviderLocationCounter" pattern), so the > information is duplicated in the huntgroups file (multiple times, as the > huntgroup is also determined by Called-Station-Id). So it would really > simplify things to have the shortname available for matching in the > huntgroups file. Use rlm_passwd to map client IP to a provider location, and then put the provider location in the huntgroups. > unrelated side note: As I see, client_find() walks linearly through the > client list. Shouldn't we keep this in a more appropriate data > structure, like a btree or a trie, Yes. The CVS head does this. > and/or save the once found RADCLIENT* > pointer in the REQUEST struct? Most of the information is saved in the REQUEST struct. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
