How exactly does the firewall track surfing time towards the quota? Is it tracked by bandwidth over time, or is it simply the amount of time the user is authenticated against the firewall? I know I can set a timeout that will log someone out of the firewall if a certain amount of data is not been seen over time, and I was wondering if that method was used to track time towards a surfing quota.
This comes into play with younger kids who log in with an authentication agent, maybe on a laptop AND on a mobile device. It's hard to to tell them that they need to log out every time they put the device down (or that they need to log in every time they pick it up for that matter), and invariably I get complaints that even though the system says they are out of time, they really are not because their device has been idle all that time.
I just want to know so I can tell people how to conserve their surfing time.
To that end, what is everyone using a a reasonable timeout for the authentication agents? I've currently got it set to 6 minutes at 1024 bytes (which I believe is the default), but I kind of think 1K every six minutes is low and I don't believe anyone ever gets logged out at that setting.
Thanks for the info.
This thread was automatically locked due to age.
