Hello Roy -
On Sat, 27 Nov 1999, Roy Hooper wrote:
> I'm looking at the session database, and it appears that Acct-Start records
> are not what is used to create an entry, but rather authentication-Accept
> packets.
>
> Is there a particular reason for this? I'm finding that this method is
> leaving stray data behind.
>
Here is the relevant code fragment from Handler.pm:
if ($status_type eq 'Start' || $status_type eq 'Alive')
{
# Some Ciscos dont send accounting-on, so we will
# detect a reboot with the first session (ID 00000001)
$sessdb->clearNas($nas_id, $p)
if $session_id eq '00000001';
# Ciscos sometimes sends Alive. Use them to make _sure_
# there is an entry in the database
$sessdb->add($original_username, $nas_id, $nas_port, $p);
}
elsif ($status_type eq 'Stop')
{
$sessdb->delete($original_username, $nas_id, $nas_port, $p);
}
As you can see, the session database is updated from the Accounting packets
(Start, Alive and Stop). The Access-Request packet is used as a tidy up to
remove session database entries that may not been removed due to a missed Stop.
Perhaps there is something else amiss? Send us a trace 4 debug log and we'll
have a look.
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.
