(RADIATOR) Question about handlers.

Fri Jan 28 17:28:00 CST 2005

Hello Ricardo -

Something like this:

# define Handlers

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

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

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

.....

<Handler>
	<AuthBy INTERNAL>
		DefaultResult REJECT
	</AuthBy>
</Handler>

regards

Hugh

On 29 Jan 2005, at 07:53, Ricardo Martinez wrote:

> Hello Hugh.
> 	I want to make a last question about this same issue.  What i want
> to do is after the RADIUS request is compared with all the Handlers 
> that i
> have in my configuration file, i want a last HANDLER which deny all the
> REQUEST that reach it.  So, if a REQUEST is not matched with the first
> HANDLERS the REQUEST is denied.
>
> Thanks,
>
> Ricardo Javier Martinez Ogalde
>
>> -----Mensaje original-----
>> De: Ricardo Martinez [mailto:rmartinez at redvoiss.net]
>> Enviado el: Jueves, 30 de Diciembre de 2004 18:27
>> Para: 'Hugh Irvine'
>> CC: 'radiator at open.com.au'
>> Asunto: RE: (RADIATOR) Question about handlers.
>>
>>
>> Hugh.
>> 	Thank you very much.  Now is working perfectly.
>> 	Best regards,
>>
>> Ricardo.-
>>
>> -----Mensaje original-----
>> De: Hugh Irvine [mailto:hugh at open.com.au]
>> Enviado el: Jueves, 30 de Diciembre de 2004 16:59
>> Para: Ricardo Martinez
>> CC: 'radiator at open.com.au'
>> Asunto: Re: (RADIATOR) Question about handlers.
>>
>>
>>
>> Hello Ricardo -
>>
>> You will need to order your Handlers with the most specific _before_
>> the more general.
>>
>> This is because the Handlers are evaluated in the order they
>> appear in
>> the configuration file with the first match being the only match.
>>
>> Therefore you should do something like this:
>>
>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>> h323-billing-model=numero:normal>
>> something 2...
>> </Handler>
>>
>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>> h323-billing-model=numero:800>
>> something3...
>> </Handler>
>>
>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>> h323-billing-model=numero:myrsta>
>> something4...
>> </Handler>
>>
>> <Handler Request-Type = Access-Request>
>> something...
>> </Handler>
>>
>> regards
>>
>> Hugh
>>
>>
>> On 31 Dec 2004, at 04:21, Ricardo Martinez wrote:
>>
>>> Hello List.
>>> 	I have a question regarding the Handlers.
>>> 	If i want to use different SQL querys for different types of
>>> request, based on a Attribute.  Which is the way to do this?.  The
>>> Attributes are :
>>>
>>> cisco-h323-billing-model = "h323-billing-model=numero:myrsta"
>>>
>>> or
>>>
>>> cisco-h323-billing-model = "h323-billing-model=numero:normal"
>>>
>>> or
>>>
>>> cisco-h323-billing-model = "h323-billing-model=numero:800"
>>>
>>> For the first query the attribute cisco-h323-billing-model is not
>>> present so
>>> i want to use a Hadler like this :
>>>
>>> <Handler Request-Type = Access-Request>
>>> something...
>>> </Handler>
>>>
>>>
>>> Then for the other subsequent request i have to match in one of the
>>> next
>>> handlers :
>>>
>>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>>> h323-billing-model=numero:normal>
>>> something 2...
>>> </Handler>
>>>
>>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>>> h323-billing-model=numero:800>
>>> something3...
>>> </Handler>
>>>
>>> <Handler Request-Type = Access-Request, cisco-h323-billing-model=
>>> h323-billing-model=numero:myrsta>
>>> something4...
>>> </Handler>
>>>
>>> But is not working....
>>> Can anyone help me?.
>>> For a normal transaction the first auth packet is like this one :
>>>
>>> 	User-Name = "1234567890987654"
>>> 	cisco-h323-conf-id = "h323-conf-id=1583381F 599A11D9 8521ED09
>>> C78C1568"
>>> 	cisco-avpair = "h323-ivr-out=transactionID:51"
>>> 	Calling-Station-Id = "xxxxx100"
>>> 	NAS-Port-Type = Async
>>> 	Cisco-NAS-Port = "ISDN 1/0:15:2"
>>> 	NAS-Port = 0
>>> 	Service-Type = Login-User
>>> 	NAS-IP-Address = xx.xx.xx.71
>>>
>>> I want this packet in the first handler.
>>>
>>> Then the 2nd auth packet is like this :
>>>
>>> 	User-Name = "1234567890987654"
>>> 	cisco-h323-conf-id = "h323-conf-id=1583381F 599A11D9 8521ED09
>>> C78C1568"
>>> 	cisco-h323-billing-model = "h323-billing-model=numero:myrsta"
>>> 	cisco-avpair = "h323-ivr-out=transactionID:52"
>>> 	Calling-Station-Id = "xxxx100"
>>> 	Called-Station-Id = "xxxxxxxxx7000"
>>> 	Service-Type = Login-User
>>> 	NAS-IP-Address = xx.xx.xx.71
>>>
>>> I want this second packet on a handler based on the
>>> cisco-h323-billing-model
>>>
>>>
>>> Thanks in advance
>>>
>>> Ricardo Martinez.-
>>>
>>> --
>>> 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 read the reference manual ("doc/ref.html")?
>> Have you searched the mailing list archive
>> (www.open.com.au/archives/radiator)?
>> Have you had a quick look on Google (www.google.com)?
>> 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.
>>
>
>

NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive 
(www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
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.