ASCII NUL in NAS-Filter-Rule

[Ruslan Pustovoytov]

Phil, this construction does not send string2.
I assume when freeradius see nul character it stops reading the string.
Also I cannot send different rules for each customers in such manner.

I found one decision for my problem.
If I send additional NAS-Filter-Rule attribute equal to "0x00" after 
each of my own, character nul is successfully sending.



Phil Mayers wrote:
> On 04/15/2011 09:05 AM, Ruslan Pustovoytov wrote:
>> Hi All
>>
>> My nas box can use attribute NAS-Filter-Rule from radius server to
>> construct filter rules per subscriber "on the fly".
>> Accodingly to rfc 4849 this attribute should contain ascii NUL (0x00) as
>> a delimiter between individual filter rules and at the end of rules.
>> Freeradius define this attribute as a string and I do not know how to
>> create valid string with nul character.
>> I changed attribute type to octets and successfully add null character
>> but a whole string converted to hex also and attribute was not readable.
>> How to send nul character without changing attribute type ?
>
> Try this:
>
>  update reply {
>    NAS-Filter-Rule = "string1\000string2"
>  }
>
> -
> List info/subscribe/unsubscribe? See 
> http://www.freeradius.org/list/users.html
>
>