Stefan A. wrote:
I want to send RADIUS Accounting Messages to another RADIUS Server, depending on some contents of a Packet.
'a Packet' in this context might be an Access or an Accounting Packet.
The Access-Request && Accounting-Request packets are handled independently. If you want to change accounting behavior based on authentication packets, you will need to store information in database.
The intended Flow:
Packet comes in ... - for Access type, check if user might be authenticated - if OK, try to decide to send an Accounting packet to a Server on some attributes (in my case, VSA from downstream RADIUS Proxy Server)
Do you mean *create* an accounting packet, or forward *later* accounting packets for that session?
- (possibly) don't care about the answer - for Access type: accept/reject to Client - for Accounting type: ACK to Client
As far as I understood, the proxy module does - (only) proxy based on realm - in proxy module, normal local Logfiles won't be used
That's not true. You can proxy based on anything you want. See raddb/proxy.conf for documentation. You can proxy *and* log to detail files. Alan DeKok.