Hi Gary -
On Thu, 28 Oct 1999, Gary wrote:
> No joy Hugh...
> Our setup is basic... can you see the problem ?
>
> I test ring in from the office with a proper setup in the normal users
> file, and it does not act on the rejectusers, and continues to
> authenticate on the normal users file.
>
>
> ----------------------------------
> Trace 3
>
> DbDir /usr/local/raddb/
>
> LogFile /var/log/radius/%Y%mradiator.log
>
> AuthPort 1645
>
> AcctPort 1646
>
> include /usr/local/raddb/clients
>
> # You will probably want to change this to suit your site.
> <Realm DEFAULT>
> AuthByPolicy ContinueWhileAccept
> <AuthBy FILE>
> AcceptIfMissing
> Filename /usr/local/raddb/rejectusers
> Nocache
> </AuthBy>
> <AuthBy FILE>
> Filename /usr/local/raddb/users
> Nocache
> </AuthBy>
> AcctLogFileName /var/log/radius/%Y%mdetail.log
> PasswordLogFileName /var/log/radius/%Y%mpassword.log
> </Realm>
>
Try running Radiator at Trace level 4 and have a look at the Access-Request
packets coming in. Do they have Calling-Station-Id present in the packet? And
if so, is your rejectusers file set up to match correctly? If you send me both
the debug trace and the rejectusers file, I'll have a look.
cheers
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
