Vincent, Fabien wrote:
Of course ! But to simplify documentation, I've put all in one file radiusd.conf except sql requests / config
That's a terrible idea. You can't get the server to work the way you want, but you're willing to completely change it's configuration? That makes no sense.
Another question with Perl / Accounting :
I want to made accounting on my F5 LTM / GTM. But the F5 uses something "special", because all Audit logs are forwarded to the Radius using syslog-ng. The consequence is that the Accounting-Request is coming with the following format :
Ready to process requests. rad_recv: Accounting-Request packet from host 10.10.10.12 port 47931, id=4, length=235 NAS-IP-Address = 127.1.1.1 F5-Acct = "Oct 18 17:18:59 local/lb2b notice mcpd[4820]: 01070417:5: AUDIT - user radtest - transaction #40213784-2 - object 0 - modify { pool_member { pool_member_pool_name \"...... WARNING: Empty section. Using default return values. +- entering group accounting {...} Invalid Accounting Packet
That message is generated by the Perl module.
++[perl] returns invalid Finished request 0.
Did you know if it's normal that the accounting section reject the accounting packet and say "Invalid Accounting Packet" ... Is it due to NAS-IP-Address attribute ?
No idea... look at the rlm_perl source.
And one more question, can I replace it dynamically with, for example, rlm_perl using the IP address from sender host (here 10.10.10.12 ?).
Yes. Alan DeKok.