On Mon, 2 May 2005, Sarkis Gabriel wrote: > Hello All, > > At the moment i am running a local radius server on one of my pops, and > the business is expanding steadily and we are going to have multiple pops. > > All pops are linked to a Satellite Dish with a 550ms Delay to the provider, > I am looking for the best way to centralise the Main Radius Server. > > Ideas i have played about with. > > - Archive radius database once in the evening and upload it to the pops Via > cron and process it at the other end, means running multiple radius servers. > > - Put a central Server at the provider and get all radius request going there. > problem clog of BW at a point will request timeout the authentication. > > So what do you guys out there think.. > > Thanks > > Sarky >
You could use ldap or mysql as the backend and setup a master server at one location with all your user accounts. This doesn't even need to run radius, just a mysql db or ldap directory that contains all users. Then setup slave mysql or ldap servers at each remote location. Have the radius servers at the remote locations authenticate to the local database/directory. Your accounts will be in sync up to the delay for the replication to take place. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
