...
DELETE FROM radius.usergroup WHERE GroupName = 'aroma'
THEN...
INSERT INTO radius.usergroup (UserName, CreationDate, GroupName)
VALUES ('username0001', (CURRENT_DATE), 'aroma');
repeated for all 500 usernames...
I think this should work, as all the usernames in use are stored in
Andrew Long [EMAIL PROTECTED] wrote:
I tried Session-Timeout but it doesn't seem to do the job.
So... is it being sent back to the NAS? If it is, then the NAS is
ignoring it. Go ask your NAS manufacturer for a refund, or for a
firmware upgrade that implements RADIUS.
Alan DeKok.
Sent: Donnerstag, 09. November 2006 14:51
To: Alan DeKok; FreeRadius users mailing list
Subject: Re[5]: limiting sessions
Andrew Long [EMAIL PROTECTED] wrote:
I tried Session-Timeout but it doesn't seem to do the job.
So... is it being sent back to the NAS? If it is, then the NAS
Andrew Long [EMAIL PROTECTED] wrote:
How would you suggest I verify the session-timeout is actually being
sent/received?
tcpdump / wireshark?
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
-
List
Andrew Long [EMAIL PROTECTED] wrote:
I tried Session-Timeout but it doesn't seem to do the job.
So... is it being sent back to the NAS? If it is, then the NAS is
ignoring it. Go ask your NAS manufacturer for a refund, or for a
firmware upgrade that implements RADIUS.
Alan DeKok.
On Thursday 09 November 2006 11:00, Andrew Long wrote:
Here is the output from radiusd -X regarding the answer to an
auth-request from one of the properties where I changed
session-timeout to 1800. It does not look to me like the
session-timeout attribute is being sent... any suggestions?
On Thursday 09 November 2006 11:00, Andrew Long wrote:
Here is the output from radiusd -X regarding the answer to an
auth-request from one of the properties where I changed
session-timeout to 1800. It does not look to me like the
session-timeout attribute is being sent... any suggestions?
* Try to respond just to the list and not me personally. I don't enjoy wading
through duplicate messages. Thanks!
On Thursday 09 November 2006 11:34, Andrew Long wrote:
also ran
SELECT
`usergroup`.`UserName`,
`usergroup`.`creationdate`,
`usergroup`.`GroupName`
from usergroup
where
On Thursday 09 November 2006 11:34, Andrew Long wrote:
also ran
SELECT
`usergroup`.`UserName`,
`usergroup`.`creationdate`,
`usergroup`.`GroupName`
from usergroup
where username = '4aroma70370';
and that also comes up null...
Does it make sense that radius is not recognizing the
Andrew Long [EMAIL PROTECTED] wrote:
I need to boot users at one property after a specified time period.
We have adjusted the max-daily-session to 1800 (30 minutes),
but users still seem to be staying on. Can someone point me in the
right direction. The NAS is a Colubris cn3000.
Why use
Andrew Long [EMAIL PROTECTED] wrote:
I tried Session-Timeout but it doesn't seem to do the job.
So... is it being sent back to the NAS? If it is, then the NAS is
ignoring it. Go ask your NAS manufacturer for a refund, or for a
firmware upgrade that implements RADIUS.
Alan DeKok.
--
I need to boot users at one property after a specified time period.
We have adjusted the max-daily-session to 1800 (30 minutes),
but users still seem to be staying on. Can someone point me in the
right direction. The NAS is a Colubris cn3000.
The other attribute we have that may apply is
Andrew Long [EMAIL PROTECTED] wrote:
I need to boot users at one property after a specified time period.
We have adjusted the max-daily-session to 1800 (30 minutes),
but users still seem to be staying on. Can someone point me in the
right direction. The NAS is a Colubris cn3000.
Why use
that may apply is max-acct-age. I am
pretty new to this, so any detail is most appreciated.
The NAS should support Session-Timeout, which is the most common method
of time-limiting sessions. If not, hit the vendor with a big cluebat,
as it's in the RFC.
--
James Wakefield,
Unix Administrator
Andrew Long [EMAIL PROTECTED] wrote:
I need to boot users at one property after a specified time period.
We have adjusted the max-daily-session to 1800 (30 minutes),
but users still seem to be staying on. Can someone point me in the
right direction. The NAS is a Colubris cn3000.
Why use
15 matches
Mail list logo
