Mapping between sqlippool and radius attributes
Good evening, after reading the configuration files, the wiki entry as well as trying to dig in the code I haven't been able to figure out how the columns from the sqlippool module are mapped back to radius attributes. The default table scheme creates a column "framedipaddress" which appears to become the "Framed-IP-Address" attribute through magic. Is there a way to extend this with a "Framed-IPv6-Prefix"? Is adding a column with that name sufficient? I've seen it being done using xlat extensions and sql in the post-auth section but this seems to be a horrible approach and I'd love to avoid that. Best regards Thore
On Apr 13, 2018, at 8:02 AM, Thore Krüss <thore@scimeda.de> wrote:
after reading the configuration files, the wiki entry as well as trying to dig in the code I haven't been able to figure out how the columns from the sqlippool module are mapped back to radius attributes.
See raddb/mods-config/sql/ippool/ The files there contain all of the queries necessary for IP pool allocation. Also, read raddb/mods-available/sqlippool That file contains documentation about how it works, and it includes the files which do the actual queries.
The default table scheme creates a column "framedipaddress" which appears to become the "Framed-IP-Address" attribute through magic.
As always, run the server in debug mode. Read the output. See what it does. i.e. configure the sqlippool module as per the docs and examples, then send it packets and read the debug output. It should then be clear what's going on and how.
Is there a way to extend this with a "Framed-IPv6-Prefix"? Is adding a column with that name sufficient?
No. Read raddb/mods-available/sqlippool. This is documented. Alan DeKok.
On Fri, Apr 13, 2018 at 09:18:12AM -0400, Alan DeKok wrote:
On Apr 13, 2018, at 8:02 AM, Thore Krüss <thore@scimeda.de> wrote:
after reading the configuration files, the wiki entry as well as trying to dig in the code I haven't been able to figure out how the columns from the sqlippool module are mapped back to radius attributes.
See raddb/mods-config/sql/ippool/
The files there contain all of the queries necessary for IP pool allocation.
Also, read raddb/mods-available/sqlippool
That file contains documentation about how it works, and it includes the files which do the actual queries.
The default table scheme creates a column "framedipaddress" which appears to become the "Framed-IP-Address" attribute through magic.
As always, run the server in debug mode. Read the output. See what it does.
i.e. configure the sqlippool module as per the docs and examples, then send it packets and read the debug output. It should then be clear what's going on and how.
Is there a way to extend this with a "Framed-IPv6-Prefix"? Is adding a column with that name sufficient?
No. Read raddb/mods-available/sqlippool. This is documented.
Thank you for your quick reply, looking at this: https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/mods-avail... made it a whole lot clearer than the config provided with debian (stretch). Thank you for the hint in that direction. Best regards Thore
On Apr 13, 2018, at 12:05 PM, Thore Krüss <thore@scimeda.de> wrote:
Thank you for your quick reply, looking at this: https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/mods-avail... made it a whole lot clearer than the config provided with debian (stretch).
That's why *we* ship the server with all available modules. It's beyond me why some distributions butcher the configuration to make it unusable. Alan DeKok.
participants (2)
-
Alan DeKok -
Thore Krüss