Thanks! :-)
I will implement your solution as soon as my schedule allows me. :-)
Regards,
Evert
[EMAIL PROTECTED] wrote:
> No, that's not what you have set up. If user uses several sessions he
> will be able to use up 24 hours of online time over several
> days/weeks/months/years.
>
That's not how counters work. Daily counter will count usage during that
day. Next day it starts from 0. It doesn't care what happened the day
before. If you want an account to expire after a set period of time use
Expiration attribute.
Ivan Kalik
Kalik Informatika iSP
Dana 21/11/2007, "Evert" <
I've been checking radacct, and there is a record there for every 'Login OK'.
Isn't the
oldest of those used to figure out when 24 hours have passed?
IMHO the type of NAS and/or sniffing for stuff is not relevant here. It's the
RADIUS
server which keeps on giving 'Login OK' even after the 24-hou
True, it managed to confuse me, but re-reading Evert second
post "All I need is that when the user tries to log in again > 24
hours after 1st logon
(based on AcctStartTime) he gets a 'Maximum never usage time reached'."
- Ivan's solution is on the spot.
Though if we give this a little bit more tho
No, that's not what you have set up. If user uses several sessions he
will be able to use up 24 hours of online time over several
days/weeks/months/years.
Your requirement: "I have users in my system who are supposed to be able
to logon as much as they want, in a period of 24 hours starting from
If your NAS is not sending any accounting packets to the server on the usage
for a user how should freeradius know to increment it's counter for
the attribute?
So how about you eliminate all of the possible obvious errors by
telling us which
NAS is it (someone here might have had the same problem)
>From this location I have no direct access to the NAS in question at the
>moment, so that
will have to wait a bit.
But what about my comment that the user should not get a 'Login OK' but a
'Invalid user
(rlm_sqlcounter: Maximum never usage time reached)' as soon as 24 hours have
passed and he
How about checking Alan's comment on whether your NAS
is actually sending accounting information or not?
Regards,
Liran.
On Nov 21, 2007 2:12 PM, Evert <[EMAIL PROTECTED]> wrote:
> There is indeed a record in the usergroup-table with
> UserName= ofjyc5
> GroupName= 24hours
>
> ;-)
>
>
> Regards
There is indeed a record in the usergroup-table with
UserName= ofjyc5
GroupName= 24hours
;-)
Regards,
Evert
liran tal wrote:
> Hopefully you didn't forget to set the user-group mapping in usergroup
> table, right?
>
>
> Regards,
> Liran.
>
> On Nov 21, 2007 1:01 PM, Evert <[EMAIL
Hopefully you didn't forget to set the user-group mapping in usergroup
table, right?
Regards,
Liran.
On Nov 21, 2007 1:01 PM, Evert <[EMAIL PROTECTED]> wrote:
> Alan DeKok wrote:
> > Evert wrote:
> >> I have users in my system who are supposed to be able to logon as much as
> >> they want, in a
Alan DeKok wrote:
> Evert wrote:
>> I have users in my system who are supposed to be able to logon as much as
>> they want, in a
>> period of 24 hours starting from their 1st logon.
> ...
>> however, a user who is a member of the 24hours group is able to log on
>> longer than the
>> 24hours peri
Evert wrote:
> I have users in my system who are supposed to be able to logon as much as
> they want, in a
> period of 24 hours starting from their 1st logon.
...
> however, a user who is a member of the 24hours group is able to log on longer
> than the
> 24hours period:
Is the server receivi
Quoting Jaco van Tonder <[EMAIL PROTECTED]>:
> The Expiration module does exactly what you require. It also calculates the
> correct session timeout and it is fine grained it uses the format
> "Expiration := 01 Sep 2005 12:00:00" in the radcheck table. What version of
> freeradius are you using? I
The Expiration module does exactly what you require. It also calculates the
correct session timeout and it is fine grained it uses the format
"Expiration := 01 Sep 2005 12:00:00" in the radcheck table. What version of
freeradius are you using? In older versions the granularity of the time was
limit
> Hi,
>
> I am a newbie when it comes to radius. I need more security, eg: setting up
> vpns for each authenticated groups. How do we set it up. The reason is , that
> each group gets the same iprange, and then they can get into each others
> personal files. Please Help
>
>
> Regards
> Zaine
>
Sin
login at again.
Thank You
- Original Message -
From: "EROS" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 20, 2005 1:35 PM
Subject: RE : User accounts
Try the login-time check attribute
You should find a little description in the user_edit.php3 of dialu
Try the login-time check attribute
You should find a little description in the user_edit.php3 of dialup
admin, I think.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de
Samareanu Florin
Envoyé : jeudi 20 janvier 2005 12:24
À : freeradius-users@lists.f
17 matches
Mail list logo
