(RADIATOR) multiple DEFAULT behavior

[Hugh Irvine]

Hello Viraj -

Your assumption is correct.

What you show below is usually a better way to set up this sort of 
authentication, because the configuration file does not need to be altered 
and Radiator will automatically detect any changes in the file used by the 
AuthBy FILE clause and reload it as needed.

regards

Hugh


On Sat, 8 Jun 2002 00:44, Viraj Alankar wrote:
> Hello,
>
> If I have something like the following in a AuthBy FILE:
>
> DEFAULT Calling-Station-Id = 111, Auth-Type = A
>
> DEFAULT Calling-Station-Id = 111, Auth-Type = B
>
> This seems to do the same behavior as if A and B were in an AuthBy GROUP
> with a policy of ContinueUntilAccept. Is it safe to assume this? i.e. will
> Radiator continue processing these DEFAULT entries if a request came in
> with Calling-Station-Id = 111 but failed Auth-Type A?
>
> Viraj.
> ===
> 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.

-- 
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.