>
>
>> Hi people,
>>
>> We are having trouble with stale records in our SessionDatabase.
>>
>> The NAS is a Nortel Shasta that doesn't seem to have a reasonable means
>> of being queried about a particular Acct-Session-Id or Username/Framed-IP-
>> Address.
>>
>> We started using Ping, but it seems to be giving addresses on a FIFO
>> basis, so they are almost immediatly re-used making this method useless.
>>
>> The people at Nortel say that they can configure it so it sends Acct-
>> Interim-Update packets every <N> minutes.
>>
>> What we could do is to catch every Acct-Interim-Update packet and make an
>> update on the SessionDatabase record's Timestamp.
>>
>> Now, if we have a user trying to authenticate and according to our
>> SessionDatabase it would exceed it's Simultaneous-Use value, we could
>> check every record for this user and if the Timestamp is older than <N>
>> minutes + 10% (or something like that), we consider it invalid and allow
>> the user in again.
>>
>>
>> How would I do this?
>>
>>
>> That is, as there is an AddQuery for an Acct-Start and a DeleteQuery for
>> an Acct-Stop, I would need to use a kind of "UpdateQuery" for an Acct-
>> Interim-Update. How can I do this?
>>
>>
>> Where should I handle the Simultaneous-Use check? That is, now I simply
>> set a NasType in the Shasta's <Client> entry. How can I use an arbitrary
>> perl function for this?
>>
>>
>> Thanx.
>> --
>> Baby
>>
>>
>> --
>> PS: If one of the Shasta users out there is handling lost Acct-Stop
>> packets in some other way, I would very much like to know... as we are a
>> third party and not the ISP itself, we don't have direct access to the
>> Nortel people.
>>
>>
>
>I forgot... our current setup is a Netra T1 with 512Mb RAM running
>Radiator 2.17.1 and MySQL 3.22.32 for the SessionDatabase.
>
>The accounting database we have just moved it out to another Netra T1
>running also MySQL because it appeared that making queries on the
>accounting database slowed down the machine (though I ain't that sure
>about this).
>
>The question is, do you think that adding all these Acct-Interim-Update
>packets and espcially the update queries can degrade the performance of
>the radius server?
>
>There are currently between 2000 and 3000 users on line simutaneously and
>they are usually connected for long periods... I would risk something
>like 4 hours average but made no real statistics on this.
With the proper indexes on the database tables, you should be fine.
(see my previous mail regarding your problem)
regards
Hugh
--
NB: I am travelling this week, so there may be delays in our correspondence.
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
