User-accounts do not expire in time...
Hi all! 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. This requires 2 entries in radgroupcheck, right? Based on http://wiki.freeradius.org/Rlm_sqlcounter I think both Max-All-Session & Max-Daily-Session need to be 86400 if I'm not mistaken? I have in radgroupcheck: 24hours Max-Daily-Session := 86400 24hours Max-All-Session := 86400 however, a user who is a member of the 24hours group is able to log on longer than the 24hours period: Mon Nov 19 13:15:35 2007 : Auth: Login OK: [ofjyc5] (from client stline port 2151678956 cli 30:13:02:31:68:B9) Mon Nov 19 13:28:00 2007 : Auth: Login OK: [ofjyc5] (from client stline port 2151678959 cli 30:13:02:31:68:B9) Tue Nov 20 09:11:04 2007 : Auth: Login OK: [ofjyc5] (from client stline port 2151678995 cli 00:19:D2:29:F9:D5) Tue Nov 20 15:04:31 2007 : Auth: Login OK: [ofjyc5] (from client stline port 2151679001 cli 00:19:D2:29:F9:D5) Wed Nov 21 07:21:19 2007 : Auth: Login OK: [ofjyc5] (from client stline port 2151679009 cli 00:19:D2:29:F9:D5) /etc/raddb/sqlcounter.conf is a copy from http://wiki.freeradius.org/Rlm_sqlcounter What am I doing wrong here...? Regards, Evert
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 receiving accounting packets? The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc. The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for. Alan DeKok.
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 period:
Is the server receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for.
Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not? How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'. (I'll have to check on the accounting packets. Not sure about them) Regards, Evert
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 <evert@poboxes.info> 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 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for.
Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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 <evert@poboxes.info> 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 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for.
Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for.
Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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 tries to log in again...? Am I wrong there? Regards, Evert liran tal wrote:
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
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) and check these issues with a sniffer maybe to be sure. Regards, Liran. On Nov 21, 2007 3:14 PM, Evert <evert@poboxes.info> wrote:
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 tries to log in again...? Am I wrong there?
Regards, Evert
liran tal wrote:
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 > 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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-hour period has passed. The server runs version 1.1.6 of FreeRADIUS ;-) Regards, Evert liran tal wrote:
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) and check these issues with a sniffer maybe to be sure.
Regards, Liran.
On Nov 21, 2007 3:14 PM, Evert <evert@poboxes.info> wrote:
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 tries to log in again...? Am I wrong there?
Regards, Evert
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 >> 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 receiving accounting packets? > > The fact that a user received an Access-Accept doesn't mean they > succeeded in logging in. The NAS may have rebooted, they may have hung > up, the Access-Accept could have been lost, etc. > > The server knows (and accounts for) the user logging in only when it > receives an Accounting-Request packet. The accounting packets are also > used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
liran tal wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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" <evert@poboxes.info> piše:
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-hour period has passed.
The server runs version 1.1.6 of FreeRADIUS ;-)
Regards, Evert
liran tal wrote:
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) and check these issues with a sniffer maybe to be sure.
Regards, Liran.
On Nov 21, 2007 3:14 PM, Evert <evert@poboxes.info> wrote:
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 tries to log in again...? Am I wrong there?
Regards, Evert
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 >>> 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 receiving accounting packets? >> >> The fact that a user received an Access-Accept doesn't mean they >> succeeded in logging in. The NAS may have rebooted, they may have hung >> up, the Access-Accept could have been lost, etc. >> >> The server knows (and accounts for) the user logging in only when it >> receives an Accounting-Request packet. The accounting packets are also >> used to determine how long the user was logged in for. > Provided both the server and the NAS have not rebooted in the mean time, shouldn't the > server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, > accounting packets or not? > > How long the user has been logged on in the 24-hour period is not really relevant in my > case. 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'. > > > > (I'll have to check on the accounting packets. Not sure about them) > > > Regards, > Evert >
liran tal wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/usershtml
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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 their 1st logon." Exact solution: Run a logon script that adds Expiration attribute set 24 hours from now() if one does not exist in users profile. Ivan Kalik Kalik Informatika ISP Dana 21/11/2007, "Evert" <evert@poboxes.info> piše:
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 tries to log in again...? Am I wrong there?
Regards, Evert
liran tal wrote:
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 > 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 receiving accounting packets?
The fact that a user received an Access-Accept doesn't mean they succeeded in logging in. The NAS may have rebooted, they may have hung up, the Access-Accept could have been lost, etc.
The server knows (and accounts for) the user logging in only when it receives an Accounting-Request packet. The accounting packets are also used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
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 thought you will see Evert that it's suffice to simply utilize the Max-Daily-Session attribute only. The Max-Daily-Session attribute combined with the reset = never option is what you are looking for. This is because you want to allow the user to have access only 1day after he's initial login (remember 24h = 1 day, although I'm not sure if 1day wraps after 24h or after midnight of the next day). Hopefully this extra information will prove useful whatever method you choose to implement your restrictions. Regards, Liran. On Nov 21, 2007 3:40 PM, <tnt@kalik.co.yu> 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.
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 their 1st logon."
Exact solution: Run a logon script that adds Expiration attribute set 24 hours from now() if one does not exist in users profile.
Ivan Kalik Kalik Informatika ISP
Dana 21/11/2007, "Evert" <evert@poboxes.info> piše:
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 tries to log in again...? Am I wrong there?
Regards, Evert
liran tal wrote:
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 >> 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 receiving accounting packets? > > The fact that a user received an Access-Accept doesn't mean they > succeeded in logging in. The NAS may have rebooted, they may have hung > up, the Access-Accept could have been lost, etc. > > The server knows (and accounts for) the user logging in only when it > receives an Accounting-Request packet. The accounting packets are also > used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thanks! :-) I will implement your solution as soon as my schedule allows me. :-) Regards, Evert tnt@kalik.co.yu 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.
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 their 1st logon."
Exact solution: Run a logon script that adds Expiration attribute set 24 hours from now() if one does not exist in users profile.
Ivan Kalik Kalik Informatika ISP
Dana 21/11/2007, "Evert" <evert@poboxes.info> piše:
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 tries to log in again...? Am I wrong there?
Regards, Evert
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 <evert@poboxes.info> wrote:
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 <evert@poboxes.info> 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 >> 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 receiving accounting packets? > > The fact that a user received an Access-Accept doesn't mean they > succeeded in logging in. The NAS may have rebooted, they may have hung > up, the Access-Accept could have been lost, etc. > > The server knows (and accounts for) the user logging in only when it > receives an Accounting-Request packet. The accounting packets are also > used to determine how long the user was logged in for. Provided both the server and the NAS have not rebooted in the mean time, shouldn't the server send a 'Maximum never usage time reached', based on the rules in sqlcounter.conf, accounting packets or not?
How long the user has been logged on in the 24-hour period is not really relevant in my case. 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'.
(I'll have to check on the accounting packets. Not sure about them)
Regards, Evert
liran tal wrote: - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (4)
-
Alan DeKok -
Evert -
liran tal -
tnt＠kalik.co.yu