SV: Max length of SQl return string?

Alexander Silveröhrt Alexander.Silverohrt at
Fri Nov 29 03:46:49 CET 2013

Thx for the update on this.

I guess the only way is to make a workaround like checking if the string is >250 chars and if it is then instatiate a DBI call from the perl hook instead that retrieves all the accounts. Hopefully that will no be that many cases.
Its just that i wanted to move away from the DBI inside the hooks bc it takes far to long for the script to execute no matter caching variables across threads or not as Alan recommended a while back.

Thank you again for the answers.

best regards
Från: at [ at] för Arran Cudbard-Bell [a.cudbardb at]
Skickat: den 28 november 2013 16:24
Till: FreeRadius users mailing list
Ämne: Re: Max length of SQl return string?

On 28 Nov 2013, at 14:54, Phil Mayers <p.mayers at> wrote:

> On 28/11/13 14:41, Alexander Silveröhrt wrote:
>> Hello,
>> We are doing a query which are supposed to comeback with a bunch of
>> subscriber accounts.
>>  update request {
>>                 Subscriber-Accounts := "%{sql-cisco-bng:SELECT
>> GROUP_CONCAT(username SEPARATOR ';') FROM radcheck WHERE username LIKE
>> '%{User-Name}%%'}"
>>  }
>> But it seems that there is a limit on how long the return string can be?
> Well, it's a radius attribute, so it's probably 253 bytes.
> Not sure if this limit is changed/removed in later versions of the server (e.g. for attributes which are internal, since they never go on the wire there's no protocol reason to limit their length)

It's... better. But there are many places static buffers are still used. The VP themselves now have a char pointer in the union, which points to a chunk of talloced memory in the VP context.

However, the xlat functions still need to be updated to do dynamic allocation, the limit is probably around 1000bytes. break on rlm_sql.c:144, p freespace and see :)

Arran Cudbard-Bell <a.cudbardb at>
FreeRADIUS Development Team

List info/subscribe/unsubscribe? See

********* DISCLAIMER *********

This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person

More information about the Freeradius-Users mailing list