Hello Wes -

On Tuesday 09 January 2001 09:00, Wes wrote:
> Hello,
>
> The company I work for has two separate ISPs. My problem is that any user
> from either ISP can dial into any NAS that either ISP has.  This works
> well except for the customers who share a common username with someone on
> the other ISP.  All of our Authentication/Accounting/SessionDatabase is
> going to be done on a single radius/mysql server.  Up until now, we have
> just been adding a "Simultaneous-Use=2" to the check items on the
> duplicate users, and not really been worrying too much about the
> accounting mess it creates.  The only difference between ISP1's users and
> ISP2's users is the password.  Currently I just have "ContinueUntilAccept"
> in my <Handler> clause and this authenticates the user just fine, but it
> stores all the accounting and sessiondatabase information in the first
> AuthBy clause no matter what.  Is there any way to get the information to
> go into different tables depending on which user table they get
> authenticated to?  By the way, I am running Radiator 2.17.1 on RedHat
> Linux, with MySql tables for Authentication/Accounting/SessionDatabase (2
> sets of each, one for each ISP).
>

In each AuthBy clause you should use an AddToReply, like this:

# AuthBy for ISP1

<AuthBy SQL>
        Identifier ISP1
        DBSource ....
        DBUsername ....
        DBAuth ....
        .....
        AddToReply Class = ISP1
</AuthBy>

# AuthBy for ISP2

<AuthBy SQL>
        Identifier ISP2
        DBSource ....
        DBUsername ....
        DBAuth ....
        .....
        AddToReply Class = ISP2
</AuthBy>

# configure Handlers for accounting 

<Handler Request-Type = Accounting-Request, Class = ISP1>
        AuthBy ISP1
</Handler>

<Handler Request-Type = Accounting-Request, Class = ISP2>
        AuthBy ISP2
</Handler>

# configure Handler for authentication

<Handler>
        AuthByPolicy ContinueUntilAccept
        AuthBy ISP1
        AuthBy ISP2
</Handler>

hth

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