acctstoptime updated without acctterminatedcause
Hi everybody, I use coova chilli as captive portal and freeradius for users authentications and I have problems with freeradius that I can't reproduce unfortunatly for now. in raddact table i can see sometimes some rows with an acctstoptime not NULL but the acctterminatedcause is blank (not null... blank, empty) and i think that problem didn't close the connection on the nasid. more stange (or not... maybe it's linked), approx 50% of that problems have an acctupdateinterval greater than the stop interval. where do you think this could come from ? I use coova 1.3.2 on openwrt/lede & freeradius 3.14 on a dedicated server (debian 9). Thx Luc
On Jun 20, 2018, at 4:25 AM, Luc Zimmermann <luc.zimmermann@e-wi.fr> wrote:
I use coova chilli as captive portal and freeradius for users authentications and I have problems with freeradius that I can't reproduce unfortunatly for now.
in raddact table i can see sometimes some rows with an acctstoptime not NULL but the acctterminatedcause is blank (not null... blank, empty) and i think that problem didn't close the connection on the nasid.
more stange (or not... maybe it's linked), approx 50% of that problems have an acctupdateinterval greater than the stop interval.
where do you think this could come from ?
FreeRADIUS records what is sent by the NAS. So if data is missing, blame the NAS. Alan DeKok.
participants (2)
-
Alan DeKok -
Luc Zimmermann