(RADIATOR) accounting double up avoidance

Hugh Irvine hugh at open.com.au
Mon Nov 18 02:35:09 CST 2002


Hello Brad -

This is a difficult problem, however, accounting records with a 
non-zero Acct-Delay-Time attribute will have the "Timestamp" attribute 
automatically corrected (ie. the Timestamp reflects the time the event 
occured, not the time it was sent). You should be able to use this fact 
in the indexes you mention below. Otherwise, you should post-process 
the stop records and remove the duplicates then.

regards

Hugh


> Just wanted some opinions on accounting double up avoidance.
>
> We are using mysql with radiator and currently we get double ups mainly
> from VISP services (due to congestion) and sometimes from our local 
> NAS's
>
> We are using the bog standard insert statements. We have dupintervals 
> at
> 10 secs for all clients
>
> At first I thought it would be simple to have a unique index in the
> accounting table based on the account session id but as we know our 
> cisco
> NAS's don't give a unique account session id. I then thought maybe a
> concatenation of acct sessionid, nasport and curdate()(or something 
> like
> that) as a unique index in the table. Then this would leave the insert
> queries failing on double ups
>
> How would radiator handle this? Our double ups at best are sometimes 
> ten
> times in a row (the radius data comes across the wan for VISP) I know 
> this
> wouldn't be really great but when you look to other methods that I have
> thought of below ....
>
> I thought maybe a replace based on the same concatenated unique index
> above in a where clause would work but then account start and stop 
> times
> shift right with every double up as they are based on timestamp -
> acct-sessiontime(starttime) and timestamp(stop time)
>
> I did notice in the doco the example of using the AcctInsertQuery with 
> a
> update or insert query. Again I can see that this will move the 
> acctstart
> & stop times right with every double up.
>
> Anyway thats where I am at. Any feedback or comments would be 
> appreciated
>
> --
> Brad Lilly
> Ph +61244218555
> Fax +61244218500
>
> -------------------------------------------------------
>
> -- 
> Mike McCauley                               mikem at open.com.au
> Open System Consultants Pty. Ltd            Unix, Perl, Motif, C++, WWW
> 24 Bateman St Hampton, VIC 3188 Australia   http://www.open.com.au
> Phone +61 3 9598-0985                       Fax   +61 3 9598-0955
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
> TTLS etc on Unix, Windows, MacOS etc.
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list