Hello Arturo -
On Tue, 18 Jan 2000, Arturo Pina wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > On a related topic - this is the reason that many people use
> > AccountingStopsOnly in their accounting database - because
> > it is impossible to
> > always match every Start and Stop (one of the disadvantages of
> > UDP).
> >
>
> Just a little question: Is it possible then to enforce MaxSessions
> just with AccountingStopsOnly?
> Thx for your help.
>
Yes - the MaxSessions are checked against the Access-Request's, which happen
before the Accounting-Request's. The normal sequence of events is this:
1. user dials the NAS
2. some NAS's can check the Calling-Station-Id and/or Called-Station-Id before
answering the phone
3. NAS answers the phone
4. modem training sequence occurs
5. NAS starts PPP negotiation
6. NAS does authentication as part of PPP (CHAP or PAP usually)
7. NAS sends radius Access-Request to Radiator (which does Sim-Use)
7a Radiator updates SessionDatabase (delete only)
8. if Access-Accept, complete PPP negotiation (if not disconnect)
9. if PPP completes successfully, NAS sends Accounting-Request (Start)
9a. Radiator updates SessionDatabase and writes accounting record
10. when call completes, NAS sends Accounting-Request (Stop)
10a. Radiator updates SessionDatabase and writes accounting record
NB. Radiator manipulates the SessionDatabase independently to writing the
accounting records
If you need any other help feel free to ask questions.
cheers
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
