Hello Antonio -
On Fri, 14 Jan 2000, Antonio Coloma wrote:
> Hi everybody,
>
> We have detected that a session is added to the
> DatabaseSession only when Radiator gets an Start accounting-request, not
> when it receives an Access Request and this request is accepted. Why?
> Shouldn't add to session database when user is accepted?
> What happens If the start accounting-request arrives later
> than the stop accounting request?
>
Just because Radiator sees an Access-Request doesn't mean that a session
actually gets started. The only definite notification is via the
Accounting-Request. You will have noticed also that the Access-Request causes
Radiator to delete the entry in the SessionDatabase for that NAS/Port
combination (since clearly there cannot be a session there already) this is
done just to make sure. If you are concerned about maintaining strict coherence
of the SessionDatabase, you should enable the Simultaneous-Use checking and
turn on NasType for your Clients. This will cause Radiator to verify with the
NAS directly any possible inconsistencies.
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).
hth
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.
