Thank you for the reply Matthew The debug output is sending the value i input, including 0 The NAS is Mikrotik, and it is also getting the 0. My understanding of Mikrotik is that it will accept 0 to be unlimited now that i know that 0, 1500, and 15000 are valid in freeradius, ill look deeper into the NAS to find out why it is finding an idle-timeout event when idle-timeout is 0 Thanks! On Sat, Oct 24, 2020 at 1:43 PM Matthew Newton <mcn@freeradius.org> wrote:
On 24/10/2020 21:25, Sam T wrote:
in short, we have some users that are getting idle-timeout after under 1 min, but mostly between 20min-5 hours.
I have tried moving our idle-timeout from 1500min to 15000min, and also tried 0
Still getting idle-timeouts
Is 15000 possibly too long and not recognized by freeradius? does 0 really mean unlimited?
Look at the attributes sent in the reply shown in the debug output. If FreeRADIUS is sending the number you set, then it's nothing to do with FreeRADIUS.
My goal is to have no idle timeout or session timeout, or understand how to set these variables to simulate a best practice for no timeouts / monthly timeouts.
The device is a windows computer, so it is likely generating a good amount of background traffic via dhcp, netbios, etc (is there maybe a minimal bytle quota that defines idle? or is idle really 0 bytes?)
If your NAS is ignoring whatever values sent by FreeRADIUS, then you need to fix the NAS.
-- Matthew - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html