Re: dynamically selecting, which attribute to evaluate
Stefan A. wrote: and then to evaluate TicetType specific Attributes... if (reply:%{control:TicketType}-trigger-reactivation != ){ You can't really do two levels of expansion like that, sorry. Why does it not expand the %{control:TicketType} to Ticket245 in this situation? You can't really do two levels of expansion like that, sorry. How may I dynamically select Attributes to check for? Perl. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: dynamically selecting, which attribute to evaluate
:-( but thanks, Alan, Unfortunately, I've never have been able to build FR with perl on my x86 Solaris 10 boxes... but we well keep trying ;-) For the meantime, would it be feasable to update control { temp_attribute := reply:%{control:TicketType}-trigger-reactivation } and later if (%{control:temp_attribute} != ){ do the rest } Regards Stefan -Original Message- From: freeradius-users- bounces+a.freeradius=premit...@lists.freeradius.org [mailto:freeradius- users-bounces+a.freeradius=premit...@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Wednesday, December 01, 2010 2:18 PM To: FreeRadius users mailing list Subject: Re: dynamically selecting, which attribute to evaluate Stefan A. wrote: and then to evaluate TicetType specific Attributes... if (reply:%{control:TicketType}-trigger-reactivation != ){ You can't really do two levels of expansion like that, sorry. Why does it not expand the %{control:TicketType} to Ticket245 in this situation? You can't really do two levels of expansion like that, sorry. How may I dynamically select Attributes to check for? Perl. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: dynamically selecting, which attribute to evaluate
Stefan A. wrote: :-( but thanks, Alan, Unfortunately, I've never have been able to build FR with perl on my x86 Solaris 10 boxes... but we well keep trying ;-) It should be possible. For the meantime, would it be feasable to update control { temp_attribute := reply:%{control:TicketType}-trigger-reactivation } and later if (%{control:temp_attribute} != ){ do the rest } sigh I said: You can't really do two levels of expansion like that, sorry. Why does it not expand the %{control:TicketType} to Ticket245 in this situation? You can't really do two levels of expansion like that, sorry. I suggest reading the messages on this list. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: dynamically selecting, which attribute to evaluate
On 2010/12/01 07:46 PM, Alan DeKok wrote: For the meantime, would it be feasable to update control { temp_attribute := reply:%{control:TicketType}-trigger-reactivation } and later if (%{control:temp_attribute} != ){ do the rest } sigh I said: You can't really do two levels of expansion like that, sorry. Using rlm_perl, you should be able to get the functionality you want. -- Johan Meiring Cape PC Services CC Tel: (021) 883-8271 Fax: (021) 886-7782 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html