Hi,
Hello List,
I have asked this before (http://readlist.com/lists/lists.freeradius.org/freeradius-users/1/7788.html) and Alan DeKok did say that I should place those accounting packets in a different Acct-Type, but that was when I did not wish to log the information but I now need to log the information and replicate to all radius servers.
I need to know why the radrelay application stops replacation when it comes across a 0 session length packet. This morning I found a 40Mb backlog file for each server and realised that it was the 0 session-length packet again.
I know FreeRadius does complain about it but it still logs this accounting packet into the sql database. So is it because FreeRadius indicates that an error (0 Session Length?). If so could I not just somehow tell FreeRadius to stop complaining and just accept the stupid packet. (As I am passing configurable triggers via 0 session length radius packets).
I have similar issues (had similar issues) and my detail config now only fires stuff into the detail log for 'out of band' SQL processing if that Acct-Session-Time does not = 0. however, I believe that the latest CVS version (so this will be in 2.0.5) now handles session time of 0 alan