Re: What is the minimal attributes that must be in START, INTERIM UPDATE and STOP packets
On Fri August 8 2003 01:10, Aime wrote: > Hello All, > > What are the minimal attributes to use to issue > START , INTERIM UPDATE and STOP radius packet ? This is set on your NAS. Read the documentation for your NAS and it shoudl tell you how to enable these features. -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: What is the minimal attributes that must be in START, INTERIM UPDATE and STOP packets
On Fri, Aug 08, 2003 at 02:02:46AM -0700, Aime wrote: > I have no hardware NAS. > I am just writing a radius client in Perl, and i am > wondering what the radius server is expecting as > minimal attributes in check items to honour STOP , > INTERIM UPDATE AND STOP accounting request I think reading rfc2058/59 might help you. There is no minimal set, but normally you will have something like: Start: User-Name, NAS-IP-Address, Acct-Status-Type, Acct-Session-Id Update: Start plus perhaps Acct-Session-Time, Acct-Input-Octets, Acct-Output-Octets, ... Stop: Update plus perhaps some disconnect cause attributes... but that depends on the type of service. Perhaps this is no service with traffic accounting, or you can't know a cause... Oliver. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: What is the minimal attributes that must be in START, INTERIM UPDATE and STOP packets
Aime <[EMAIL PROTECTED]> wrote: > I am just writing a radius client in Perl, and i am > wondering what the radius server is expecting as > minimal attributes in check items to honour STOP , > INTERIM UPDATE AND STOP accounting request Try reading the RFC's. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html