Right. I was hoping there was a way for robust-proxy-accounting to respond to the NAS when the proxy isn't responding, since the accounting request has been "successfully" processed (i.e., written to the detail log and saved for later proxying).
So it's still waiting to be processed - it hasn't been successfully processed.
I'm adapting robust-proxy-accounting for our environment and can't figure out how (or if it's possible) to get FreeRADIUS to respond to the originating NAS when proxying fails and the detail is logged for later proxying.
Yep that's a good idea if the data is time critical, it also allows multiple requests to be forwarded in parallel.
nod, this is my preference. Unfortunately (as I mentioned above), I haven't been able to figure out if/how it's possible to have FreeRADIUS always respond to the NAS, even when the proxy isn't responding and accounting is spooled to the detail file for later processing.
Use appropriate policy (decoupled accounting). Ivan Kalik Kalik Informatika ISP