radacct MySQL table only gets filled with the last session values for a given user ( no history logging )
Client : Windows 10 NAS : Cisco SB WAP121 RADIUS Server : Debian 8 / FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu, Authentication : PEAP/MSCHAPv2 While the /varl/log/freeradius/radacct/192.168.1.2/detail-20160324 files gets filled with correct data values for each user session : sudo cat /var/log/freeradius/radacct/192.168.1.2/detail-20160324 | grep Acct-Input-Octets Acct-Input-Octets = 43976 Acct-Input-Octets = 845 Acct-Input-Octets = 394240 Acct-Input-Octets = 371260 Acct-Input-Octets = 24927 the radacct MySQL table only gets filled with the last session values for a given user ( 24927 here ). There is no history logging : mysql> select radacct.username, radacct.nasipaddress, radacct.acctstarttime, radacct.acctstoptime, radacct.acctinputoctets, radacct.acctoutputoctets from radacct; +-----------+---------------+---------------------+---------------------+-----------------+------------------+ | username | nasipaddress | acctstarttime | acctstoptime | acctinputoctets | acctoutputoctets | +-----------+---------------+---------------------+---------------------+-----------------+------------------+ | User1 | 192.168.1.2 | 2016-03-24 08:44:46 | 2016-03-24 08:44:23 | 24927 | 20814 | | User2 | 192.168.1.2 | 2016-03-24 08:40:33 | 2016-03-24 08:42:22 | 0 | 0 | +-----------+---------------+---------------------+---------------------+-----------------+------------------+ 2 rows in set (0.00 sec) 2 rows in set (0.00 sec) Is this the normal expected behaviour ? I highy doubt it. I must have done something wrong, but I'm using a very standard Freeradius/MySQL install. Any help would be greatly appreciated :-) --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
I Up my question, before giving-up the case :-) On Mar 24, 2016 2:14 PM, "oatech" <oatech7402@gmail.com> wrote:
Client : Windows 10 NAS : Cisco SB WAP121 RADIUS Server : Debian 8 / FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu, Authentication : PEAP/MSCHAPv2
While the /varl/log/freeradius/radacct/192.168.1.2/detail-20160324 files gets filled with correct data values for each user session :
sudo cat /var/log/freeradius/radacct/192.168.1.2/detail-20160324 | grep Acct-Input-Octets
Acct-Input-Octets = 43976 Acct-Input-Octets = 845 Acct-Input-Octets = 394240 Acct-Input-Octets = 371260 Acct-Input-Octets = 24927
the radacct MySQL table only gets filled with the last session values for a given user ( 24927 here ). There is no history logging :
mysql> select radacct.username, radacct.nasipaddress, radacct.acctstarttime, radacct.acctstoptime, radacct.acctinputoctets, radacct.acctoutputoctets from radacct;
+-----------+---------------+---------------------+---------------------+-----------------+------------------+ | username | nasipaddress | acctstarttime | acctstoptime | acctinputoctets | acctoutputoctets |
+-----------+---------------+---------------------+---------------------+-----------------+------------------+ | User1 | 192.168.1.2 | 2016-03-24 08:44:46 | 2016-03-24 08:44:23 | 24927 | 20814 | | User2 | 192.168.1.2 | 2016-03-24 08:40:33 | 2016-03-24 08:42:22 | 0 | 0 |
+-----------+---------------+---------------------+---------------------+-----------------+------------------+ 2 rows in set (0.00 sec)
2 rows in set (0.00 sec)
Is this the normal expected behaviour ? I highy doubt it. I must have done something wrong, but I'm using a very standard Freeradius/MySQL install.
Any help would be greatly appreciated :-)
--- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
On Apr 16, 2016, at 4:49 AM, olivier a <oatech7402@gmail.com> wrote:
I Up my question, before giving-up the case :-)
FreeRADIUS is only as good as the data it gets. If the NAS sends the SAME information for all sessions, the data will use the same row(s) in SQL. For the sessions to be in different rows, the NAS has to send information which is *unique* for each session. e.g. Acct-Session-Id. And as always, run the server in debug mode to see what's going on. Alan DeKok.
participants (3)
-
Alan DeKok -
oatech -
olivier a