I have two outstanding suppor calles relting to proxying of accounting info to a 3rd party radius server ( Freeradius 2.2.9)
Issue 1
I add the Filter-Id attribute to the outgonig accounting packet containing the username associated with the session. Initially it didn't work. Now it works ..... sort of. A lot of the time it does have the username associatged with the auth session .... otheewise it has someone elses username or no filter-id attribute at all!
Issue 2
If I try rolling accounting proxying out over all my services, the polcy manager hangs and the radius module sends access-rejects to everyone.
Eventually a watchdog (?) restarts the policy manager and some auths work correctly ... then it hangs again ... and the loop goes round.
Managed to configure things so 1 service can proxy accounting packets by "tweaking" a policy manager thread setting, but thats only for 1 service doing accounting
A