Hi All, I thought I would share something that had me very confused for a couple of hours this morning. It is not really a bug, rather my poor implementation of reporting the contents of Radonlne. But it may help some others on the list.
This relates to NAS's that send interim 'Alive' packets in addition to start and stop packets. (For people in Australia - Comindico do this) It appears that whichever module manages the Radonline table takes this packet and adds or replaces the current radonline details with these updated details including specifically the timestamp field. I have an inhouse web page we use to report active users using the radonline database. This page calculates the time a user has been online as the time difference between 'now' and the value in the radonline record 'timestamp'. This works fine for NAS's that don't send alive packets, but it reports incorrect information for those that do - it reports the time since the last alive packet instead of the time since login. After reading the doco the solution I found is to change the default RADONLINE table and create a custom AddQuery to also insert acctsessiontime values into radonline. I then had to adjust my web page to calculate and report based on both the timestamp and the interim acctsessiontime. I hope this helps others. It had me convinced that a NAS 'upgrade' was causing users to drop off after 15 minutes (ie the time between 'alive' packets) Regards, Brian Morris === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
