On 11/12/2016 04:38, Sachin Yadav wrote:
Here are some more details, From the logs i found that 1 NAS reboots and it updates radacct. This query cause a mass update of acctstoptime value for almost 26 records out of 319 currently active, all updates happen for openwrt NAS only. Below is the log
rad_recv: Accounting-Request packet from host 45.xx.1xx.1xx port 58986, id=0, length=189 ChilliSpot-Version = "1.3.1-svn" ChilliSpot-Attr-10 = 0x00000002 Event-Timestamp = "Nov 23 2016 15:30:09 IST" Acct-Status-Type = Accounting-On
That is correct behaviour by the NAS. When it reboots it sends an accounting packet with Acct-Status-Type = Accounting-On But if the NAS has rebooted, does this not also imply that all of the previously-active sessions on that NAS must have terminated?