Hi Alan, thanks for the answer. One more questions, is it possible to create a detail file per listening port? If it is, that would let you proxy accounting without having to write logic to segregate real nas from radius severs proxying, right? Thanks. Regards On Fri, May 22, 2015 at 10:46 AM, Alan DeKok <aland@deployingradius.com> wrote:
On May 21, 2015, at 9:20 PM, Ricardo Larrañaga < ricardo.larranaga@gmail.com> wrote:
I would like to implement redundancy on the accounting database using copy-acct-to-home-server. From what i understand, i should be able to maintain identical copies of the accounting tables this way, and i would be able to accomplish simultaneous use check, which would be desirable.
Sure, that's fine.
Now, first of all, each of the servers have a local accounting database, and i am writing to the database using an sql_buffered server. This works great.
Good.
Now, reading through the forums, i understand that having several readers reading on the same accounting file can bring unpredictable results, is this the case? In that case, can these two functions work together?
Yes. You just need to have TWO detail files. Each accounting packet goes into two detail files. The copy-to-home-server configuration reads one. The buffered SQL one reads the second.
Also is this kind of configuration scalable to more than two servers? I am wondering how can i configure each server to send the packets to 2 or more different servers at the same time (In the case i would like to increase to 3 servers, or even more)
That can be done. Just write multiple detail files, one for each destination. It's not perfect, but it does work.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html