On 16/07/13 04:24 PM, Heikki Vatiainen wrote: > On 07/13/2013 08:20 PM, Michael wrote: > >> So, my complicated config determines what device the request needs to >> go to and sends, and then it converts the POD and COA packets to >> accounting packets using scripting, then sends to my accounting >> handler and that POD/COA request is logged. > Ok, so that's where the 'Accounting rejected' log entry in your first > message came from. > > The default processing in Radiator will proxy back both ACKed and NAKed > messages. The latter will be logged as a failed message with > 'Change-Filter-Request rejected: thereason', but it will be proxied back > just like an ACKed reply. > > However, rejected accounting messages are dropped. The RADIUS spec does > not specify how to reject accounting messages, so there's no > Accounting-Rejected message type to send back. You get drops instead. > > Thanks, > Heikki >
hmm so, are you saying radiator after proxying out my POD/COA requests, and after i then convert the packet to an accounting packet and log it, radiator is actually expecting that the POD/COA reply coming back is actually an accounting reply and does not relay it to the radpwtst? _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
