On Mar 12, 2018, at 11:00 AM, Pierre Delamotte <pierre.delamotte@brightwave.co.za> wrote:
Agreed that the NAS is crappy, but ditching it is not an option for the moment (it is one of my main Capwap controller), so I have to leave with it.
Then complain to the manufacturer, and tell them to fix it.
Knowing that at least the NAS is signalling Freeradius when it is rebooting,
Is it? FreeRADIUS has accounting queries which look for a reboot ("Acct-Status-Type = On"), and close all open sessions for that NAS. So the problem *should* be fixed on the FreeRADIUS side, if the NAS follows *some* of the RADIUS standards.
could I consider the option of updating a radacct record acctuniqueid (I see that the field is defined as Unique Key NOT NULL) targeted by a stop by setting the value to NULL?
Playing games with the schema is a bad idea. It's better to fix the problem.
Should I expect bad side effects?
Yes. The larger questions is why is this happening? Even if the NAS re-uses Acct-Session-Id values, FreeRADIUS will create and use Acct-Unique-Session-Id. Which will solve the problem. So... *why* are these sessions being re-opened? Right now, you're trying random solutions. It would be much better to find the *problem*. Which then leads you to the correct solution. Alan DeKok.