RE: (RADIATOR) AuthBy NT & returning IP address

[Eli Tovbeyn]

Title: Message

I also thought about this idea. Another option could be ConfinueWhileAccept policy that combines authby NT and authby FILE.

I just though maybe someone has realy nice idea how to avoid managing users in two places.

 

________________________________________ 
Eli Tovbeyn                               [EMAIL PROTECTED]

-----Original Message----- 
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 19 February, 2003 08:17
To: Eli Tovbeyn
Cc: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) AuthBy NT & returning IP address

Hello Eli -

One way of doing this is with cascaded AuthBy clauses, like this:

# define AuthBy clauses

<AuthBy FILE>

Identifier CheckUsers

Filename %D/users

</AuthBy>

<AuthBy NT>

Identifier CheckNT

.....

</AuthBy>

# define Realms or Handlers

<Realm ....>

AuthBy CheckUsers

.....

</Realm>

The "users" file would contain something like this:

# users file

someuser Auth-Type = CheckNT

Framed-IP-Address = n.n.n.n

anotheruser Auth-Type = CheckNT

Framed-IP-Address = m.m.m.m

.....

You will need to maintain your users in two places however.

regards

Hugh

On Tuesday, Feb 18, 2003, at 23:57 Australia/Melbourne, Eli Tovbeyn wrote:

Hi,

I'm looking for nice solution for working with AuthBy NT and returning static IP address to every client.

I'm working with Radiator 3.5.

Any ideas are welcome.

________________________________________ 

Eli Tovbeyn                               [EMAIL PROTECTED]

--

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.