Hello Richard -

On Fri, 18 Feb 2000, Richard Andrews wrote:
> Hi,
> 
> We are receiving a substantial amount of errors relating to delays and 
> retransmittions, below are two examples:
> 
> RADIUS authentication failed for "auser" on J1.31 Message: Cannot open 
> RADIUS session (no authentication response)
> Fri Feb 18 11:57:45 2000: INFO: Duplicate request id 92 received from 
> 1.2.3.4: ignored
> 
> The main Tigris NAS is connected via an uncongested 100Mb Switch to the 
> Radiator server, so we can assume that network failures are pretty 
> unlikely.  The PC the radius server is on is only running 1 instance of 
> Radiator and ssh to copy and unzip the configs from another machine.  The 
> PC is Pentium1 233 with 192Mb RAM and running FreeBSD 3.2-RELEASE.  We use 
> flat files for passwords and log files and we currently don't use radius 
> proxying.
> 
> We currently have the authentication retry interval set to 10 seconds and 
> the retry count set to 3.
> The accounting retry interval is set to 40 seconds and the retry count set 
> to 10.
> 
> What would be the optimum retry interval and count?  What should we look at 
> in more detail to prevent these types of problems?
> 
> We are also getting a duplicate stop entries.  The entries concerned have 
> the same session ids, and different accounting delay times.  I have noticed 
> that the duplicate entries are exactly the 40sec apart, which is the 
> retransmittion time set on our NAS'.  We can change the timeout to 1-60 
> seconds.  Do you have any recommendations, or is the only solution to 
> filter these out in our accounting DB?
> 

Please send me a copy of your configuration file (no secrets) and a trace 4
debug listing showing what is happening.

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.

Reply via email to