AuthByPolicy has to do with the processing of the AuthBy's in Handlers,
not the handlers themselves. Radiator will process the Handlers in
order they are in the config file, and will only process the first
match. that's it. If you want to do multiple things with the same
packet, you would have to configure only 1 Handler, and multiple
AuthBy's to do more than one thing with a packet.
Michael
On 27/03/13 12:41 PM, Michael Newton wrote:
On 27 March 2013 09:29, <radiator-requ...@open.com.au
<mailto:radiator-requ...@open.com.au>> wrote:
My requirement is to process and handle ,Alive and Stop packet
separately and the configuration must be called/processed
separately ,each time the radiator receives it based on the Acct
Status type as described above. Please help me out , i could not
find an explanation for this anywhere and i am confused. Please
let me know, if you need any more specifics to help me out.
There shouldn't be any problem with using <Handler
Acct-Status-Type=Start>, <Handler Acct-Status-Type=Alive>, or <Handler
Acct-Status-Type=Stop>, it is how we do accounting on our server.
Maybe make sure you you are using "AuthByPolicy ContinueWhileIgnore"
if you have problems with subsequent handlers not getting called?
If that doesn't help, I'd suggest posting the config that doesn't work
instead of the one that does; other people may be able to provide more
suggestions.
Mike
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator