Question : Windows machines will keep sending the data even if no traffic is being passed and no application/browser is open. How to stop that to see a user time out?
Environment : This article applies to all Aruba controllers and os versions.
Windows machines will keep sending the data even if no traffic is being passed and no application/browser is open.
This the user will not time out as long as he is connected.
Many times, while testing, roaming issues, idle timeout issues, key exchanges, L-3 mobility we wanted to see user pushed of the user table because of idle-timeout.
Closing internet programs and applications on the user machine just do not stop the traffic from client device. Many background services like email client sync, Windows updates and keepalives sent by chat clients do not allow us experience user idle-timeout behavior.
We can achieve this by disabling all protocol stacks on your Wireless adapter as shown below. This purges all L3 traffic being initiated from client machine and hence the user idle-timeout can be experienced.
Thus by enabling "user-debug" logging for the client, we can look at the controller's action before it deletes the entry from user table. Below image shows that a controller is trying to ping the client 3 times before deleting the entry: