I already sent separate email to P.K. with details of our setup, since it seems to be close to what he wants to do. A couple of comments on this discussion:
> "P. K." <[EMAIL PROTECTED]> wrote: >>Thanks for your reply. Unfortunately, the FreeRadius documentation and >>support is so abysmal ... Alan DeKok wrote: > And I will note that I've dealt with many people who've installed > multiple servers, commercial and open source. Most say that the > FreeRADIUS documentation is more than adequate for their needs. Strange as it may seem, I agree with both of you: - Alan: The documentation is adequate; I've learned everything I need to know about FreeRadius from the included documentation, as well as from websites and asking careful questions on this list. - P.K.: It is abysmal: a collection of man pages, assorted text files, sample scripts and source code comments, with no overarching organization or index (except for 'grep'). As I said in private email, it's like a hologram: all the information is there, but you have to look at all of it to make sense out of how FR works. I've never complained on this mailing list about the quality of the documentation, because I already know the answer I'll get: "Write something better and submit it." When I get time (IF I get time) I'll do that. Until then, I'll make do with what's there. -- George C. Kaplan [EMAIL PROTECTED] IST - Infrastructure Services 510-643-0496 University of California at Berkeley - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html