(RADIATOR) Configuration help for fail-proff authentification method

[Hugh Irvine]

Hello Antonio -

A simple approach would be to do something like this (which may not be 
what you want):

<Realm DEFAULT>
	AuthByPolicy ContinueWhileAccept
	<AuthBy GROUP>
		AuthByPolicy ContinueWhileIgnore
		<AuthBy SQL>
			.....
		</AuthBy>
		<AuthBy INTERNAL>
			DefaultResult ACCEPT
			.....
		</AuthBy>
	</AuthBy>
	<AuthBy DYNADDRESS>
		.....
	</AuthBy>
	.....
</Realm>

regards

Hugh


On Friday, Mar 14, 2003, at 03:29 Australia/Melbourne, Antonio Navarro 
Navarro wrote:

> Hi all,
>
> I have a radiator configured with a PostgreSQL user database. Last
> night the database failed, and the users where unabled to connect. The
> configuraion section related to the Realm follows :
>
> <Realm DEFAULT>
>   AuthByPolicy ContinueWhileAccept
>   RewriteUsername tr/A-Z/a-z/
>   <AuthBy SQL>
>     DBSource dbi:Pg:dbname=radiator
>     DBUsername xxxxxxxxxxx
>     DBAuth xxxxxxxxxxx
>     DefaultSimultaneousUse 1
>     AuthSelect select PASSWORD, CHECKATTR, REPLYATTR from SUBSCRIBERS 
> where USERNAME='%n'
>     AccountingStopsOnly
>     AccountingTable accounting
>     AcctColumnDef USERNAME,User-Name
>     AcctColumnDef TIME_STAMP,Timestamp,integer
>     AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type
>     AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer
>     AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer
>     AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer
>     AcctColumnDef ACCTSESSIONID,Acct-Session-Id
>     AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer
>     AcctColumnDef NASPORT,NAS-Port,integer
>     AcctColumnDef NASPORTTYPE,NAS-Port-Type
>     AcctColumnDef FRAMEDIPADDRESS,Framed-IP-Address
>     AcctColumnDef CALLINGID, Calling-Station-Id
>     AcctColumnDef CALLEDID, Called-Station-Id
>   </AuthBy>
>   <AuthBy DYNADDRESS>
>     AddressAllocator MainClass
>     PoolHint Dynamic
>     StripFromReply PoolHint
>   </AuthBy>
>   AddToReply Service-Type=Framed-User, Framed-Protocol=PPP
> </Realm>
>
> ¿ What can I do in order to allow users to connect if the database
> server fails ?
>
> Best regards,
>
> Antonio Navarro Navarro
> hostmaster at bemarnet.es
> BemarNet Management
> http://www.bemarnet.es
>
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.