The current SQL client format uses a column based layout to describe client attributes. It currently supports: * identifier (IP, FQDN, prefix) * secret * shortname * nastype * server (optional). The current static client parser supports: * identifier (IP, FQDN, prefix) * secret * shortname * nastype * server (optional). * src ip address (override) * login * password * protocol * limit - max_connections * limit - lifetime * limit - idle_timeout * coa_server Many of those different attributes are optional and are not needed, so extending the schema to add the extra columns seems wasteful. Does anyone see issues with allowing an alternative schema (whilst supporting the old one), where the primary key was the client identifier, and then just had attribute and value columns? It would also support arbitrary client attributes like the current static client definitions do. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team