SQL Schema and usage
1 - Search the radcheck table for any check
attributes specific to the user
2 - If check attributes are found, and there's a match, pull the reply items from the radreply table for this user and add them to the reply
3 - Group processing then begins if any of the following conditions are met:
The user IS NOT found in radcheck
The user IS found in radcheck, but the check items don't match
The user IS found in radcheck, the check items DO match AND Fall-Through is set in the radreply table
The user IS found in radcheck, the check items DO match AND the read_groups directive is set to 'yes'
4 - If groups are to be processed for this user, the first thing that is done is the list of groups this user is a member of is pulled from the usergroup table ordered by the priority field. The priority field of the usergroup table allows us to control the order in which groups are processed, so that we can emulate the ordering in the users file. This can be important in many cases.
5 - For each group this user is a member of, the corresponding check items are pulled from radgroupcheck table and compared with the request. If there is a match, the reply items for this group are pulled from the radgroupreply table and applied.
6 - Processing continues to the next group IF:
There was not a match for the last group's check items OR
Fall-Through was set in the last group's reply items (The above is exactly the same as in the users file)
7 - Finally, if the user has a User-Profile attribute set or the Default Profile option is set in the sql.conf, then steps 4-6 are repeated for the groups that the profile is a member of.
2 - If check attributes are found, and there's a match, pull the reply items from the radreply table for this user and add them to the reply
3 - Group processing then begins if any of the following conditions are met:
The user IS NOT found in radcheck
The user IS found in radcheck, but the check items don't match
The user IS found in radcheck, the check items DO match AND Fall-Through is set in the radreply table
The user IS found in radcheck, the check items DO match AND the read_groups directive is set to 'yes'
4 - If groups are to be processed for this user, the first thing that is done is the list of groups this user is a member of is pulled from the usergroup table ordered by the priority field. The priority field of the usergroup table allows us to control the order in which groups are processed, so that we can emulate the ordering in the users file. This can be important in many cases.
5 - For each group this user is a member of, the corresponding check items are pulled from radgroupcheck table and compared with the request. If there is a match, the reply items for this group are pulled from the radgroupreply table and applied.
6 - Processing continues to the next group IF:
There was not a match for the last group's check items OR
Fall-Through was set in the last group's reply items (The above is exactly the same as in the users file)
7 - Finally, if the user has a User-Profile attribute set or the Default Profile option is set in the sql.conf, then steps 4-6 are repeated for the groups that the profile is a member of.
radcheck table and radreply table are in freeradius
or sql server ??? check (poin 1) is to sql server and reply (point 2) from sql
server ?
..so I got that error after point 2 right ?
hmmmm..
radius_xlat: '[EMAIL PROTECTED]'
rlm_sql (sql): sql_set_user escaped user --> '[EMAIL PROTECTED]'
radius_xlat: 'VoIP_Radius '[EMAIL PROTECTED]''
rlm_sql (sql): Reserving sql socket id: 16
radius_xlat: ''
radius_xlat: 'VoIP_Radius '[EMAIL PROTECTED]','', '','192.168.1.1','''
rlm_sql: Failed to create the pair: Unknown value VOIP for attribute Service-Type
rlm_sql (sql): Error getting data from database
radius_xlat: ''
rlm_sql (sql): sql_set_user escaped user --> '[EMAIL PROTECTED]'
radius_xlat: 'VoIP_Radius '[EMAIL PROTECTED]''
rlm_sql (sql): Reserving sql socket id: 16
radius_xlat: ''
radius_xlat: 'VoIP_Radius '[EMAIL PROTECTED]','', '','192.168.1.1','''
rlm_sql: Failed to create the pair: Unknown value VOIP for attribute Service-Type
rlm_sql (sql): Error getting data from database
radius_xlat: ''
in mssql.conf file i have
mssql.conf:
authorize_check_query = "VoIP_Radius
'%{User-Name}'"
authorize_reply_query = "VoIP_Radius '%{User-Name}','%{Calling-Station-Id}', \
'%{Called-Station-Id}','%{NAS-IP-Address}','%{h323-conf-id}','VOIP'"
authorize_reply_query = "VoIP_Radius '%{User-Name}','%{Calling-Station-Id}', \
'%{Called-Station-Id}','%{NAS-IP-Address}','%{h323-conf-id}','VOIP'"
can anyone help me to focuse on the
problem?
----- Original Message -----
From: "Giuseppe Parlato" <[EMAIL PROTECTED]>
To: "FreeRadius users mailing list" <[email protected]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, May 28, 2006 6:39 PM
Subject: Re: failed to create the pair
> default queries? can you give me an example or a specific guide for that? I
> haven't found much http://wiki.freeradius.org/index.php/Rlm_sql
>
>
>
> ----- Original Message -----
> From: "Alan DeKok" <>
> To: "FreeRadius users mailing list" <[email protected]>
> Sent: Sunday, May 28, 2006 4:36 PM
> Subject: Re: failed to create the pair
>
>
>> "Giuseppe Parlato" <[EMAIL PROTECTED]> wrote:
>>> in mssql.conf file i have
>>>
>>> authorize_check_query =3D "VoIP_Radius '%{User-Name}'"
>>> authorize_reply_query =3D "VoIP_Radius =
>>> '%{User-Name}','%{Calling-Station-Id}', \
>>> =
>>> '%{Called-Station-Id}','%{NAS-IP-Address}','%{h323-conf-id}','VOIP'"
>>
>> The VOIP text is breaking things. Use the default queries until you
>> understand what they do, and how they work.
>>
>>> I don't know sql server really much and I'm starting learning
>>> freeradius, so can some one explain me how "authorize_check_query" and
>>> "authorize_reply_query" dialogue with ms sql server?
>>
>> The documentation explains what the queries do.
>>
>> Alan DeKok.
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>>
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.1.394 / Virus Database: 268.7.2/349 - Release Date: 26/05/2006
>>
>>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.7.2/349 - Release Date: 26/05/2006
>
>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
