Operators have not been implemented yet. If you wish to make a patch, perhaps this would benfit everyone. All that needs to be done is add a operator column, and have it use these operators on an authorize call.
On Thu, 2001-11-29 at 11:04, [EMAIL PROTECTED] wrote: > This is related to a previous post I made. > > How do I send a different set of reply attributes depending on > an request attribute using sql?. > > Using the users file I have done it by: > > ---------------------- > user Password==\"something\", Attribute=~\"something1\" > reply-attributes1=value1 > > user Password==\"something\", Attribute=~\"something2\" > reply-attribute2=value2 > ---------------------- > > But how do I accomplish the same thing using rlm_sql?. > > I have thought about creating a radreply1 table and a radreply2 > table. But then I will have to make a patch for myself only to > support filtering of the \"Attribute\" and deciding which > radcheck table to use. > > I believe somebody must have had this situation before. And I > know it can be a configuration level solution for this, it is > just not documented at all. If so, please, please helP!!!! > > Thanks, > > Jose\' L. > > > ------------------------------------------------------------------------ > Mail enviado desde PortalMail 1.4.2 Web based email system. > PaloSanto Solutions, Sunnyvale CA. > http://www.palosanto.com > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Mike Machado [EMAIL PROTECTED] InnerCite Inc. Engineering Director / CTO - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
