wether setting
an Expiration attribute in radcheck normally implies a Session-Timeout
to be added to the access-accept messages, or not.
Yes.
If it doesn't work in SQL, try it in the users file.
Thank you for answer. I tried with the users file and got the same
behavior as with
with freeradius-0.9.3, mysql-4.1.1 and Patton 2996 RAS.
Kindly help.
goksie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alan DeKok
Sent: Thursday, March 31, 2005 6:50 PM
To: freeradius-users@lists.freeradius.org
Subject: Re: Session-Timeout not set
Hi again,
I'm sorry to post twice but as I'm not an english person I was
wondering wether what I asked was really clear. I'm not looking for a
complicated solution of any kind, but I'd like to know wether setting
an Expiration attribute in radcheck normally implies a Session-Timeout
to be added
Joachim Bloche [EMAIL PROTECTED] wrote:
I'm sorry to post twice but as I'm not an english person I was
wondering wether what I asked was really clear. I'm not looking for a
complicated solution of any kind, but I'd like to know wether setting
an Expiration attribute in radcheck normally
When a user logs in 23 hours and 59 minutes after the first
connection, I expected freeradius to return the Session-Timeout
attribute in the access-accept (with value 60).
Actually it does not, so the user can stay connected well after the 24
hours limit.
So... what does the
Joachim Bloche [EMAIL PROTECTED] wrote:
When a user logs in 23 hours and 59 minutes after the first
connection, I expected freeradius to return the Session-Timeout
attribute in the access-accept (with value 60).
Actually it does not, so the user can stay connected well after the 24
hours
6 matches
Mail list logo
