Michael Plourde wrote:
I want to use multiple database to sort different kind of radius authentification (dialup, wireless, router login, etc). I don't know if i'm using it the right way, but I have try to run freeradius with two virtual server using two different sql instance. Those sql instance are configured the same way except for the database: one use "radius_db = radius_dialup" and the other one "radius_db = radius_login".
You don't have to do that. You can use one SQL instance, and change the radius_db on the fly. But for now, it's likely good enough.
If I load only one of those virtual server at radiusd startup (I remove sites-enabled links for one of those server), everything works fine. If I try them together, I got this error:
Adding client 172.16.0.2 (gw-calma.digicom.ca, server=MT-Login-User) to clients list Failed to add duplicate client gw-calma.digicom.ca rlm_sql (sql_MT): Failed to add client 172.16.0.2 (gw-calma.digicom.ca) to clients list. Maybe there's a duplicate? Failed to load clients from SQL. ... Doesn't each virtual server had his own clients list ? Why duplicate entry ? How can I force freeradius to use one client list per virtual server taken from SQL table ?
See the sample SQL queries && schema. 2.1.1 allows you to define a "server" column. That entry is used to associate one client with a particular server. Alan DeKok.