I wanted to test this scenario: This is a sample configuration for robust proxy accounting. Accounting packets are proxied, OR logged locally if all home servers are down. When the home servers come back up, the accounting packets are forwarded. In my case freeradius detects that home server is down. I assume that freeradius will log accounting packet locally (via detail module) to the disk. I have checked /app_log/radius/ggsn/radacct/detail file, but accounting packet was not written. Therefore i sent debug output. On Sat, Apr 18, 2015 at 4:45 PM, Alan DeKok <aland@deployingradius.com> wrote:
On Apr 18, 2015, at 4:07 AM, Peter Balsianok <balsianok.peter@gmail.com> wrote:
I`m testing configuration for robust-proxy-accounting.
Here is my configuration file (sites-enabled/robust-proxy-accounting):
Please start off by describing what you're doing, and what the problem is. Don't post configurations unless we ask. 99% of the time it's not necessary. Forcing us to read through hundreds of lines of useless text is annoying.
As you can see packet is not written into disk (in the case of post proxy fail via detail module).
It's not supposed to be written back to the detail file.
The detail file reader will automatically retransmit packets that fail.
Reading from the detail file and then writing BACK to the detail file is a bad idea. It can cause all kinds of problems. So the server doesn't allow you to do that.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html