(RADIATOR) How do MaxSessions work with Rewrite ?

[Hugh Irvine]

Hello Ross -

The thing to keep in mind is that the NAS maintains its internal session 
table with the username that was entered by the user. If you are using 
RewriteUsername in your configuration file, you should set up an SQL session 
database and add a column for the rewritten username. Then you can modify the 
session database queries to do whatever you require.

regards

Hugh


On Wed, 16 Jan 2002 09:43, Ross Kusler wrote:
> Hey Hugh,
>
>     I'm using Radiator with Sessions and NASType to hopefully prevent users
> from logging on more than once at a time... however I'm a little confused
> as to how this works with Rewrite statements.
>
>     Here's a very simple version.  If a user logs in with username   bob,
> the rewrite changes it to bob... then the Call gets logged and the user is
> added into a session as "bob".
>
>    If he tries to log in again as "Bob", the write changes it to "bob"...
> then Radiator sees that 'bob' is already logged in, and queries the Nas
> server.  However won't the Nas server say that "Bob" is logged in on that
> port instead of "bob".. and allow the user to log in ?
>
> Ross Kusler
> InReach Internet LLC

-- 
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.