Thanks for your answer. I should have been more specific with what I mean by the previous version. My previous version was Freeradius 3.0.16 (Ubuntu 18.04). So what I just did was to copy both queries.conf and schema.sql from 3.0.16 and copied them in the same place on a Freeradius 3.0.19 (Ubuntu 19.04). I have restarted Freeradius and I can connect now. Is this approach ok? Thanks, On Thu, 19 Dec 2019 at 14:43, Alan DeKok <aland@deployingradius.com> wrote:
On Dec 19, 2019, at 9:26 AM, Houman <houmie@gmail.com> wrote:
Ah I understand now.
So I have to replace /etc/freeradius/3.0/mods-config/sql/main/mysql/schema.sql
You don't need to change the schema. It's just an example.
and /etc/freeradius/3.0/mods-config/sql/main/mysql/queries.conf with the previous version.
You can't "replace" the file. You need to edit the queries to match your schema.
The v2 sql.conf file and queries *cannot* be copied to a v3 configuration. They *will not* work.
I couldn't see anything else in the config itself that has to be changed.
Yes. That's why we hide the SQL complexity in "queries.conf" file. So nothing else needs to change when you change the queries.
Did I understand that correctly?
Pretty much.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html