Mapping from ldap attributes to radius attributes is fine using the
ldap.attrmap file, such as
replyItem Framed-Protocol protocol
In addition, using the ldap entries to store a reply line is also fine
using:
replyItem $GENERIC$ dialAttr
but what if the dialAttr ldap attribute consists of more than one set of
values... using the radiator radius server, we simply iterate over the
returned ldap entries and add them to the reply packet. i'm not sure how to
handle this here... the above only add the first value to the reply packety
tariq
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
