Re: (RADIATOR) Current Logged in Users

2002-02-11 Thread Hugh Irvine


Hello Rolando -

On Tue, 12 Feb 2002 01:03, Rolando Riley wrote:
 When I say 'fairly accurate' - if your NAS fails to deliver a STOP record
 to radiator, the user will not be removed from the online users database.


 The above  seems to be very common to happen. That is

 1) hanged users which can't auth  because of a Max Sessions reached and no
 STOP record sent by the NAS has been taken
 2) Sometimes hanged RADIUS. That still happens to us when we change all the
 auths to LDAP. And it is due to the same cause in point 1)

 My question is:
 1) what is the accurate way to use scripts like scripts like
 goodies/cleanup.txt or checksessiondb.txt

These scripts are designed to be run periodically from cron or similar.

 2) do you know what are the frequent causes that  make NAS don't send the
 STOP record ?


The two most frequent causes are congested links dropping UDP packets or NAS 
software bugs that don't send them at all.

regards

Hugh


-- 
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) Current Logged in Users

2002-02-11 Thread Brian Morris



Hi Shane - 

Just add this code to the bottom of your radius.cfg 
file (or whatever you call yours)

SessionDatabase SQL 
DBSourcedbi:ODBC:RadiusLog 
DBUsernameradiususer 
DBAuthradiususerpassword/SessionDatabase

Where :
- RadiusLog is your ODBC datasource setup for 
Radiator (you probably already have this for authentication and accounting - use 
the same one)
- radiususer is the SQL user account with access to 
the above datasource
- radiususerpassword is the above users password 
for accessing the SQL datasource

You should have/create a table within the above 
database calledRADONLINE its structure and details can be found in the 
goodies section. Use the suggested structure for now (that way you can 
accept the defaults) but you can add to it to record additional helpful info 
later if you want.

Regards, Brian Morris




  - Original Message - 
  From: 
  Shane 
  Malden 
  To: Brian Morris 
  Sent: Monday, February 11, 2002 4:10 
  PM
  Subject: Re: (RADIATOR) Current Logged in 
  Users
  
  Thanks for this. Do you use NT and SQL yourself 
  or just know Radiator fairly well?? Do you have any sample code on how 
  so get Radiator to log this information??
  
  Regards,
  Shane
  
- Original Message - 
From: 
Brian 
Morris 
To: Shane Malden ; [EMAIL PROTECTED] 
Sent: Monday, February 11, 2002 3:22 
PM
Subject: Re: (RADIATOR) Current Logged 
in Users

If you are using an SQL back-end database, the 
RADONLINE table contains a fairly accurate list of all users currently 
online.

When I say 'fairly accurate' - if your NAS 
fails to deliver a STOP record to radiator, the user will not be removed 
from the online users database.


  - Original Message - 
  From: 
  Shane 
  Malden 
  To: [EMAIL PROTECTED] 
  Sent: Monday, February 11, 2002 2:59 
  PM
  Subject: (RADIATOR) Current Logged in 
  Users
  
  Does anyone know any simple way of seeing who 
  is logged on, using the logs from Radiator? We do receive start and stops 
  from our gear. We are running ver 2.19 on a NT Server. Any help would be 
  appreciated.
  
  Regards,
  Shane


(RADIATOR) Current Logged in Users

2002-02-10 Thread Shane Malden



Does anyone know any simple way of seeing who is 
logged on, using the logs from Radiator? We do receive start and stops from our 
gear. We are running ver 2.19 on a NT Server. Any help would be 
appreciated.

Regards,
Shane


Re: (RADIATOR) Current Logged in Users

2002-02-10 Thread Brian Morris



If you are using an SQL back-end database, the 
RADONLINE table contains a fairly accurate list of all users currently 
online.

When I say 'fairly accurate' - if your NAS fails to 
deliver a STOP record to radiator, the user will not be removed from the online 
users database.


  - Original Message - 
  From: 
  Shane 
  Malden 
  To: [EMAIL PROTECTED] 
  Sent: Monday, February 11, 2002 2:59 
  PM
  Subject: (RADIATOR) Current Logged in 
  Users
  
  Does anyone know any simple way of seeing who is 
  logged on, using the logs from Radiator? We do receive start and stops from 
  our gear. We are running ver 2.19 on a NT Server. Any help would be 
  appreciated.
  
  Regards,
  Shane


Re: (RADIATOR) Current Logged in Users

2002-02-10 Thread Hugh Irvine


Hello Shane -

It isn't particularily easy to tell who is logged on just by looking at the 
logs. On NT it is probably easiest to set up an SQL session database with 
MS-SQL and use the radwho.cgi script in a web server.

regards

Hugh


On Mon, 11 Feb 2002 14:59, Shane Malden wrote:
 Does anyone know any simple way of seeing who is logged on, using the logs
 from Radiator? We do receive start and stops from our gear. We are running
 ver 2.19 on a NT Server. Any help would be appreciated.

 Regards,
 Shane

-- 
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.