Hello Lisa -
This message is related to what I described in my other mail, and is due to a
reply being received *after* a timeout has occured, and the timeout entry has
already been removed from the list.
Have a look at the code in AuthRADIUS.pm -
sub handleReply
{
.....
regards
Hugh
On Wednesday 06 June 2001 00:05, Lisa Goulet wrote:
> Hi,
>
> I'm running Radiator 2.18.1.
>
> The radiator is proxying to a customer radius server(also radiator). I've
> seen several error messages in the log file after receiving an
> Accounting-Response from the customer radius server. The number of
> occurences of these errors seems proportional to the number of "Timed out,
> retransmitting" errors to this server.
>
> The message is as follows:
>
>
> Mon Jun 4 13:00:53 2001: DEBUG: Received reply in AuthRADIUS for req 172
> from xx.xx.xx.xx:1646
> Mon Jun 4 13:00:53 2001: ERR: Timeout ARRAY(0x8d532e8) was not in the
> timeout list
> Mon Jun 4 13:00:53 2001: WARNING: Bad authenticator received in reply to
> ID 172
>
>
> Thanks in advance,
> Lisa
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
