Clients keep getting Disassociated from AP = Reason 8

[jason_sparrow]

Well, the on-going saga continues.

I have an R600 that for some reason disassociates clients giving 'reason 8' that i found in the web UI log.

Could someone tell me what reason 8 is please?

Also, could someone maybe explain what the AP classes as 'interference'?

I am confused as to why the AP all of a sudden starts to SmartSelect to find a clearer 5G channel when there no other rogue 5G networks anywhere nearby.

Plus, the 2.4G network is perfectly stable and that has plenty of reason to hop about as there quite a fair few nearby networks.

[seanmuir]

Here is some information that might help you:

https://forums.ruckuswireless.com/ruckuswireless/topics/unleashed-aps-with-zonedirector-1106?utm_sou...

I have not personally statically assigned IP addresses to the AP's, so cannot confirm if there is a work around to the bug that I, and others, have experienced.

Good Luck

Sean

[bill_burns_6069]

I'm not sure if this thread is about channelfly, "reason:8" or "unleashed".If it's about channelfly then:

If you're in a crowded wifi environment where other people's APs in the area are competing w/ you for bandwidth, then channelFly may be helping you.

If you're using it in a controlled environment where you manage all the APs and there are no rogue APs, then (in my opinion) you should turn channelFly off because it causes more problems than it solves.

[jason_sparrow]

Thanks Bill,

The original question was about "Reason 8" which has now been answered, and i think it drifted into Unleashed.

As you have advised, i did make the decision to fix the channels and now everything seems to be ok on the 5G networks.

However, the 2.4 is still on because of a few rogues nearby.

These are now jumping around all over the place when "Channel Flying" and not just doing the one hop. As i was told, it should scan first and then hop, but mine don't, and thats across 3 AP's.

[dave_watkins_74]

From my understanding, ChannelFly can't "scan first", it only has one radio and that is servicing clients, so the way it scans is by hopping and then seeing whats happening where it's landed. Over time it builds a good understanding of what channels are congested at what times of the day and then avoids them, building that initial data can take a couple of days and even after that hopping is common. 

On top of that, there seems to be a large number of 2.4Ghz devices/drivers that don't support the notification used by the AP to indicate it's changing channels. I see this even on dual band client cards, they happily seamlessly follow a ChannelFly enabled 5Ghz radio but fail to do so when on 2.4 and have to re-associate. For that reason I've never used ChannelFly on 2.4 after the initial test showed those results. I use background scanning with a long interval for 2.4

[jason_sparrow]

Thanks Dave,

Another 'interesting' development is that on my R500, it does the scanning and settles on a channel, however, for some reason, when my iPhone (6s) connects to its 5G network, it "detects interference" and so channel hops and dumps the client.

This is the ONLY time it hops as i have tested it over the last few days, and with the very latest firmware released a few days ago and the logs show it in detail.

On my R600's everything seems to be ok and this doesnt happen. In fact, one of the R600's mainly has my iphone and Macbook connected and hasn't had this issue. 

Edited to add...

I am also noticed that one of my R600's is seemingly having issues.

During the night agin, my iPhone will randomly associate and then disassociate, and from what i can see in the logs gives Reason 0. 

I also now have the following: "wmi_peer_sta_kickout_event_handler:838 Kicking off STA *************** AID 1"

I have two R600's and the main one downstairs does not have this issue, as i am connected to it all day.