Hello All, Is there a succinct way to describe how freeradius processes requests? sort of a high level overview? Like: The radiusd daemon is running and receives a valid request It parses out attributes passed in with the request ... and then... That is the point where I'd like some clarification... what files does it parse as it continues, etc...? Any takers? If this is documented somewhere and I missed it, I apologize. Regards, Lin Richardson
"Lin Richardson" <lin@xmission.com> wrote:
Is there a succinct way to describe how freeradius processes requests? sort of a high level overview?
doc/aaa.txt is about as good as it gets.
That is the point where I'd like some clarification... what files does it parse as it continues, etc...?
Everything is driven off of radiusd.conf. The "authorize" section is run from top to bottom, and then one subsection of "authenticate" is run. Alan DeKok. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Lin Richardson