SQL module - merging radcheck/radreply
aland at deployingradius.com
Wed Dec 20 17:02:55 CET 2017
On Dec 20, 2017, at 9:48 AM, Maxime Gerges <maxime.gerges at ariane.network> wrote:
> I have some quick questions regarding the freeradius SQL module and the different implemented tables.
> As far as I know these are the tables defined in the default SQL schema for freeradius :
The behaviour of those tables are also defined in the C source to the SQL module.
> - radcheck : attributes in this table are only internal to freeradius and not used in the radius reply (confirm ?)
Why ask? This is documented. See the Wiki.
> - radreply : attributes in this table are used as reply attributes sent to the NAS
> - radgroupcheck : same as radcheck only for groups
> - radgroupreply : same as radreply only for groups
> Would it be possible to merge both tables (radcheck & radreply or radgroupcheck & radgroureply) as the attributes in radcheck would already be considered as internal and not send in the reply according to their VSA number ?
I have no idea what that means.
Go read the documentation to see how the SQL module works. These questions are based on a misunderstanding of what the tables do.
> As far as I know these internal attributes (located in radcheck) are considered control attributes when their VSA number is 1000+, and placed in the corresponding chain after being extracted from the database.
> From your point of you, does it make sense to merge both table ?
No. Read the documentation, and then things should be clearer.
More information about the Freeradius-Users