as a diagnostic note - the debugging output from radiusd -x does show that all the attributes are read from the ldap server and the code itself ( modules/rlm_ldap/rlm_ldap.c ) suggests that all of these should be added to the packet data structure... i'm now trying to find the point between this and rad_send() from lib/radius.c where it doesn't do that.
t -----Original Message----- From: Kostas Kalevras [mailto:[EMAIL PROTECTED] Sent: 02 March 2004 19:16 To: '[EMAIL PROTECTED]' Subject: Re: multiple repliItems from ldap On Tue, 2 Mar 2004, Tariq Rashid wrote: > > 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 Use operators in the ldap values. Something like: dialAttr: value1 dialAttr: += value2 dialAttr: += value3 > > tariq > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
