Clients still getting kicked from AP.

[jason_sparrow]

I think the various questions i am asking are getting lost in other threads so....

Could someone tell me why i'm seeing this...?

"wmi_peer_sta_kickout_event_handler:838 Kicking off STA *************** AID 1"

I am also seeing the above, but with AID 2 at the end.

Thanks.

[seanmuir]

OK so your max-aid value is not impacting clients being kicked or stopping them from connecting.

I would say that unless you are seeing any issues with clients not being able to connect or are being kicked during connection i.e. watching You Tube and then your suddenly offline (other entertainment  websites are available), that there is no reason to be concerned with outputs from the log of the AP.

What I would say is that if you have session idle timeout configured on the AP/ZD then this value should be set to be the same as your DHCP lease value as I have seen this to cause issues in the past

Note: In my home network I have the session idle timeout value within my WLAN on my ZD set to 600 minutes.

[jason_sparrow]

Thanks Sean,

My DHCP leases on my router are set to the default which is 1500minutes so i guess that rules that out, but then, should my AP match the router or is there no way of altering the AP as im on stand alone firmware?

My iPhone also doesn't seem to always connect straight away when i have been out of the building and return, and sometimes its a fair few minutes before it does connect.

My only reason of concern with the logs is that again i got up this morning to find my phone had dropped back to 4G, and when i checked the log again when i got up, it showed a channel fly, just before the kickoff (AID 1) which now appears the reason that my phone was disconnected, but then reconnected when i unlocked it. (the last actual wifi use was around 11pm as i check emails before i go to bed).

What i don't understand is why it gets kicked (Aid 1, and then also Reason 0) but then doesn't reconnect? There is plenty of signal there.

The frustrating things is, is that this doesn't happen every night, and when it does, the log seems to show a different reason each time, although not always.

If need be, i will open a support ticket, however, i'm not overly convinced there is a solution.

[seanmuir]

I would monitor the reason Codes and see what your getting.

Reason Code 0 is a funny one as it's reserved:

https://support.ruckuswireless.com/answers/000002430

Usually you see Reason Code 4 or 8 - none of which are anything to worry about.

If you are just having issues with reconnecting on an irregular basis, have you tried other devices and are you seeing the same behaviour, or is it specifically tied to the iPhone?

[jason_sparrow]

Hi Sean, 

Yes i get the occasional reason 0, and i did find that it was a reserved code, although im sure i saw somewhere that it is also listed as "normal operation" or words to that effect.

Must admit, i certainly havent seen a Reason 4 (inactivity?) code yet.

[jason_sparrow]

Anyway, apologies for all the questions.

i appreciate that these products are primarily for enterprise use, however, i would like to understand how they work as much as possible so that i can learn what to look out for when ther are problems such as this.

🙂