Hello Tim -
No you can't have logical "or" definitions in Handlers.
What I usually do is something like this:
# define AuthBy clauses with Identifiers
<AuthBy ....>
Identifier SomethingDescriptive
......
</AuthBy>
<AuthBy ....>
Identifier AnotherDescription
.....
</AuthBy>
# define an AuthBy GROUP if required
<AuthBy GROUP>
Identifier CheckUsers
AuthByPolicy ContinueUntilAccept
AuthBy SomethingDescriptive
AuthBy AnotherDescription
.....
</AuthBy>
......
# define Handlers
<Handler Realm=dsadsadasd>
AuthBy CheckUsers
.....
</Handler>
<Handler Called-Number=/4343/>
AuthBy CheckUsers
.....
</Handler>
......
I also tend to find that if I construct my Handlers correctly, a final
<Handler> clause will catch "everything else" - ie an inclusive "or".
BTW - an added benefit in constructing configuration files in this fashion is
that they tend to be *much* easier to read, understand and maintain.
regards
Hugh
On Fri, 26 Apr 2002 23:05, Timothy G. Wells wrote:
> Greetings,
>
> Can a Handler have an "or" situation instead of an "and" situation, for
> instance?
>
> <Handler Realm=dsadsadasd **or** Called-Number=/4343/ >
>
> I'm hoping I didn't miss this in the manual ;)
>
> -- Tim
>
>
>
> Timothy G. Wells
> Good News Internet Services
> [EMAIL PROTECTED]
> http://www.goodnews.net
--
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
