IPv6 accounting RADIUS SQL schema?

[Alan DeKok]

On Aug 16, 2018, at 2:16 PM, Michael Ducharme <mducharme at gmail.com> wrote:
> 
> I am wondering whether there is any standard SQL schema for IPv6 radius accounting, and standard queries?

  The schemas are pretty much already IPv6 compliant.

- Postgresql has the "framedipaddress" field as INET, which is IPv4 or IPv6

- MySQL has it "varchar", which is anything...

- as does Oracle and sqlite

  The only thing that needs doing is to update the queries to use:

	%{%{Framed-IP-Address}:-%{Framed-IPv6-Address}} instead of just %{Framed-IP-Address}

> I understand from doing a bit of research that to store the IPv6 schema we have to manually add fields to the SQL database and the queries to the queries.conf. That is certainly doable and is easy enough, however instead of naming them what I want, I would rather have some official guidance as to what the fields should be named and what the queries should be.

  It's all there already.

> The reason is that we use some third party software that reads accounting data directly out out of the FreeRADIUS radacct table, and it expects the standard field names to be used - unfortunately there seem to not be standardized field names for SQL for IPv6 RADIUS accounting yet, and it would simply save us some future headache if we had this. They seem to not want to build support for IPv6 until there is some standard schema released by FreeRADIUS that gives the MySQL field names for IPv6 accounting info.
> 
> Also small ISPs are beginning to roll out IPv6 more and more, ISPs that use FreeRADIUS, so it might be good to add those into the standard install at some point? Just an idea.

  Send a github pull request for the v3.0.x branch.  It should be pretty simple.

  Alan DeKok.