Alan DeKok wrote:
"Mitchell, Michael J" <[EMAIL PROTECTED]> wrote:
I've already done some work to get this working, its pretty much finished, but I'll try to do finish it off in the next couple of week... But in the meantime I can provide some patches?
Sure, please put them on bugs.freeradius.org
OK, I should get some time over the weekend to make sure its all ship shape, and I'll submit it then.
I think there's also been patches added to provide hooks to check for a client in a database at authentication and accounting time. Not sure if any work should be done here to support that also.
There were patches posted to do that, but they haven't yet been integrated into the server.
Yep, I knew some patches had been submitted, just wasn't sure where they were up to with respect to inclusion in the server. I think its safe to leave these two issues as separate for now.
One thing I'd really like to see added is huntgroups out of LDAP as clients.conf and huntgroups kind of go hand in hand. If anyone has some thoughts of a good way to do this, I'd love to hear some ideas...
You should be able to define huntgroups in LDAP via an LDAP schema, and some kind of LDAP query.
Yeah, the difficulty I'm having is in defining the order in which huntgroups are assigned/matched. In the huntgroups file, huntgroups are matched in the order in which they appear in the file - ie first one that matches is used. I think its a bit harder to "order" the entries in the LDAP directory... Only way I could think of was to have a "priority" attribute, and once all the huntgroup records had been retrieved, order them based on the priority.
I'm wondering if I'm approaching it from the wrong angle though. I'll have another think about it, but in the meantime if anyone has any thoughts, as I said before I'd be more than willing to listen to any ideas...
cheers, Mike
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
