On Sep 5, 2018, at 1:05 PM, Ryan Raamsumair via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I previously ran freeradius 2 incident free , having recently upgraded to freeradius 3 . I am bogged down with stale sessions freeradius is already the newest version (3.0.12+dfsg-5+deb9u1).
The newest version is 3.0.17.
The Nas are linksys accesspoints running on openwrt
If the user manually disconnects from the network , and acctstop is updated and the records close properly , but if the person walks away from the network no update is made
Blame the NAS. The NAS (or AP in this case) is supposed to send a stop record when it decides that the user is no longer online. If the NAS doesn't do this, it's broken. FreeRADIUS just records what the NAS sends. If the record isn't correct, then blame the NAS. No amount of poking FreeRADIUS will make the NAS send the correct records. On another note, you sent two complete debug outputs, most of which was for EAP. Not accounting. If you want us to help debug accounting issues, show the debug output from accounting packets. You also sent multiple copies of the configuration files. We don't need that. We've already seen those configuration files. They ship with the server. It's a total waste of time to send them to the list. Please read this page: http://wiki.freeradius.org/list-help It describes what information we need. Alan DeKok.