Hi there,


I would like to implement black listing  caller ids which have known to have
been used to hack into SYstems or into ISP accounts.


Of course, I also need to know how to get the value of the
Calling-Station-Id inside the PreAuthHook Code so that I could make a check
if the caller id is black listed.  If it is, Radiator will deny access.

A pseudo code of what I want  to implement is written below:
a) Get value of Calling Station Id
b) Search Black List Table for that caller id
c) If caller id is black listed, then deny access


Hoping for any support from all Radiator Guru  out there..=)

Egie

---
Edgar R Gutierrez
NOC- Network Services Manager
Impact Information Systems

----- Original Message -----
From: Hugh Irvine <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; Randy Cosby <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Saturday, May 13, 2000 8:59 AM
Subject: RE: (RADIATOR) Merged ISP's


>
> Hi Randy -
>
> On Sat, 13 May 2000, Randy Cosby wrote:
> > How do I BEST deal with the fall-through to the next
> > radius if the first fails?
> >
>
> You would specify multiple Host parameters in the AuthBy RADIUS clauses.
>
> Have a look at section 6.25.1 in the Radiator 2.15 reference manual.
>
> regards
>
> Hugh
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
>
>
>
> ===
> 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.
>
>


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