Cannot control attribute ordering via rlm_perl

[Heiko Rehm]

Hello Alan,

>   You can work around it by returning policy names in Perl.  Then in FreeRADIUS, check for those policy names, and add the correct attributes.

Interesting. Would you have a config example how to build this?
Or a hint to a manual where those Policies are described?

Thanks,
Heiko
------------------------------------------------------------------------
*PYRAMITE* 	*Heiko Rehm ///
PYRAMITE-IT/*
Email: hrehm at pyra-mite.net 	Location: https://goo.gl/maps/vcxUbJJUaEq
Jabber: heiko at chat.pyra-mite.net 	Mobile Kenya: (+254) 708 725 844
Web: http://www.pyra-mite.net 	Mobile Germany: (+49) 7344 175333
Skype: heikorehm 	Mobile Belgium: (+32) 495 26 44 26
PGP-Public: goo.gl/h9fgZZ <https://goo.gl/h9fgZZ> 	Facebook:
goo.gl/J8dyJA <https://goo.gl/J8dyJA>


On 6/30/2018 1:33 PM, Alan DeKok wrote:
>> On Jun 30, 2018, at 6:10 AM, Heiko Rehm <hrehm at pyra-mite.net> wrote:
>>
>> Hello List,
>>
>> I am falling in the same trap as below quoted a few years back.
>> When using WiMAX, the reply attribute ordering is important.
>> Using rlm_perl which is used with "Splynx" (www.splynx.com) messes up the order in the response and I can't seem to find a way around this.
>>
>> Alan mentioned in a old post "suggestions welcome".
>> Wondering if there was a solution in the meantime or if anyone has a idea how to solve this (with perl)?
>   There isn't a good solution, unfortunately.  Perl hashes the name and uses that for ordering.  FreeRADIUS assumes that the attributes are an ordered list, independent of name.
>
>   You can work around it by returning policy names in Perl.  Then in FreeRADIUS, check for those policy names, and add the correct attributes.
>
>   Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html