Debian 8 prevents the NAS to generate data volume accounting
Something strange is happening : While the Windows 10 client does have a valid accounting stop message generated, with proper data accounting values ( Acct-Input-Packets, Acct-Output-Packets, Acct-Input-Octets, Acct-Output-Octets), the Debian 8 client always have 0 in each of these fields. Ex : 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 = 0 Acct-Input-Octets = 371260 Acct-Input-Octets = 0 ( Here, Windows 10 gets proper values recorded, Debian 8 always gets 0 ) Does anybody understand what may cause Debian 8 to prevent data accounting ? I'm using a very standard Freeradius/MySQL setup ... Clients : Windows 10 / Debian 8 NAS : Cisco SB WAP121 RADIUS Server : Debian 8 / FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu, Authentication : PEAP/MSCHAPv2 --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
Its the NAS that sends the data to the RADIUS server, not the client , so you need to look at debug logs (on the NAS and on the server) to get an idea of why that value is 0 alan
Thank you for your answer. Sure, the client is not/should not be able to interfere with the NAS/FreeRADIUS accounting job. Yet, something is triggering this strange behavior. And it is triggered by the client .... The NAS/FreeRADIUS is so basic/classic/simple/straightforward I can’t see what may be happening ... Here is what I have so far : . Changing the wifi dongle suppresses the problem. So it’s not an OS issue. . The NAS is sending 0 accounting values ( checked in FreeRADIUS logs/wireshark). FreeRADIUS is not mis-undestanding the NAS messages. Debian8 is not the cause. I tried changing its Wifi dongle, and that did fix the problem. So it’s the Wifi dongle that’s the remote cause of this problem. The NAS debug logs doesn’t bring any clue : It’s a 100€/$ Wifi AP, and turning the logging level to debug only outputs 8 lines for a whole conect/disconect cycle. This does not bring any significant clue. As about FreeRADIUS log, they’re too rich for me to be able to understand them. The only sure thing is that the NAS is sending accounting values=0. FreeRADIUS is not mis-interpreting the values sent by the NAS. It’s the NAS that is sending zero values. Althought the problem is fixed/dodged, I’d really wish I could understand what may be happening ... Subject: Re: Debian 8 prevents the NAS to generate data volume accounting
Its the NAS that sends the data to the RADIUS server, not the client , so you need to look at debug logs (on the NAS and on the server) to get an idea of why that value is 0
alan
--- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
So you're thinking the cause might be a cheap AP.... I'm a little new to RADIUS/802.1X/FreeRADIUS, so I needed to ask for some experienced people's opinion, but I understand ... everything seem to point toward a faulty cheap AP ... I'll try to get a AIRONET when possible Thanks for your inputs and help people :-)
The NAS debug logs doesn’t bring any clue : It’s a 100€/$ Wifi AP,
Buy another one. It's cheaper to buy a new AP than to spend days trying to debug a broken one.
Alan DeKok.
--- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
participants (3)
-
Alan Buxey -
Alan DeKok -
oatech