Hi Mike,
All of my users are in the Radmin Database. The MAXIDLETIME is currently set
to 40 (I'll change it to 2400 shortly). The users who are logging in with an
Idle-Timeout of 2400 are failing their Radmin DB authentication and are
picking up their Timeout from the Users file and authenticating from the
Shadow password file (This is a seperate issue that I havent bothered sorting
out yet, users with a correct Radmin Password, who always authenticate from
the shadow password file).
I'll send my radius.cfg file to you again. Could you think of some way of
debugging why the MAXIDLETIME field in the Radmin DB is not getting set into
the Idle-Timeout attribute?
Regards. Paul
Mike McCauley wrote:
> Ive had a look at the log, but Im not sure whichg user is the one demonstrating
> the problem? I can see one access accept for "altrex" with a Session-Timeout of
> 2400. But I didnt see any with Idle-Timeout of 0 ?
>
> The only reason I can think of for not putting the idle timeout in the reply
> is that the IDLETIMEOUT column for that user is null. Can you confirm that?
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
