On 12/5/09 14:01, Toledo, Luis Carlos wrote:
On Mon, 11 May 2009 15:01:22 +0200, Alan DeKok <aland@deployingradius.com> wrote:
Toledo, Luis Carlos wrote:
I have a single freeradius server with 1.1.7, its stable, but I would like to upgrade it to 2.1.4 version.
Is it a sacrilege or mistake to use radius.conf and sites-available/default files to configure my single aaa server? What does that mean?
Could be asking whether it's wrong to use the sites-available include folder, instead of bundling it all into radiusd.conf when you have a single sever ?
I would like to say: Is it correct to use sites-available/default config file to put my configures? Or is it more correct to create a new config file?
It's up to you. I'd recommend you keep the default file for reference, but there's a copy included with the src so it'd fine to go ahead and edit it. In general, policy configuration goes in the sites-available file, then module instance configuration is done in the various raddb/*.conf files and raddb/modules/*.conf. -- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk), Authentication, Authorisation and Accounting Officer, Infrastructure Services (IT Services), E1-1-08, Engineering 1, University Of Sussex, Brighton, BN1 9QT DDI+FAX: +44 1273 873900 | INT: 3900 GPG: 86FF A285 1AA1 EE40 D228 7C2E 71A9 25BB 1E68 54A2