When we first developed OpenWISP RADIUS we tried making the first database migration use the same schema used by freeradius at that time and then perform any change in subsequent DB migrations, so that it should be easier to migrate an existing freeradius DB to OpenWISP RADIUS.
However, since then, I believe freeradius kept changing the schema a bit and I am not sure we can do much about it. The schema changes seem to be minimal and do not affect us because we are mostly using the freeradius rml_rest module as a backend for most operations and by default we do not rely on the sql module (which can be enabled if needed, but you may have to tweak the queries.conf file). If I was you and I wanted to use the features offered by OpenWISP RADIUS, I would do it differently: - I'd start with the OpenWISP RADIUS schema and configure freeradius as we recommend, I'd start on a single server - I'd verify all the features work as expected - I'd move the freeradius server away from the single server, they don't need to be on the same server, I believe you can have multiple freeradius instances as well if you need. I hope this helps. Best regards *Federico Capoano* OpenWISP OÜ Kotkapoja tn 2a-10, 10615, Harju maakond, Tallinn, Estonia VAT: EE101989729 +372 59361689 *openwisp.io* <http://openwisp.io> On Mon, 25 Aug 2025 at 10:03, 'Asad Vathare' via OpenWISP < [email protected]> wrote: > Hey, > My company is trying to use openwisp as the main service to manage our > devices, and we are trying to integrate external freeradius server to > openwisp, so we can use openwisp as single interface to manage our devices. > So, we went with connecting external freeradius instead of openwisp_radius > due to scalability and availability issues we want to prepare for. > > We have tried couple of things on our own. like > > 1. Connecting same database to openwisp and freeradius. > 2. Creating database with freeradius schema first and then ran migrate > command to create tables for other modules except openwisp_radius (which we > --fake 'd), then manually created remaining columns and tables in mysql > 3. Using openwisp server as freeradius proxy > > we tried all this, and we are facing schema mismatch issues where > freeradius is using different schema than openwisp, and it seems that they > aren't compatible. But the documentation suggested that there is a way to > connect external freeradius server to openwisp, and we want some help > setting it up. > Any documentation is appreciated, Thank you. > > Attaching screenshot of "Note" from official openwisp documentation > https://openwisp.io/docs/stable/ansible/user/enabling-modules.html > > [image: image] > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion, visit > https://groups.google.com/d/msgid/openwisp/9d8a2de1-9caf-4034-abb8-9bf1c9cc7fc3n%40googlegroups.com > <https://groups.google.com/d/msgid/openwisp/9d8a2de1-9caf-4034-abb8-9bf1c9cc7fc3n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6%2BzmNvsaXVE8mC4QmJou1agx3xgFJV4P756wfaMG9Eg9Q%40mail.gmail.com.
