(RADIATOR) handlers and realms

[Shon Stephens]

thanks for all responses. i will just use <handler> then. 

shon

-----Original Message-----
From: Hugh Irvine [mailto:hugh at open.com.au]
Sent: Friday, August 30, 2002 12:25 AM
To: Shon Stephens
Cc: 'radiator at open.com.au'
Subject: Re: (RADIATOR) handlers and realms



Hello Shon -

You *should* not mix Realms and Handlers - it is possible to do - but it 
is almost impossible after the fact to understand what is going on when 
trying to debug problems.

Here is what to do:

<Handler ......>
	......
</Handler>

<Handler Realm = foo.com>
	......
</Handler>

<Handler ....>
	......
</Handler>

Keep in mind that Handlers are evaluated in the order they appear in the 
configuration file, and the first match is the only match, so the more 
specific Handlers must appear before the more general.

Also note that in some cases it makes sense to split the processing into 
two (or more) seperate instances of Radiator, depending on what else you 
are trying to do.


regards

Hugh


On Friday, August 30, 2002, at 11:13 AM, Shon Stephens wrote:

> i am not sure, but i thought i read that you should not (or could not?) 
> use
> <handler> and <realm> in the same radius config file. is this true? if 
> so,
> what to do if for some clients i need to use a handler, and others a 
> realm?
>
> thanks,
> shon
> ===
> 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.