Hello Daud -
On Fri, 21 Jan 2000, Daud Yusof wrote:
> Hi All,
> I've found out on how to do the above in the FAQ as shown below
>
> <Realm whatever>
> AuthByPolicy ContinueAlways
> <AuthBy SQL>
> DBSource dbi:???????
> DBUsername userfordb1
> DBAuth authfordb1
> # an empty AuthSelect turns off auth
> AuthSelect
>
> AccountingTable whatever
> etc, etc, etc.
> </AuthBy>
> <AuthBy SQL>
> DBSource dbi:???????
> DBUsername userfordb2
> DBAuth authfordb2
> # an empty AccountingTable turns off accounting
> </AuthBy>
> </Realm>
>
> However, how do I disable the user from connecting if the Accounting
> Database is down
> because the AuthByPolicy ContinueAlways will allow him to be connected
> regardless.
>
A better approach is to have a second Accounting Database, so the AuthBy can
failover in case the first server has a problem. In addition, you can log to a
local file on the Radiator host and post process to re-synch the Accounting
Database when it comes back. Most operators try very hard not to stop people
from connecting.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
