> > I'm having to write my own validation and accounting for a device, > > Don't. Please. There are a number of RADIUS libraries available, > including freeradius-client, on freeradius.org. It's supported, it > works, and it's in use by a number of products. > I have no issue using a library. Right now I'm working with Net::Radius. But to use it I need to understand the flow since it only seems to be able to assemble and disassemble the packets, not tell me how to do it. > > > and I need to understand a little about the flow. Is there a good reference > > for this? I don't have to support much, basically user/pass authentication, > > updating accounting, timeout, logoff. > > See the RFC's. > Ok. I was hoping for something more than RFC's, but if thats the starting point, off I'll go. > > > I believe I next need to send an accounting_start packet. Some > > of the items I'm not sure where they come from (Acct-Session-Id, > > Acct-Unique-Session-Id) or how they might be generated. > > This is not a mailing list for general RADIUS questions. The RFC's > exist. Please read them. > Jawol. > > If you're doing this for a customer, you're getting paid. Don't > expect anyone here to help you (for free) to create your product that > has nothing to do with FreeRADIUS. > Actually, no, I'm not doing this for a customer. I'm doing it for an OpenSource/Sourceforge project, but I really appreciate your support in it all.
Tuc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html