Hello Anura -
On Mon, 06 Dec 1999, Anura Abayaratne wrote:
> Hi there,
>
> We have installed radiator 2.14.1 on BSDI 4.0.1. Sometime we get multiple
'Stop' records for the same session. That means, For one 'start' record we get
multiple Stop records in accounting. this can be a serios problem when
charging from Customers.
> If Someone can tell me how to avoid these multiple Stop records, It would be
vary much appreciated.
This is almost certainly due to timeouts and retransmissions. There should be
configuration parameters in the NAS to specify how long to wait for a Radius
response before sending a retry. Depending on your network environment, this
should be set to a realistic value for your expected transmission times. There
is also a Radiator Client parameter called DupInterval which can be set to deal
with (identical) duplicates caused by multiple transmission paths. Note that
the example configuration files usually show DupInterval 0 for the localhost,
but this should not be used in real operational clients because it will cause
all duplicates to be accepted. The Radiator 2.14.1 default value is 2 seconds
if the parameter is not set and this is probably acceptable for 99% of all
cases.
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.
