(RADIATOR) multi check

[Hugh Irvine]

Hello Herman -

You can do the first part with a Calling-Station-Id check item, and you 
can do the second part with an SQL session database and an AuthBy 
PORTLIMITCHECK clause in addition to your normal AuthBy.

regards

Hugh


On 16 Mar 2004, at 20:32, Herman verschooten wrote:

> Hi,
>  
> I am looking for a way to do a double authentication on some of our 
> users.
>  
> I want them to be checked on callerid first and then on username, if 
> not already rejected.  Anyone done this?
>  
> Situation:
>  
> User A has callerId 1 attached in the DB.
> User B has no callerId attached in the DB.
>  
> * User A calls in with callerID 1 : Accept
> * User A calls in with callerID 2 : Reject
> * User B calls in with callerID 1 : Reject
> * User B calls in with callerID x : Accept
>  
>  
> Tx,
>  
> Herman verschooten
>  
>  
> WebVisie bvba
> Een klare kijk op interne en externe communicatie
> _______________________________________________
> Oudaan 15 / 33        2000 Antwerpen       http://www.webvisie.net
> tel 03/206.72.70       fax 
> 03/234.93.82      h.verschooten at webvisie.net  
>   
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

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