Hello Vicente -
This is one of the problems with strict session limit checking - if
you lose connectivity with the NAS(s) you have a problem. The best
way to deal with this is to configure a backup radius server in your
NAS(s) and run a second copy of Radiator as the backup without strict
checking.
hth
Hugh
At 8:00 +0000 28/8/00, Vicente Ferrando Berenguer wrote:
> Hello every body,
>
> We are using NasType AscendSNMP in our radiator.cfg. Last week some
>NASes lost connectivity with aur Radiator, some but not all of them. And
>that caused Radiator was unable to authenticate users. Even, users that
>were trying to connect on NASes that responded to SNMP queries were rejected.
>
> My question is: Is there any way to make Radiator keep on working when
>one or more NASes, listed as clients in the radiator.cfg, does not respond?.
>
> Thanks in advance and kind regards.
>--
>--
>Vicente Ferrando / [EMAIL PROTECTED]
>Wanadoo Espa�a
>Explotaci�n Red de Sistemas
>Tel :+34 96 5040000 Ext. 44718 - Fax: +34 96 5040047
>http://www.wanadoo.es
>---
>
>
>===
>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.
--
--
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.
