(RADIATOR) Lost Stop Record Scripts

[Hugh Irvine]

Hello Paul -

The "lost stop record" problem is in many ways directly due to the design of 
the radius protocol, as it is based on UDP and records can and do go missing. 
There are also various NAS software bugs that can cause accounting packets to 
go missing as well.

Most operators tend to do their accounting based on stop records alone and 
treat the lost records as operating overhead. 

Note that you could do something with a cron job that scans the session 
database and generates a stop record for any "stale" record and then deletes 
it. This is not a standard Radiator feature however.

regards

Hugh


On Tue, 23 Apr 2002 11:24, Paul wrote:
> Dear All,
>
> Does anyone have any scripts that can scan through a logfile and/or an SQL
> table and locate lost stop records, or identify which sessions have been
> lost based on Alive packets. We are having problems with Lost stop records
> and need to locate them so we can pass them onto our developers. Any advice
> or scripts would be apprciated.
>
> Thanks
>
> ===
> 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.