Hello Steve -
You will need to use cascaded AuthBy clauses and a users file:
# define AuthBy clauses
<AuthBy FILE>
Identifier CheckFILE
Filename ....
</AuthBy>
<AuthBy NT>
Identifier CheckNT
.....
</AuthBy>
# define Realms or Handlers
<Realm ....>
AuthBy CheckFILE
.....
</Realm>
Then in the users file you would have this:
# users file
DEFAULT Auth-Type = CheckNT
.....
user1 Auth-Type = CheckNT
Framed-IP-Address = x.x.x.x ,
......
user2 Auth-Type = CheckNT
Framed-IP-Address = y.y.y.y ,
......
.......
hth
Hugh
On Wednesday 30 May 2001 20:23, Steve Phillips wrote:
> Hiyas,
>
> has anyone got an example of how to do this ? we have a few hundred users
> authenticating off an NT domain and there is a need for around half of them
> to have static IP addresses, short of adding a seperate handler for each
> user with the reply attributes set in the conf file, is there any other way
> to assign static IP's to users authenticated off an NT domain ?
>
> Probably missing the obvious again (and yes, i've been busy reading the
> archives)
>
> --
> Steve.
>
> ===
> 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.
--
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.
