Hello Marites -
The first thing to do is to reduce duplicates to a minimum. Then you
can set the "DupInterval" parameter in your Client clauses to a value
that will handle the problem.
hth
Hugh
At 11:44 +0800 01/2/21, Marites L. Quitoriano wrote:
>hi hugh!
>
>we just have one concern. our company is offering prepaid cards.
>how can we prevent the Radiator not to automatically debit the
>ACCTSESSIONTIME from the TIMELEFT colum if we have
>duplicate stop records?
>
> thanks,
>---
>Marites Legamia-Quitoriano <[EMAIL PROTECTED]>
>AVP - Engineering
>Interdotnet Philippines, Inc.
>
>"Information and attachments herein are intended for the named recipients
> only. It may contain attorney-client privileged or confidential matter.
>If you
> have received this message in error, please notify us immediately by a
> collect phone call to +(632)8177746, and destroy the original message.
> Do not disclose the contents to anyone. Thank you."
>----- Original Message -----
>From: Hugh Irvine <[EMAIL PROTECTED]>
>To: Colin <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
>Sent: Thursday, January 01, 1970 11:01 AM
>Subject: Re: (RADIATOR) duplicate stop records
>
>
>>
>> Hello Colin -
>>
>> At 10:53 +1100 01/2/13, Colin wrote:
>> >Hi
>> >
>> >We seems to have a problem with stop records being entered into the
>> >mysql database.
>> >This does not happen all the time but seems to vary, however on
>> >occasions we have duplicate stop records logged. The duplicate record
>> >may be exactly the same with the same time, same ip, same octets etc. Or
>> >they are slightly different, eg, one instance involves one, where the
>> >stop record for a user, has been duplicated 7 time but at different
>> >times. eg: 12:54:05, 12:53:51, 12:53:36, 12:53:21....................The
>> >total usage of this user came to about 796 hours!! This is impossible as
>> >there was only about 744 hours in the month.
>> >
>> >The start records seems fine with no duplicates, it only happens on
>> >occasions with the stop records, which is enough to give us incorrect
>> >data.
>> >
>>
>> This sounds like a NAS bug. However, this is really an issue with
>> your post-processing, as the nature of the Radius protocol is such
>> that duplicates can and do occur. As such, your accounting processing
>> should really do duplicate removal before generating bills.
>>
>> hth
>>
>> 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.
>>
--
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.
