(RADIATOR) Handle the same client with different handlers

[Hugh Irvine]

Hello Alex -

You cannot do what you show below because only the last Client clause 
is being used (the others are overwritten).

How should the requests be differentiated?

regards

Hugh



On 9 Jul 2004, at 20:26, Lopez, A. wrote:

> Hello all,
>
> I want to handle different types of requests coming from the same 
> client with different handlers.
>
> Since the username attribute is not present in those requests (I 
> cannot use the realm) I thought about defining such a client in three 
> different ways, as follows:
>
>  
>
> <Client Ipaddress>
>
>             Secret secret1
>
>             Identifier identifier1
>
> </Client>
>
> <Client Ipaddress>
>
>             Secret secret2
>
>             Identifier identifier2
>
> </Client>
>
> <Client Ipaddress>
>
>              Secret secret3
>
>             Identifier identifier3
>
> </Client>
>
>  
>
> And then handle the request based on the identifier:
>
> <Handler Client-Identifier=identifier1>
>
> …
>
> </Handler>
>
>  
>
> <Handler Client-Identifier=identifier2>
>
> ….
>
> </Handler>
>
>  
>
> The point is that the radius server complains “bad authenticator in 
> request”
>
> Can anyone tell me another way to do this?
>
> Thanks in adcance,
>
> Alex
>

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, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

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