Hello Ferhat -
On Tue, 07 Dec 1999, Ferhat DILMAN wrote:
> >%_Hi,
>
> I have tested Session-Timeout="until 1800" parameter and does not work.
>
Thanks for pointing this out - as it happens, a user reply item of
Session-Timeout="until 1800"
does in fact work. However, due to an oversight, it doesn't work in an
AddToReply. Our apologies for this and Mike will post a fix shortly.
> The config is: Ascend TNT, Radiator 2.14.1 with new AuthGeneric.pm module on
> Debian Linux and here is the user file and the config file and the logfile.
>
> I have radiator main server and i have created a proxy. Main server sends
> the requests to this server. By the way, main server is still in 2.13
> version. Does it matter?
>
> Anybody tested this new parameter?
>
> P.S. I have added the Ascend attribute into the dictionary:
> ATTRIBUTE Session-Timeout 27 integer
>
You mention in your other email that Ascend uses
ATTRIBUTE Ascend-Maximum-Time 194 integer
does this mean that Ascends do not honour the standard Session-Timeout?
You might also check what version on Ascend software you are running and
whether other versions behave differently?
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.
