freeradius@puchol.com wrote:
i had to coerce the latest cvs version into fedora core 3 with more hacks than i would have liked,
Such as...? It's a development version, so not everything works.
one issue i find so far is that my NASs have a dynamic ip.
That's evil. Very evil.
i managed this externally at great pains, however, for the purposes of radius accounting, i'd like to see the accounting records on a per-nasid file in
/var/log/radius/radacct/<nasid>
rather than what i see now as:
/var/log/radius/radacct/<ip-address>
Step 1: Find out which module writes those files Step 2: Edit the modules configuration See "radiusd.conf". You're probably looking for th e"detail" module.
while i am on the list, and at the risk of irking someone i would like to (lazily) ask if anyone knows offhand where can i find a document that i saw a few months back on "hardening" radiusd. the process exited on me a couple of times due to dynamic ip issues, creating multi-hour blackouts that i rather not see again. looking for freeradius hardening or crashing i cannot seem to find that most excellent list of things to restart or manage a crashed server.
doc/supervise-radiusd.txt Alan DeKok.