Hello Christopher -
On Wed, 09 Feb 2000, Christopher J. Carlson wrote:
> We have been using Radiator for about 3 weeks now, with great success.
> One small problem that we have seen is that one of our MAX's tends to send
> authinticating packets for itself every now and then. Normally, we
> only see this type of behavior when we switch the MAX from tacacs, a bunch
> of auth requests that fail, and then it behaves like normal.
>
> I can't figure out for the life of me why it keeps doing this. Has
> anyone had any similar problems with Ascend's?
>
> Error is as stated:
>
> Access rejected for pools-MAX01-<townname>: No such user
>
The MAX's have an optional software feature that can be configured to request
additional configuration information from radius. You can turn this behaviour
off in the MAX. This has been discussed on the list before, so have a look at:
http://www.thesite.com.au/~radiator
and do a search.
Alternatively you can define bogus users corresponding to these requests and
simply reject them (or set up a special Handler based on some common attribute
in the requests and reject them there).
hth
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.
