On Mon, 14 Jun 1999, Mike McCauley wrote:
> Hi James.
>
> On Jun 11, 2:21am, James H. Thompson wrote:
> > Subject: Re: (RADIATOR) Simultaneous use
> > Since the NAS reply items are different for each NAS, I'd have to setup
> > 3 full sets of check/reply items for each user. That sounds like
> > too much work. How would I do it by chaining the File authentications?
> I was thinking about something like this:
>
> <Realm DEFAULT>
> AuthByPolicy ContinueAlways
Shouldn't the line above be:
AuthByPolicy ContinueWhileAccept
if the first Authby Rejects, we don't want to
let the next accept it?
> <AuthBy FILE>
> DefaultSimultaneosUse 1
> Filename xxx
> </AuthBy>
> <AuthBy FILE>
> Filename yyy
> </AuthBy>
> </Realm>
>
> In file xxx:
> # This make user1 and user2 have a sim-use limit of 2, everyone else gets 1
> DEFAULT
> user1 Simultaneous-Use=2
> user2 Simultaneous-Use=2
>
>
> IN file yyy:
>
> DEFAULT NAS-Identifier = "LRD56_82BE00", Auth-Type = ljnet_sql
> Service-Type = Framed-User,
> Framed-Protocol = PPP,
> Framed-Compression = Van-Jacobson-TCP-IP
> Idle-Timeout = 400
>
> # Nortel
> DEFAULT NAS-Identifier = "las-nortel", Auth-Type = ljnet_sql
> Service-Type = Framed-User,
> Framed-Protocol = PPP,
> Framed-Compression = Van-Jacobson-TCP-IP
> Idle-Timeout = 200
>
> etc.
>
> So the effect is that xxx checks the sim-use amd yyy check everything else.
>
>
Jim
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
