Hello -
At 15:57 -0800 01/1/24, System Administrator wrote:
>We're having a problem getting Radiator to deal effectively with
>primary and secondary radius clients.
>we have the following entry in the radius.cfg file.
>
><Realm realm.net>
> AuthByPolicy ContinueAlways
> AuthBy xxxAcct
> <AuthBy RADIUS>
>
> Host 20.20.20.1
> Host 30.30.30.1
> Secret abcdefgh
> </AuthBy>
></Realm>
>
> We expect that when 20.20 is not available, Radiator will seek
>30.30 for authorization. that is indeed what happens, Radiator
>sends the authorization request to the secondary server; the
>secondary server approves the request and response was OK; but
>Radiator refuses to recognize the response and authorize the user.
>If we reverse the order of the primary and secondary server, then
>Radiator sends the request to 30.30, receives the Acknowledgment
>and authorizes the user..
>what we cannot figure is out to get Radiator to approve the request
>which is sent to the secondary when the primary is unavailable.
>we would be delighted to hear from someone who has solve this
>problem or who is successfully authorizing to primary and secondary
>clients
Could you send me a trace 4 showing what happens in both cases?
thanks
Hugh
--
NB: I am travelling this week, so there may be delays in our correspondence.
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.
