Hello Gordon -

On Thu, 14 Dec 2000, Gordon Smith wrote:
> Thanks Hugh,
> 
> I've CC'd to the list for the benefit of others with similar queries.
> 
> Basically, this is a new ISP that has been hosting one group of users. We
> are now bringing online two more ISPs to be run as virtual branded products.
> For reporting and management convenience, it was my intention to split user
> authentication and accounting information into different tables for each
> realm.

Authentication and accounting are already in seperate tables.

> The problem at the moment is that Radmin strips the realm portion of the
> username when displaying such pages as current usage. Rather than patch the
> script, I was thinking that perhaps just using the realm to point Radiator
> to the correct set of database tables would be a tidier way to go. That way,
> I wouldn't run into upgrade problems further down the track.
> Should the separate Log SQL clauses be placed within the AuthBys? Or outside
> the AuthBy but within the Realm clause?
> 

Log SQL is for server messages, not accounting.

> If there is a better way to do this, I'd love to know. This just seemed to
> be the most efficient way to be able to keep reporting, etc tidy.
> 
> I've also noticed that radwho.cgi will display the username that the user
> logged on with, before passing through the rewrite rules. Easy enough to do
> rewrites within the CGI script, but something I thought I'd let you know
> about.
> 

I am still not clear on your requirements, perhaps you could state them a bit
more clearly after you have had some sleep?

;-)

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

Reply via email to