On Tue, 09 Nov 1999, mike wrote:
> Hi,
> I just started using radiator within the past 2 months and it runs great,
> well most of the time, that is. I have found a problem cropping up
> occasionally that I am not sure how to resolve. I do quite a bit of
> proxying and when one of my customers has a problem with their radius
> server it feeds back to local authentication on my radius servers and some
> of my own users randomly cannot login. The error message I get in the
> logs is
> Mon Nov 8 08:06:14 1999: INFO: AuthRADIUS: No reply after 3 retransmissions
> Now the load average on my server is less that .50. Why would proxying
> failures cause my local users to not authenticate correctly? As soon as
> the other server is fixed or reachable those users can authenticate and
> mine can also reliably. I am using Radiator 2.14.1 and MySQL to
> authenticate my local users and it works flawlessly unless one of my
> proxying customers is having a problem.
>
> I have the following config for each of my proxying customers:
> <Realm realm name>
> <AuthBy RADIUS>
> Fork
> Host first radius server
> Host second radius server
> Secret secret
> AuthPort 1645
> </AuthBy>
> </Realm>
>
> I am going to try shortening timeouts in my config by adding
> Retries 2
> RetryTimeout 3
>
I think I will need to see your complete configuration file (no secrets).
And I tend to agree with your comment above, as it is probably the PC dialup
client timeout or possibly NAS radius timeout causing the problem.
thanks
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.
