We have been facing an issue that may be related to inactivity on the guest network. After a period of time guests are no longer able to communicate with the network. The user still apears in the user table in the correct role however they cannot ping anything or browse the web. They can be pinged by the controller. The only way for them to function again is to disconnect from the SSID and connect and authenticate again. This is very troublesome in meetings etc. we have increased the user idle timeout value to 900 but it did not seem to help. I am confused how a loptop that is not hibernating can be sending no traffic that would keep the connection alive. Has anyone else experienced this? It doesnt seem that this should be an expected behavior. I did notice the output below in the user debug output as the last communication from the client.
Jun 20 10:30:46 :501065: <DBUG> |stm| Get Next/Get Request mac is 00:1b:77:2c:3b:ff
Jun 20 10:40:59 :501065: <DBUG> |stm| Get Next/Get Request mac is 00:1b:77:2c:3b:ff
Jun 20 10:51:11 :501065: <DBUG> |stm| Get Next/Get Request mac is 00:1b:77:2c:3b:ff
Jun 20 11:01:23 :501065: <DBUG> |stm| Get Next/Get Request mac is 00:1b:77:2c:3b:ff
Jun 20 11:11:35 :501065: <DBUG> |stm| Get Next/Get Request mac is 00:1b:77:2c:3b:ff