IPv6 accounting RADIUS SQL schema?

Nathan Ward lists+freeradius at daork.net
Sun Aug 19 07:49:21 CEST 2018


> On 19/08/2018, at 5:21 PM, Michael Ducharme <mducharme at gmail.com> wrote:
> However, I don't think it is necessarily a technical problem to have three different fields to store the IPv6 address and searching across three fields. The biggest risk is going to be lack of understanding of what the fields are for, where developers who create billing systems or web interfaces that offer some kind of address search function may only program it to search one of the three fields, not understanding the purpose of the different fields. I expect that a developer extending their billing system or web interface to IPv6, not having an understanding of some of the technicalities, would think that search of a "framedipv6address" field was sufficient and not bother to search the "framedipv6prefix" and "delegatedipv6prefix" fields, and that would end up creating issues for end users.

If this would be the approach then I think it’s best left as examples of what could be done, rather than change the standard schema - a standard schema needs to support 0+ of each of the fields you suggest here, not simply 0-1.

Nathan Ward

More information about the Freeradius-Users mailing list